Read the statement by Michael Teeuw here.
MMM-Alexaonoff can’t find devices
-
@sdetweil hi Sam a month ago that was your post, you have shown me how it looks at your pi 😀
my Maschine is the same -
This post is deleted! -
@Stoffbeuteluwe so, can u go to one device and get its IP address somehow? so we can see if its on the same network address range…
also wonder if the code works on Mac… open the developers window and look at the console…
but u said it worked once…maybe you can look in your router dhcp clients page
-
i can’t get alexa to discover any of virtual wemo devices
-
@sdetweil maybe Alexa problem
-
21900 21901 21902 21903 21904 21905 21906 21907 21908 21909 21910 21911 21912 21913 21914 21915 21916 21917 21918 21919 21920 21921 21922 21923 21924 21925 21926 21927 21928 21929 21930 21931 21932 21933 21934 21935 21936 21937 21938 21939 21940 21941 discoveryService not running +0ms FauxMo service started. Listening on 192.168.178.35:21900-21941 discoveryService binding to port 1900 for ssdp discovery +2ms discoveryService server listening 0.0.0.0:1900 +164ms deviceEndpoints Setup Server running. +9msdo you know what that means?
-
@Stoffbeuteluwe said in MMM-Alexaonoff can’t find devices:
FauxMo service started. Listening on 192.168.178.35:21900-21941
means the code in the module has setup to listen on a number of known ports that the Wemo plugs use for discovery by the alexa plugin.
when alexa does home automation device discovery, it sends a broadcast message ('is anyone there?) to anything listening on those ports, and whatever is listening will respond with a predefined response (‘yes, I am here’)…
the discovery code for wemo plugs was built into alexa early code… but seems that Alexa has removed that code and expects a plugin to do the work… (My opinion)
a google search on ‘wemo app not finding devices’ produces a lot of info. I could never get alexa to discover my mirrors
-
@sdetweil ok thank you for your help…
