New addition to the FAQ:
Thanks, tried this but it didn’t solve the issues…
I will send my Z-TRM2fx today to Athom for further analysis…
Brief update on the issue with missing temperature reporting.
Athom analyzed the Z-TRM2fx I send them and found a containment to utilize the temperature reporting.
It appears that during the inclusion the device is not reporting all supported command classes (among others the Multilevel Sensor CC) as it supposed to do. I’ll pass this info back to ThermoFloor.
But we found an approach to still “listen” to the reports that the device is still sending, which will be implemented in the next Homey SW release (Homey SW 2.0.5).
Fortunately, I will not require to remove and re-include the devices.
I will be testing this approach with the current devices as soon as possible and if indeed successful, I will be updating the drivers and release the remaining devices.
Tip: for those who have problem pairing the Z-TRM2fx, move the homey as close as possible before trying! (the older TF 021 was pairing without problems at longer distance from Homey)
After 30-40 failed attempts pairing my Z-TRM2fx when homey was placed in other room 7-8 meters away, I moved the homey to bathroom (1 m from thermostat) and it paired on first attempt, then when it`s first paired, distance seems to be no problem
Good luck solving the temp reading issues for Z-TRM2fx
Any progress on the missing temperature reporting @TedTolboom ?
Could anyone here that has experience with Z-Water, create a guide how it is set up in Homey? Preferably with virtual thermostats and not the Z-TRM2fx if possible. Thanks!
Added a bunch of thermostats today. Mostly worked, but got an issue with two of them. Seems like it stopped pairing during
Retrieving command class versions (5/12). . It stopped on that message, then I got an error. When I try to pair again I get
status.already_added. Any ideas? I moved the Homey right next to them as well.
@Hauken, try to exclude the thermostat before you try to pair the thermostat again…
@TTXy: How do I exclude the thermostat? I excluded it from Futurehome before, and the include and exclude-mode on the thermostat seems to be the same.
Try to reset the device. It involved holding in the touch buttons for a while. Cant remember which ones, but you can find it in the manual I had to do it a couple of times to successfully include them.
Go to https://developer.athom.com/tools/zwave and remove your device. Make sure it does not have any power (unplug your power cables) and wait for a few minutes. Then use the remove option from within the developer site.
Any news on the temperature reporting?
I just uploaded v2.1.2 to the BETA branch of the app store; waiting for Athom’s approval.
This update will fix the temperature reporting of the Z-wave thermostat (FW 1.92), Z-TRM2(fx) and Z-Water when you are using the v2.1.2 version of the app in combination with Homey v2.x (!)
See detailed changelog, including actions from user side to get the temperature reporting working:
Please let me know if this is indeed resulting in working temperature reporting at your side.
If this is confirmed, I will promote v2.1.2 to stable.
I have now tested Z-TRM2 (fx) with the v2.12 Beta and the setup as described in change log. I I now receive data on current temperature from floor sensor, but i get no data of consumption of electricity, total power consumption, Active / idle etc. only temperate.
I have three Z-TRM2 (fx) with the v.2.1.2 beta. One was re-included with the updated beta, the other two i just updated the settings as described. I get random read of data on floor temperature, state, power, voltage and power meter. It seems like the data is not updated as frequent as it should. I am still struggeling with the devices freezing and all communication from homey with the devices fail. This happens once every day or two for all three devices. I can still use the devices with the buttons on them. Only way to get them back online is to cut their power for more than 30 seconds by using my fusebox.When they restart they are working. No restart of homey is needed. Not sure if this is a homey issue or the devices. The freezes has been happening since I got the devices, and is not a new problem with the latest beta app.
I am having the same issues at you describe, Christian.
The Z-TRM2 (fx) are “falling” out one by one.
I had the same issue with the same thermostats I my last Wave hub, the FutureHome.
The solution there was to NOT include the thermostats as secure S2, but in S0.
I just want my thermostats to work.
Ted, is there a way to include the thermostats in S0 way? (I did not type in the code/password for the thermostats in Homey)
Bought myself a Z-TRM2fx and got it installed and paired with the 2.1.2 beta app. I run the 2.1.1 SW on Homey. After i paired it i got the correct settings like described in the latest rel. notes for the beta app. Only thing that dont work is the floor temp sensor information that don’t want to play along regardless what i do. Everything else works great even the Power meter.
The temp sensor reports correctly on the device when changing the setting from display setpoint to current floor temp so my problem is like described Before in this thread.
Edit: Did a last resort off doing a factory reset on the unit and bingo that solved it Now everything works
Hi all. I cant seem to get my Heatit Z-Water regulator into Homey. I installed the beta version of this app, choose to add Heatit Z-Water, it just spins for some seconds and I get the timeout error. When I try again, I get the device already added error (something like that). So I reset the regulator (long press inclusion button), and then I can try again, but I get the same errors every time. First timeout, then already added. When I go into app settings, there is no device. But when I go into Homey developer settings I can see now like 5/6 unknown devices from all my previous trues. I cannot remove them. The last one I added, responds ok when I press test
Anyone with an idea what I can try?
My 7 Heatit TRM2fx all lost connection with the Homey within 36h.
The solution was to change the parameters:
Temperature report interval (s) from default 60 to 3600
Meter report interval(s) from 60 to 32000
My conclusion is that the frequent communication of the Heatits overloaded the z wave net sometimes.
I have set my TRM2fx to report interval to 300 sec. The thermostat have been working fine now for over 5 days…