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
Hello, I'm considering using this module for some automation and was reviewing the client.
According to the wiki a client need to keep track of which channel the client have and wait for a "clear to send" message that contain the channel code of the client. And then send the message? Otherwise we could accidentally send our command while the main board sends a status update or whatnot.
It should be fairly easy to implement and I can do it myself but maybe I've misunderstood something here? So before I start I'd like to check with you if there is a reason for not waiting for the signal to send?
The text was updated successfully, but these errors were encountered:
Ok, I have some plans to try to connect my spa to a raspberry pi through a RS-485 card and then control it through python on the raspberry pi. I'd have to alter the code to listen to these ready to send messages and replace the tcp layer with a serial port layer.
we just moved in so might be a while before I get to this but I hope to get to it before winter.
Hello, I'm considering using this module for some automation and was reviewing the client.
According to the wiki a client need to keep track of which channel the client have and wait for a "clear to send" message that contain the channel code of the client. And then send the message? Otherwise we could accidentally send our command while the main board sends a status update or whatnot.
It should be fairly easy to implement and I can do it myself but maybe I've misunderstood something here? So before I start I'd like to check with you if there is a reason for not waiting for the signal to send?
The text was updated successfully, but these errors were encountered: