-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
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
Wait for a clear to send message? #53
Comments
I believe the wiki is referring to the physical layer implementation and that the Wi-Fi module handles and filters out most of that. |
@KBlixt this would be needed to support an RS-485 solution. But I don't have anything to test/debug that so would have to rely on someone else's work. |
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. |
This issue has now been marked as stale and will be closed if no further activity occurs. |
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: