I'm having an early spring clean of my "box of many gadgets". If I can get them working with HE I'll keep them, if not they are going on Ebay.
I'm currently testing a Hortsmann ASR-ZW. It's a heating controller designed to work with the HRT4-ZW Thermostat, but is also a Zwave Relay/Switch in it's own right. If I can get it working it would be better than my current heating switch (a simple Zwave switch module) as it has easy to access manual override buttons on it and looks a bit more professional than my module in a plastic box solution.
I have got it paired to HE OK. I have tried various generic drivers and a modified ST DTH but the one that has most success is the Generic Zwave relay. Using that I can turn it on and off from HE, but if I use the manual switches on the unit it doesn't report back to HE unless I hit refresh on the driver page.
So I don't think it's far away from working perfectly, can anyone suggest a way to get over the line on this and get it to report back to HE correctly?
@mike.maxwell Any thoughts on this Mike? Do you think a driver change would be able to get this to automatically send it's local switch changes back to HE? At the moment I'm using RM to refresh it every 10 minutes which is working OK, but it would obviously be cleaner to not have to.
Pressing poll/refresh has no effect. The device is reported as being ON, and if I use hubitat to turn it off then back on again, it quite happily loses the red light and clicks the boiler into action, working fine for maybe another 24 hrs. I do seem to notice this in the morning, but that may be coincidental.
Any thoughts please? My gut tells me it's C7 related. I use wifi/zigbee for the majority of my devices and have read horror stories about the zwave issues on the C7.
These things have a fail-safe mechanism. If they don't hear from the system in x minutes they think the system has failed and it's time to shut down to avoid the heating system running forever.
in the app I use to turn the switch on/off I have a 6 minute wake-up and the app resends the last on or off as appropriate...... to be sure to be sure...... This way the fail-safe never kicks in.
Ah... Quite possibly. That might explain why it's happening at approx the same in the morning, when the heating has fired up and been left on for a while to initially heat the house for when we're waking up.
Magic, thanks simon. Couldn't find a mention of that in one of the manuals I downloaded. I can't believe that this is (hopefully) the source of my niggles. I've been troubleshooting a little for quite a while now, on and off, and presumed it was a timing issue with my boiler switch webcore Piston (something trying to switch it on occasionally whilst something else was trying to switch off and getting stuffed in the process) or more likely, a comms issue. Which didn't make sense with the regularity of the error.
As I said, colder now, so this is the first time I've really made use of schedules pre wakeup, so thought it may have always been a limitation/error within my system and I hadn't used it extensively enough to trigger it.
Adding a while loop to webcore to see if this vanishes. Either way I probably owe you a curly wurly for that