-
Notifications
You must be signed in to change notification settings - Fork 112
Description
Hi,
I have the same (or very similar) problem as reported in issue 46. That bug seems to have been closed without resolution but the instructions in this comment indicated that it would be helpful to attempt to replicate the issue with the same hardware using the dev mode of fauxmo.
I installed the stand alone package of fauxmo on the same Pi and stopped the Pi-Somfy, then I copied the example config.json and ran fauxmo. Using this setup I was able to have my Echo discover all the fake devices in the example config.json. It worked first time but it also dumped a trace.
That seems to have been benign tho because I am able to tell Alexa to turn on/off the discovered devices (which results in more spew as it tries to hit the fake URLs in the config.json).
I'm hoping that this will be useful in pinning the issue down?
For context here's some more info:
HARDWARE
Raspberry Pi 3A <--- Fresh install with just Pi-Somfy (and now fauxmo as well)
Echo Dot 3rd Gen
These devices are both on the same SSID/VLAN
I've also included a section of my operateshutters.log which I think illustrates the same problem as the original bug (I have not gone through the steps to add additional logging, but happy to do so if needed).
Other Observations
- Initially I was stupid and had the Dot and RPI on different VLANs - in this config I unsurprisingly had nothing in the log at all
- At this point I tried the Wemo app and there was also nothing
- Then I realised the RPI was on the wrong VLAN and moved it over
- Alexa didn't change behaviour in any way, but the Wemo app did (it now sticks on searching forever, whereas before it just said 'no devices' right away)
LMK if I can fiddle around with anything else? I have cloned master of fauxmo, but 2 seconds of diffing between that and the fauxmo.py code in Pi-somfy made it clear that I can't just drop in the new one and expect it to work :)