-
Notifications
You must be signed in to change notification settings - Fork 2
wemo.switch doesn't return #2
Comments
The statement Edit: Type |
Initially I reported it doesn't return (meaning no prompt, no error thrown), though it turns out I wasn't patient enough. It did eventually throw an error (actually 4 of them) after 30 seconds - all were 'no route to host' errors. BTW, on an unrelated note, I updated my init.py to use python3.6, as, I'm thinking 'python3' will run 3.5.3 (the default, in my particular installation). Some of the output makes reference to port 80, which is surprising, because I believe the management port for wemo is 49153. I do see in init.py, that there is a reference to the port number range 49152-49156, but I don't see this range being tested based on the thrown errors. pi@raspi:~/Downloads/wemo-master/wemo $ python3.6
During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
After installing wemo (sudo pip3.6 install wemo), I started a python3.6 shell, ran import, then entered 'bedroom = wemo.switch('192.168.2.121'), but the command didn't return.
I'm able to go to http://192.168.2.121:49153/setup.xml and see output from the switch, and am able to send commands to turn the switch on/off, using other software.
Am I missing something?
The text was updated successfully, but these errors were encountered: