I’ve the same problem (but not for turning it on, only by turning it off). So in flows i turn it of 2 times (2 same off cards in a flow). It also is an issue with the duux app itself. Sometimes i have to push te off button twice. Turning it of with google home doesnt work either, or you have to say turn it off twice within any seconds of the first beep.
I hope they will figure this one out, because its very annoying. But it is not so much a Homey/Duux problem but really a standalone Duux problem.
For more information how to connect your deveice to Homey, see the following link: Connecting Homey
If this will not solve your problem, please send us an email to firstname.lastname@example.org and describe your problem. Then our IT department will help you
I happily bought the Duux Threesixty because the Duux website specifically mentions that it works with Homey.
I managed to add it as a device (took me a couple of tries though) but since then the Threesixty is most of the time unreachable for Homey. The only thing I found that helps for a while (sometimes an hour, sometimes shorter) is to pull the electrical plug to turn the Threesixty off and plug it back in again.
In trying to bypass the reported bug I uninstalled the Duux app from my (Android) phone. This didn’t help at all.
I use piHole as a DNS server/tracker blocker and although the Threesixty does not appear to be blocked by it this might be an issue?
Okay. Disabling Pi-hole didn’t do the job. The Threesixty still gets disconnected (unreachable) for Homey after a while. Sometimes hours. When it’s unreachable for Homey I can still use the Duux app to operate it. Also, it becomes unreachable for Homey when the Threesixty is off or on, doesn’t matter.
The Threesixty keeps on reporting to be unavailable at for me random times in Homey. I have removed the Duux app from my phone, it doesn’t help. I don’t really understand the advice to remove the Duux app from multi-tasking. I guess I have to close all background apps on my phone, tried that numerous times but it doesn’t help either.
I thought I had a smart solution by having a flow to turn the power off and on every 2 hours (I have Threesixty connected through a smart powerplug). This works (although it doesn’t always solve the unavailability issue) but I don’t want that to happen when Threesixty is actually on and heating. Since the Threesixty can change to the unavailable state while heating I can’t check if it’s working before switching it off. The flow simply won’t run because Threesixty is unavailable so it can’t be checked.
I have tried the flowcard which checks if devices didn’t report, that doesn’t give the information I need.
I have tried a flowcard which checks if the Duux app has crashed, it doesn’t.
When I look in the Homey Developer Tools I see the property Available with value: No (Dit apparaat is tijdelijk onbereikbaar.) So the information is up for grabs. I just can’t figure out how to use it.
Is there a way to use this information in a flow? Like If device not Available…etc?
Or maybe with HomeyScript (didn’t use that up to now)?
I’m afraid not. Situation unchanged. The Duux still randomly disconnects from Homey so sometimes it won’t turn on through a flow and sometimes it won’t turn off through a flow. Annoying, especially since they advertise it to be compatible with Homey which was for me the main reason for choosing it.
And for something completely new, last week it wouldn’t even turn on using the hardware button on the thing. Had to disconnect and reconnect the powercable first.
Not happy with this product and wouldn’t recommend. Sorry.
I bought a Duux Threesixty - mainly because Duux is advertising the Homey integration.
The setup with the Duux app is fine - alls is working.
The Homey setup is asking for email/PIN and login is correct. But after that, no device is found.
@Duux : Any hints what’s wrong?
AdBlock is passing the calls to duux-service.vercel.app. So no network problem.