I have the same problem here.
First check goes green, i get an error, restart the con op the thermostat. Second check never gets green
I figured it out after calling the Heatit support phone. The instructions are literally to do the same operation twice.
To pair the zwater2, click 3 times, when the green light shows do it again.
To pair the thermostat, start the pairing, when the green light shows, exit the pairing on the thermostat and do it all over again. I guess I failed the IQ test, but I wish it was more clearly states in the instruction manual @HeatitControlsAB . Look forward to using your product.
Hi.
This issue will be fixed in the next version of our Homey app.
Homey is one of only two gateways for which we have to develop our own integrations. As a relatively small team, we have limited resources to allocate to the Homey app, which unfortunately means occasional bugs can occur.
2 Likes
Good to hear you were able to include the devices.
The fact that you need to run the same process twice is due to the way Homey does inclusion.
In their system, they always force you to exclude a device before including it. We do not account for how specific gateways do inclusion in our manuals, as it often varies, and can be changed in updates.
In the driver, we also only have the one item called learnmode (Link to Github where it shows this line) which decides what it shown, we cannot make it so it shows something else for inclusion and exclusion
Hi, I understand youâve gotten support on this directly, but for the sake of others wondering the same.
This will be added in an update of our Homey app.
1 Like
Hi,
Thanks for the update â totally understand. Softwareâs never easy, and with limited resources it makes sense that some bugs slip through. I appreciate you taking the time to fix this in the next release. Looking forward to the update!
Best,
Timothy
Hi everyone,
It appears that something has happened over the weekend which causes the Heatit Controls app to crash.
Our current assumption is that it only affects Homey Bridge customers.
Weâre currently working with Homey to resolve the situation.
Seems there mightâve been an issue with Homey servers in Stockholm.
The server has been restarted and it should be fixed now.
Hi,
I have Z-TEMP3 thermostats.
Unfortunately, the status of them (contact or demand is on of off) is not a data in flows (such as Z-TEMP2 for example) while this information is maybe the main point.
Do you think in the implantation of this data?
Thanks
Hello, this major limitation has been already reported. This should be fixed soon (I hope). Thanks
@fred_fontbonne @Flan
A beta version with this flow card has been created.
2 Likes
Hi,
The new flow card works fine except that it turns true (1 or 2 times each ours) even when the state doesnât change.
The other small problem is that the state change info is not always recorded when the manipulation is done using homey interface (It is ok when we change the state physically on the
thermostat).
Thanks for this new version.
We will do some more testing, the trigger should trigger when the device sends a Thermostat State report which it does in the same way regardless of if you control it locally or via the gateway.
It also shouldnât send multiple times.
Iâll let you know if we figure out why and if we can fix it.
It was due to the Temp3 sending Thermostat reports on interval, a function we added to ensure statuses are up to date if something were to happen and a message gets lost.
A check was added so it does not retrigger the flowcard if the new report has the same state as the previous message.
Updated version can be tested from the same link
Thanks!
I start some tests with this new version but I already noticed that when the state becomes cool , it is reported as idle (heating and idle states are ok)
You perfectly solved the problem with cool state but now I have the same pb with heat state that is not reported
Are you changing states very quickly?
Iâve done some preliminary testing, and it seems to be working fine on my part.
I know that if a lot of changes on the same device happen at the same time, it might cause issues.
II restart the App and it seems to work now.
Thanks
