Read the statement by Michael Teeuw here.
How to send a notification
-
@alyx i don’t know… i didn’t change anything in your config…
if you use the alexa app to turn the plug on or off, do you see the notifications?
-
@sdetweil ok I re added the selfie device on the alexa app and it found it fine but its now coming up as unresponsive
-
@alyx so, discovery records the IP address of the ‘device’ and the port.
so, if your pi changes ip address during boot, then it won’t work again …
all my pi type devices have fixed addresses to avoid this problem…
-
@sdetweil ah ok I’ll set a static! TBH I did have that concern but i was wrong to assume it was dynamic with the IP’s
I’ll come back if this works or not , I have a call rn
-
@alyx yeh the Alexa design is devices don’t move around, and one would only do discovery occasionally
then u have to delete the devices and rediscover
-
@sdetweil ok so after fighting with my interfaces file for a few days I have a static IP
Only issue is that I can discover devices on the Alexa app but they arent usable and just come up an unresponsive…
It seems the static IP has messed with that feature ? Any advise on this please?
-
@alyx no after u get a static IP, and your mm config.js has
address:"0.0.0.0", ipWhitelist:[],to allow incoming connections from outside the pi machine
it should work
-
@sdetweil I did that but still isnt working
-
@alyx sorry, don’t know how u to debug this. it’s really hard
you config works perfectly here
your devices are found (that means the module is running) and the ssdp discovery workednow alexa will call back at the server (MM system) ip address and port for each switch
which goes into the node_helper and is then sent up to the modulename.js to send to other modules -
@sdetweil hmmmm would you think it has something to do with my static IP?
I did the whole thing via my interfaces file and then reserved an IP in my router for it also.
Edit: I did the static in in the DHCP file. Interfaces is just to activate my USB network adapter (PI OS on desktop)
