I assume this will give some serious issues with the Homey Cloud, because they are talking about ‘applications’ and not ‘accounts’, which would make sense from a software pov. This means that the whole Homey Cloud is seen as one application.
Again, Homey Pro runs locally and therefor without issues, but the Homey Cloud is unable connect since this morning.
Running Homey Pro and it just crashed with the token/Id error again. Restarting app does work initially however all my airco devices are inaccessible since 21:00 CET
I tried that several times. It keeps telling me that I have an invalid ID or password. The password and ID I enter are correct but it keeps shutting me out even if I set a new password using “Forgotten Password” routine.
Just published version 4.2.2 that hopefully should fix the issue on Homey-Cloud.
I can not fully test it because to run a app in development mode on Homey Cloud it using a local docker container and therfor also the local public WANIP addres.
The 403 forbidden is probably a security measure on the Daikin platform because most homey cloud instances will do there request from the same public IP address.
If to many request are done the Daikin platform blocks this ip adress for some while.
In theory this should be normalized and the authorization should work again.
UPDATE:
Issue fixed by repairing the devices as mentioned. Which is pretty weird as i could still control them perfectly fine in Homey. So if anybody else is having these issues in cards, repair the devices!
Hi,
when trying to set the mode in a flow, i always get this error:
Anybody else experiencing the same? Existing cards/flows are still working, just can’t seem to change any existing one or add a new card to set the mode.