You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: Home Assistant Core 2023.6.3
Which runs PySwitchbot==0.37.6 for its Switchbot integration
When I call the 'turn on' service multiple times in a row (using to press a button on a thermostat) the WoHand only executes the press once, despite seeing the Sending command 570101 the appropriate number of times in the debug logs.
I'm trying to tinker and see what else I can figure out, but the best I can figure out now is that on the WoHand side it's consuming multiple 'Turn_on" commands and processing them as one. My understanding is that after sending the command, the returned notification is a promise of sorts, and back to back commands receive the same promise, 014890 in the case of the above logs.
Edit: It seems Turn on result: 014890 is (usually? still testing) a successful button press. Whereas Turn on result: 03ff00 is an ignored request. Wondering if these were some kind of standard response codes, I only found 03ff00 referenced here alongside an mqtt bad request response.
The following log is correlated to 2 actual button presses on the WoHand.
Yeah, after further testing it seems like the responses from the device could be used to validate that a command was executed as opposed to ignored. And maybe we could code the library to auto-retry and or auto-delay. I'll try my hand at this if I have some time.
Context:
Home Assistant Core 2023.6.3
Which runs
PySwitchbot==0.37.6
for its Switchbot integrationWhen I call the 'turn on' service multiple times in a row (using to press a button on a thermostat) the WoHand only executes the press once, despite seeing the
Sending command 570101
the appropriate number of times in the debug logs.I believe this is the relevant parts of the logs
I'm trying to tinker and see what else I can figure out, but the best I can figure out now is that on the WoHand side it's consuming multiple 'Turn_on" commands and processing them as one. My understanding is that after sending the command, the returned
notification
is a promise of sorts, and back to back commands receive the same promise,014890
in the case of the above logs.Edit: It seems
Turn on result: 014890
is (usually? still testing) a successful button press. WhereasTurn on result: 03ff00
is an ignored request. Wondering if these were some kind of standard response codes, I only found03ff00
referenced here alongside an mqttbad request
response.The following log is correlated to 2 actual button presses on the WoHand.
Commands spaced at least 1 second apart seem to work reliably.
The text was updated successfully, but these errors were encountered: