"wemo list" Returns Nothing #80
Comments
|
I punched a few holes in my firewall (port 54321) and I get the following output now (still comes back with no results): [root@localhost .wemo]# wemo -d list |
|
what wemo devices are you using? This shows it found one wemo device but could not classify it... |
|
My network has 3 WeMo devices. 2 of the regular switches and 1 insight switch. I'll attach the setup.xml files for the regular switches. Here is the setup.xml of one of the regular switches: |
|
Sorry about the comment above. I cannot seem to be able to get it to display the XML properly. You can download the file from http://ocaff.com/switch1.xml |
|
hmm... not really sure what went wrong. I did notice however that the switch for which you gave the xml was on firmware version 2.0 which wasn't supported until a couple hours ago. Perhaps git pull the latest version and try again? I don't see why the devices wouldn't be recognized though... could there be a firewall interfering? |
|
I pulled down the latest source and that didn't change anything. I disabled by firewall on CentOS and that did not do anything [root@localhost ouimeaux]# service iptables save Mar 19 06:55:08 localhost.localdomain systemd[1]: Stopped IPv4 firewall with ... Here is the debug from getting the list: DEBUG:ouimeaux.discovery:Binding datagram server to 10.1.200.1:54321 Some things to note here. The device that it found at 10.1.0.1:53164. That device is my router, not a WeMo. I also noticed this morning that in the debug it is not listing any IP addresses of my actual WeMo devices. This morning I have 2 of them on my network and their IP addresses are 10.1.1.150 and 10.1.1.151. Could the issue be that I am running a /16 network and that there are too many possible IP addresses to find? |
|
It may be possible the list command is timing out without getting a response due to such a large network? I would think it would still work but why don't you try running |
|
A 2 minute discovery didn't pick anything up. I will try a 10 minute one to see if that yields anything different. |
|
The 10 minute crawl didn't pick anything up either. |
|
FWIK we are sending out a multicast packet to the router to elicit a response from all UPnP devices on the network. All UPnP devices are required to send their response to the sender of the multicast packet. UPnP seems to be enabled on the router as you are receiving responses. Do you have multiple routers in the environment? This is sometimes a headache for UPnP from a quick google. |
|
I also notice you are running ouimeaux on an ip of 10.1.200.1 while your devices are on 10.1.1.X. Maybe your wemo devices don't support your Subnet Mask? Maybe try setting their IPs or your servers IP to be within the same /24 subnet? I don't think it is a problem with UPnP in general to be used across a /16 subnet but maybe the Belkin implementation is causing them not to respond? |
|
That would not surprise me much. I've noticed that Belkin struggles on the software end of things (hence the reason I feel the need to control these things on my own). Off topic question (and if this belongs in another topic, let me know). Is it possible to use ouemeaux using just the IP address of the device? I have my devices setup to use a reserved IP address on my router so I can easily locate them on my network. |
|
Essentially that is what ouimeaux is doing. The devices are UPnP devices which means that they most be communicated with using SOAP. There is not a REST API builtin. Unfortunately your devices are not responding to a UPnP discovery request which is a problem. You may be able to re-use the code and hardcode the IPs but you still need to communicate with SOAP on the correct ports (which change) and so it's not as simple as pointing your web browser at them. I would suggest trying the set your DHCP reservations to be on 10.1.200.X first to see if that resolves the problem. |
|
Just want to let you know I'm not falling off the wagon. I tried getting the IP address closer and that did not help. I changed my network from a /16 to a /24 network in hopes that a smaller network would help move things along. Doing that so far has caused my WeMo's to not respond to the app at all. I think I will have to readd them to the app (after waiting for the DHCP leases to expire). |
|
Maybe try resetting the firmware from the switches themselves and re-pair them to your network? I'm kind of lost for reasons why it's not working at this point! |
|
I think I want to chalk it up to Belkin at this point. These things have been so temperamental ever since I got them. Right now my router can see that they are connected and I am able to ping them, but the WeMo app cannot see them (and neither can Ouimeaux). I think that whatever Belkin did with the last software update, they messed up the outlet's ability to respond to a UPnP message. |
|
I just noticed that Ouimeaux can see the Roku devices on my network, but not my outlets. I am going to unplug all the devices, let them sit for awhile and then try to add again. That worked once. |
|
Maybe it was a botched firmware update and the app had the devices cached and then once you changed their IPs it couldn't find them again? Either way I'd recommend holding the reset button on the switches themselves to re-initialize them and then go through the setup process with the app. |
|
Since you've got two different subnets is it possible that some of your devices are behind a comcast/dsl router and some of your other devices are behind a wifi router/switch? Maybe consolidating everything onto the same subnet will fix the issue. |
|
Hi @joshpennington, did you solve this issue? |
|
The problem was with my Comcast modem / router. I put a new router in front of it and had my modem / router put into gateway mode and that worked better. The router I used was a pfSense router that I built. |
I currently have 3 WeMo devices on my network and the wemo command returns nothing. The output of my debug when I run the command:
[root@localhost .wemo]# wemo -d list
DEBUG:ouimeaux.discovery:Binding datagram server to 10.1.200.1:54321
INFO:ouimeaux.environment:Discovering devices
DEBUG:ouimeaux.discovery:Broadcasting M-SEARCH to 239.255.255.250:1900
DEBUG:ouimeaux.discovery:Broadcasting M-SEARCH to 239.255.255.250:1900
DEBUG:ouimeaux.discovery:Broadcasting M-SEARCH to 239.255.255.250:1900
DEBUG:ouimeaux.discovery:Broadcasting M-SEARCH to 239.255.255.250:1900
DEBUG:ouimeaux.discovery:Broadcasting M-SEARCH to 239.255.255.250:1900
This is a pretty much a new install of Ouimeaux so pointing me toward any config options would be appreciated! I am running it on CentOS 7.
The text was updated successfully, but these errors were encountered: