error: Caught Exception: can't start new thread - more on this

[pmitev]

• pySonoffLAN version: 0.3.0
• Python version: 3.7.3
• Operating System: Raspbian GNU/Linux 10 (buster)

Description

This fails

$ pysonofflan discover
2020-07-31 08:12:42,277 - info: Attempting to discover Sonoff LAN Mode devices on the local network, please wait...
2020-07-31 08:12:42,563 - error: Caught Exception: can't start new thread

but this manages to work, perhaps when it runs slower it does not reach the limit of the threads (don't think so) or something fails with the logger

$ pysonofflan -l DEBUG discover

2020-07-31 08:13:24,853 - debug: Attempting connection to IP: 192.168.1.250 on port 8081
2020-07-31 08:13:24,855 - debug: Attempting connection to IP: 192.168.1.251 on port 8081
2020-07-31 08:13:24,857 - debug: Attempting connection to IP: 192.168.1.252 on port 8081
2020-07-31 08:13:24,860 - debug: Attempting connection to IP: 192.168.1.253 on port 8081
2020-07-31 08:13:24,862 - debug: Attempting connection to IP: 192.168.1.254 on port 8081
2020-07-31 08:13:24,864 - debug: Attempting connection to IP: 192.168.1.255 on port 8081
2020-07-31 08:13:25,387 - info: Found Sonoff LAN Mode device at IP 192.168.1.206

Then this hangs forever

$ pysonofflan --host 192.168.1.206 -l DEBUG state
2020-07-31 08:15:35,269 - info: Initialising SonoffSwitch with host 192.168.1.206
2020-07-31 08:15:35,279 - debug: Initializing SonoffLANModeClient class in SonoffDevice
2020-07-31 08:15:35,281 - debug: send_updated_params_loop is active on the event loop
2020-07-31 08:15:35,282 - debug: Starting loop waiting for device params to change
2020-07-31 08:15:35,282 - debug: send_updated_params_loop now awaiting event
2020-07-31 08:15:35,283 - debug: setup_connection is active on the event loop
2020-07-31 08:15:35,284 - debug: setup_connection yielding to connect()
2020-07-31 08:15:35,285 - debug: Connecting to websocket address: ws://192.168.1.206:8081/

The switch is S20, FW name PSA-B01-GL running on 3.4.1 firmware version

By the way - on the README.rst the debugging option is wrong
-v, --verbosity LVL Either CRITICAL, ERROR, WARNING, INFO or DEBUG

[pmitev]

I can see from the other project that this will not work with the the 3+ firmware. The first problem is still valid, though.