Help with Honeywell T6 ZWave? Partial success..
Hi All!
Recently purchased a Honeywell t6 Pro Z-wave thermostat, and a Zwave dongle to go with it.
I'm running HA in docker, so I spooled up the Z-wave JS UI in a seperate docker container as well. I then added the HA integration for Z-wave and got it talking to the ZwavejsUI
I can tell something went right because the thermostat shows up in the HA integration as "Node 2", but there aren't any exposed entities that have anything to do with thermostat functions; It shows things like "node status", "ping", etc.
Edit: It also shows up as a "unknown manufacturer" and product in ZwavsJSUI
So something is working... just not as a thermostat.
Any help? I'm a few steps away from returning it and just using a shelly relay to short the two wires together.
8 replies
Figured it out! It was as simple as making sure the security keys were generated. I thought I had but they failed to take in ZwaveJS. So for posterity:
Big thanks to @[email protected] and @[email protected] . I learned a ton more because of your input. Oh also matter is no working as is ESPectre across a dozen or so ESP32-C3s I had. So all in all we got some major upgrades done today!
I have this same thermostat and it's been a while since I set it up but I don't remember seeing anything like that. However, with my other 40+ z-wave devices I've definitely seen things like that (especially the unknown manufacturer). Especially if, as an example, power freaks out and I had to redo a bunch of bulbs (thankfully I haven't had to do that in a couple of years).
Here's a smattering of things that I would suggest to try if you haven't already:
Do a reinterview of the node
Reboot z-wave jsui and home assistant
Exclude the thermostat and then factory reset it
Make sure it really is out of z-wave jsui, maybe even after another reboot
Add the thermostat back in and give it plenty of time to be interviewed by the controller
If those things don't work, I would suggest moving z-wave jsui over to being done inside of home assistant, at least for a test just to make sure you can get it working in at least one way.
Good luck!
Great suggestions but it wound up being even more simple and even more stupid: Security keys. Writing a top level note for anyone after right now.
Hey great catch and good job.
I have one, and it more or less just showed up. First question: do you have any other zwave devices active & fully functional? There's a bunch of cheap-ish switches you could get just to validate general network functionality.
It sounds like you might be in reduced power mode. On the thermostat, there should be a wifi icon top-right. If that icon has a little dot at the bottom, it's in 24VAC mode without 24 VAC power. From the manual:
Unfortunately this is my first and currently only z-wave device; I'll snag some "fool proof" ones for exactly what you're saying.
This is a solid lead and I suspect you're right! Although some stuff that doesn't add up:
I think you've gotten me on the right track, but I gave myself another wrinkle. I'm also trying to get matter working for the first time, and in the process of troubleshooting a provisioning, I put my unraid server (with HA) to communicate via IP6 only. It now is no longer online and also inaccessible via a directly connected monitor... So I need to solve that before I can do anything else with Z-wave...
Happy Sunday...
Just want to be clear that Honeywell UI uses the wifi icon (4 stacked circle sectors) on the z-wave thermo to indicate z-wave connectivity, not 802.11. If it's got no such icon on the thermostat itself, then I'd guess that something failed during provisioning, so you ended up stuck with just a couple of parameters.
Sounds like you've got your hands full, either way. Thank god it's a fun hobby and not a job :) Good luck.
Re: Icon: Understood, but still grateful for the clarity! Unraid working proper again, I didn't realize how much there was to Ipv6... another day. Have to take care of some things but succesfully back to baseline. I'll try repovisioning this evening and see what happens! (I'll post here for posterity)