Same concern here, this still requires the cloud, it would be great if it could be a completely “offline” (cloud independent) integration, so we’re not dependent on what will eventually be unmaintained by Dreo, increased risks of user/data leaks, etc.
Obviously it’s understandable that it was easier to do the API calls to Dreo’s cloud than to break the cert pinning of the app to RE the local calls, so I’m still glad I found this integration and appreciative of the hard work that when into it .
I’m sorry I just saw this. Yes, we use the cloud API that we traced from the app. I don’t know what protocol the fan actually uses to talk to its servers. If anyone knows that, we could consider making it local.
Thanks for the response, really appreciate the hard work that was done so far!
Looking at the traffic between the (AWS EC2) cloud and the fan, it clearly is MQTT based, but all is encapsulated in TLS1.2 rendering RE a bit more complicated (need an mitmproxy setup, and hope that certs can be bypassed…).
What is the support like for the PolyFan 513s? Looking to pick one of these https://a.co/d/0boiLZGb up and wanted to see if it’s fully supported. Thanks!
Hello all, I worked my way through a hacking adventure and built a completely cloudcut integration for my Dreo fan (Pilot Max S), via a local ESPHome device:
For those who are interested in getting rid of the cloud portion of the HA integration…
This only works for the DR-HTF004S and is not expected to work on any other fan model. Other fan models would require their own investigative work.
@ouaibe , would it be possible to start a new conversation for the cloudcutter work? It’s tricky to follow the thread and know which one people are discussing.
Please keep this thread updated with cloudcutter progress. I was able to upload a ESPHome file to it, but I made mine a dumb fan thinking the wifi commands may be the same. I know we were warned, just figured whatever you figure out may help my situation.
.
