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
I have an issue with my Flexit Roomie Dual where the commands are not registered all the time. I see that this communication is UDP-based, so I'm wondering if that is the reason for this. I can issue the command: .set_airflow(1), but nothing registers on the fan itself. If I then rerun the command, then it may work the next time.
Are there no acknowledgements in the protocol? Everything is based on UDP?
The text was updated successfully, but these errors were encountered:
Hi, the protocol used by these fans are UDP, which by nature means there is not acknowledgement of a successful transmission as you would have found in other protocols like TCP. There is however a form of acknowledgement in the implementation of the "API" / controller interface who will return a byte array representation of the current settings on successful changes to any settings. I have not implemented any sort of error handling in this library (which could have been done). To be honest I never really saw the need to do so as this has worked flawlessly in my setup. You could try to pull the source code and change the static timeout value I have set to 15 seconds to see if that helps. That said, 15 seconds should be more than enough time so i have a suspicion that your problem is related poor wifi connectivity or some other network error. I'm guessing that the manufacturer of these fans didn't invest much in a decent wifi module, so you could try to improve the wifi coverage in the location of fan (move router / AP).
Hi!
I have an issue with my Flexit Roomie Dual where the commands are not registered all the time. I see that this communication is UDP-based, so I'm wondering if that is the reason for this. I can issue the command: .set_airflow(1), but nothing registers on the fan itself. If I then rerun the command, then it may work the next time.
Are there no acknowledgements in the protocol? Everything is based on UDP?
The text was updated successfully, but these errors were encountered: