We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using state, on or off commands, I get an error when it is finishing and the command does not return
pysonofflanr3 --host 192.168.1.58 --api_key on 2023-03-02 18:37:09,566 - info: Initialising SonoffSwitch with host 192.168.1.58 2023-03-02 18:37:09,734 - info: Service type _ewelink._tcp.local. of name eWeLink_10000be334._ewelink._tcp.local. added 2023-03-02 18:37:09,738 - info: None: Connected event, sending 'available' update 2023-03-02 18:37:09,738 - info: unsolicited update received from switch: off 2023-03-02 18:37:09,738 - info: == Device: 10000be334 (192.168.1.58) == 2023-03-02 18:37:09,738 - info: State: OFF 2023-03-02 18:37:09,738 - info: None: Connected event, waiting for disconnect 2023-03-02 18:37:09,947 - info: None: Connected event, sending 'available' update 2023-03-02 18:37:09,947 - info: == Device: 10000be334 (192.168.1.58) == 2023-03-02 18:37:09,947 - info: State: ON 2023-03-02 18:37:09,947 - error: Unexpected error in shutdown_event_loop(): gather() got an unexpected keyword argument 'loop' ^C Aborted!
The text was updated successfully, but these errors were encountered:
this is no longer maintained. I have a project built on this which works - https://github.com/dauheeIRL/SonoffSimpleLAN
Sorry, something went wrong.
pySonoffLAN version: pySonoffLANr3 Python version: 3.10.6 Operating System: Kubuntu 22.04 Description When using state, on or off commands, I get an error when it is finishing and the command does not return What I Did pysonofflanr3 --host 192.168.1.58 --api_key on 2023-03-02 18:37:09,566 - info: Initialising SonoffSwitch with host 192.168.1.58 2023-03-02 18:37:09,734 - info: Service type _ewelink._tcp.local. of name eWeLink_10000be334._ewelink._tcp.local. added 2023-03-02 18:37:09,738 - info: None: Connected event, sending 'available' update 2023-03-02 18:37:09,738 - info: unsolicited update received from switch: off 2023-03-02 18:37:09,738 - info: == Device: 10000be334 (192.168.1.58) == 2023-03-02 18:37:09,738 - info: State: OFF 2023-03-02 18:37:09,738 - info: None: Connected event, waiting for disconnect 2023-03-02 18:37:09,947 - info: None: Connected event, sending 'available' update 2023-03-02 18:37:09,947 - info: == Device: 10000be334 (192.168.1.58) == 2023-03-02 18:37:09,947 - info: State: ON 2023-03-02 18:37:09,947 - error: Unexpected error in shutdown_event_loop(): gather() got an unexpected keyword argument 'loop' ^C Aborted!
I have the same problem and passed it by using the latest one in repository. Just clone repo and run python setup.py install
python setup.py install
No branches or pull requests
Description
When using state, on or off commands, I get an error when it is finishing and the command does not return
What I Did
pysonofflanr3 --host 192.168.1.58 --api_key on
2023-03-02 18:37:09,566 - info: Initialising SonoffSwitch with host 192.168.1.58
2023-03-02 18:37:09,734 - info: Service type _ewelink._tcp.local. of name eWeLink_10000be334._ewelink._tcp.local. added
2023-03-02 18:37:09,738 - info: None: Connected event, sending 'available' update
2023-03-02 18:37:09,738 - info: unsolicited update received from switch: off
2023-03-02 18:37:09,738 - info: == Device: 10000be334 (192.168.1.58) ==
2023-03-02 18:37:09,738 - info: State: OFF
2023-03-02 18:37:09,738 - info: None: Connected event, waiting for disconnect
2023-03-02 18:37:09,947 - info: None: Connected event, sending 'available' update
2023-03-02 18:37:09,947 - info: == Device: 10000be334 (192.168.1.58) ==
2023-03-02 18:37:09,947 - info: State: ON
2023-03-02 18:37:09,947 - error: Unexpected error in shutdown_event_loop(): gather() got an unexpected keyword argument 'loop'
^C
Aborted!
The text was updated successfully, but these errors were encountered: