Following up on the above.
- Fan reboot appears to be a very inexpensive operation (it takes only a few seconds; when continuisly running
ping, only one or two responses are lost)
- I ran a packet capture while rebooting the fan from the app, and as I expected, it’s trivial:
I plan to add a periodic reboot to my HA setup via an automation (I’d say even doing this 4 times a day would not be horrible. It’s also a silent operation - no beeps, and safe to do in a bedroom overnight).
This may be a viable workaround for our woes. I have not contacted MF support about any of this, and to be honest, I do not believe they’d be open to feedback and troubleshooting, since their grand scheme of integration seems to be to rely on their cloud.
Worth pointing out is that fans are rather chatty on multicast, so there is space for improvement for discovery and integration, but that may be over my time budget at the moment.
A side note… it is horrifying that this whole API is in plain-text, with no authentication whatsoever. The IoT scares the s. out of me. Then again, I’m glad they’re clueless, since reverse-engineering is beyond trivial.