Discover won't find my devices anymore #193
Comments
|
i'm getting the same issue, Have you made any progress? |
|
This has to be firmware-related because another third party program I use to control Wemo switches stopped working as well. I hope it's a trivial fix. |
|
Is anyone still maintaining this project, or at least is there anyone who can fix such a critical issue caused by a firmware upgrade? For now I've fixed the issue by simply replacing my WeMo plugs with TpLink plugs - they provide a way better maintained Python library, more functionalities, they're much cheaper, and in my case being able to control my smart devices only from the official app is not an option at all. I can't believe that an expensive smart plug like WeMo offers such scarce features compared to others on the market and such suboptimal and unmainteined development tools, while it costs nearly twice as a TpLink plug. I'd advice everyone to avoid them, there are way better alternatives around nowadays. |
|
I found a bash script that works very reliably from a Windows command line but you have to activate the Linux subsystem in Windows 10 and install Ubuntu which is no biggy. Instructions here: https://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/ Only caveat is you have to direct commands to a Wemo switch's specific IP address so IP reservation is a must. Usage is: My Windows .bat file looks like this: wemo_control.sh is in the attached zip file. Hope this helps! |
|
@replayreb Thanks for this script, this was exactly what I was looking for, I don't even need python now! |
|
Anytime! |
…devices over HTTP/XML, see iancmcc#193
This is an issue I've been experiencing consistently for 1-2 months after a firmware upgrade.
I have two WeMo devices both running the latest firmware according to the app (WeMo_WW_2.00.11401.PVT-OWRT-SNS), and both can't be discovered anymore neither through the Python API nor
wemo listdirectly.Example output of
wemo -d list(note: my devices are on IP addresses 192.168.1.19 and 192.168.1.20 but neither of them appears in the output):What I have tried already:
Tested the command above from at least 3 different computers with the latest GitHub version of ouimeaux
Made sure that both my devices and my computer are on the same WiFi network
Switched off my VPN
Explicitly bound ouimeaux to my wlan interface IP address
Increased discovery timeout to up to one minute
None of these options worked, so I guess that something must definitely be broken on ouimeaux/switch sides but I can't figure out what.
Any hints on how to investigate what's not working and why the client doesn't receive M_SEARCH replies from the switches?
Any way to implement a workaround that allows users to skip discovery and directly connect to the devices via IP address? (it would make things lots faster, btw)
The text was updated successfully, but these errors were encountered: