Since 2.2.7 I have been sighting issues with Eurotronic Zwave Thermostat Controller Valves.
The HE Hub that runs these is only managing heating/hot water - and interface for zwave devices which are managed in another HE.
For the last 4 months total stability, the Rules and the TRVs have been working perfectly.
As such has remained 'untweaked', shortly after moving to 2.2.7 it went unstable.
Rules that were run off Triggers stopped working reliably, heating system did not turn on (boiler is a zwave controlled device), direct control of TRV valves were not sent, and finally the TRVs started to show as 99% open in HE but were actually 0% as reported by the cold radiators interface.
Normally the two rooms that need heat at 6am - When the heating zones move to a higher temp form 17c to 21c were not heating up. 80% of the time the rooms were cold when I went down a coupe of hours later.
I placed Tuya zigbee Temp Sensors on the radiators so I could tell if the Radiator was actually on as indicated by HE but was in fact 19C and not the normal 50c when the radiator is heating.
I restored to 2.2.6 yesterday and the heating failed again today.
Is it possible that the zwave controller was updated in 2.2.7 and not restored to previous version ?
I don't think that was touched at all. For giggles, shut down your hub from the settings menu, unplug power (at the wall not the hub), wait about 5 mins and power back up. That will clear the z-wave radio (which isn't done during a regular reboot). See if that clears you up.
I am using 2 Honeywell Z-Wave (non plus) thermostats with the Generic Z-Wave Thermostat driver.
These are heat pumps (heat/cool). When we leave for the day, the heat is set to 66, and AC to 82. When we come home, heat is 70 and AC is 78.
Last week (a few days after the update to 2.2.7) one of the thermostats went from 66/82 to 83/88. These events were recorded in the logs (i.e. the thermostat reported this new setpoint)...but the 4.1 rules engine never changed.
I rebooted the thermostats and the hub and everything has been fine. I just figured a "glitch" until I saw your post.
I have a Rule on the MASTER HE, that sends and shutdown instruction to the HEATING HE - powers off the HE HUB ( using zigbee socket) waits 5 minutes and then reboots it.
I have the MASTER hub ping a few zwave switches to detect if the zwave module is hung up, if it fails the test reboot the Heating HE hub.
I had a similar experience this morning but less frightening: no z-wave response at all and in z-wave repair all nodes failed. After some detailed 'reconstruction' , repairing first the closest nodes and so on, all the devices were reachable again.
There was one device that has the name 'Device' and no specific driver assigned to it that I don't know what it is or where it is but that one also got repaired in the end.
And this afternoon, coming home, the whole thing repeated itself: none of the nodes reachable, all failed. Latest firmware.
Two questions:
What is going on ?
The device type for the device without driver or name which could be the culprit as a 'ghost'-device (but then again, how can it be 'repaired' ??), the device type is 4352, manufacturer 340 but I can't find a list of manufacturers or devide types anywhere which would help me find the unknown device. Anybody has a suggestion for which kind of device this might be ?
Just a newbie here, so, sorry if I did/said/asked stupid things...
Things are getting worse with time. Z-wave repair finds all nodes and routes and 10 minutes later it doesn't find any node anymore. Then "Discover" starts to appear in the device label column in more and more places....
Is restoring a backup a possible solution ?
Things are normal again. after restoring my last backup I could exclude a ghost. turned out to be a POPP dimmer outlet. While searching for the solution of the problem I encountered some other problems like the 'Hub Information'- App that polled for information from the hub every 1 to 2 seconds and 'Action Tiles' which are not in use yet but eat up a lot of CPU-time nevertheless.
Why would you set it that frequently? There’s nothing that it reports that will change that often - 90-95% of the data is static unless you restart the hub, CPU load is a 5 minute calculation span, etc... Personally I would never set it to poll more frequently than 5 minutes, and every 10 minutes is probably nearer the sweet spot for most.
Well, I didn't set anything. I downloaded the driver, installed it and that was what it did. I just discovered yesterday that it was polling the hub so frequently, I didn't even look at the settings, just removed it.
Anyone still having issues with zwave after update? My zwave devices minus my HEMv2. Tried excluding and adding to my other hub and it didn’t work there either. Shows up but no events. Rolled back firmware and it works fine.
Just for clarity these issues were resolved by rewriting the identical Rules that were already in place and working prior to this update and then disabling the old (malfunctioning Rule) and using the new re-written from scratch identical rule.
After I did that all these glitches resolved.
I don't know why it is necessary to re-write rules after an update but it appears it is a requirement.
