After reinclusion, does it say it again immediately?
Have you tried removing Unknown nodes?
Hi, The error came directly after inclusion and restart of the device.
After som more testing and more inclusions and more restarts of the device and heatit app, it suddenly works.
I dont know why but it now works. Both units are now talking to my homey device.
Strange, good to hear it works now.
Donāt hesitate to contact us again either here or at post@heatit.com if you run into more issues
Yes it worked,
Updated and reinstalled the app.
@HeatitControlsAB 4.0.9 feedback:
Thanks for the changes!
Measured temperature below the setpoint wheel: Works perfect now.
Alternate between Off and Power Regulator: This also seems to work, it is a great feature which makes the powerreg support more useful. Thanks.
I observe a few issues:
When switching back from Off to Power Regulator, operation mode parameter in advanced settings is shown as off. It works as a power regulator though, so I think the parameter is correctly set to heat but the advanced settings shows the wrong parameter value. Not sure how much of an issue this is, but thought I should note it.
Also, something weird happens. When the slider is set to Off, every morning around 04:10 (arbitrary times between 04:09 and 04:12), the slider is changed to Power Regulator automaticly (but it still behaves as off). I also tested switching to Heat and then to Off before bedtime, and in that case it switched to Heat around 04:10. The āthermostat mode changed toā card fires when this happens (that is why I know the times as I log it). I do not think I have any flows or associations that causes this to happen, are there any ā24-hour checksā or something else in the app that can cause this? I dont know if this is something odd happening on my Homey only. I aim to test this on another Homey to see if the same thing happens, but I need to wait until the occupants are on vacation next week to avoid cold floors 
When I try this it seems to work, are you sure you are waiting long enough before checking? The integration is waiting for a Configuration report from the thermostat before updating the value, so there might be some delays before the report is sent and handled by the integration.
There isnāt any check like that.
We will test it ourselves and see if we are able to reproduce it.
When I try this it seems to work, are you sure you are waiting long enough before checking? The integration is waiting for a Configuration report from the thermostat before updating the value, so there might be some delays before the report is sent and handled by the integration.
I tested now and it updated correctly and instantly. I suspect I only checked this after one of the strage daily thermostat mode changes where the operation mode in fact was off. Thus - not an issue - case closed!
There isnāt any check like that.
We will test it ourselves and see if we are able to reproduce it.
Thanks! I sent a DM with a diagnostics report ID and some example timestamps in case you can see what triggers it. I realized it also happens around 4:10 PM if it did not happen around 4:10 AM. Super strange. Maybe I have a rouge z-wave device doing odd things on the network.
@HeatitControlsAB Recently I have purchased a Z-Smoke Detector 230v for my home. I really like the product and am planning to replace the remaining Nest Protect Smoke Detectors this year.
The main reason to purchase the smoke detector is the integration in my Z-Wave network with Homey. The product works great, the only feature Iām missing is an option to configure the motion alarm cancellation time like most motion sensors do. The default time is too short and sends too quickly a motion cancellation time out to Homey and I donāt see the possibility to change it anywhere. Would there be a possibility to have this feature added for the future?
Example of the motion cancellation option in Homey (Aeotec Multisensor 6 Z-Wave Plus):
Hi,
The Z-Smoke doesnāt support the Configuration Command Class.
Very bluntly, we are not going to make this change on this device.
Hello. After a while the Z-TRM3 no longer talks with my homey. I have tried several resets on the heatit device. After trying a lot of inclusions it will not talk to homey. When including heatit, pressing ācon" homey talks to the heatit device and asks for pin, everything seems fine. After PIN is set, I set where it belongs to and everything seems fine. After a while (30 sec to a minute) I get the timeout Zwavesendcommandtimeout after 30000ms. Is there anything else I can try or is this unit defect?. I have one other unit of the same, that works fine.
Hi, if you are being required to fill a pin when including you are not using out integration.
Using the Pin adds security, and weāve removed this due to a lot of issues using it with Homey.
Please select Heatit Controls when adding the device instead of the generic Z-Wave option
Thanks for your guidance, the unit works now flawlessy. Thanks for the support. 
Good to hear!
4.2.2
The updated app do not work. All my devices is now āoff-lineā. The app is not showing, when reinstall it shows but when trying to restart the app it says ānot installedā
Same issue here also
Hi,
We are looking into the issue and have contacted Homey support.
It works on some Homeys and not others, the only difference from the previous version is the icon for the new Z-Smoke2.
We are not sure what the issue is, but are reverting to the previous version to see if this solves the issue.
Hi
Thanks
Hi,
I would like for you to test the Beta version first and see if this fixes the install issue.
Please let me know if you are able to install this, if that works, I will publish it.
4.2.3 works 
Great!
Iāve published it so it should be live for anyone wanting to try and fix the issue.
