Off topic a bit, but is the zwave stick which comes with hubitat able to be used with a PC for say Hass.io?
Wanting to test a couple of features see if I'll use alongside Hubitat
Device information and pairing is stored on the stick. Plugging it into another system may wipe everything on the stick out forcing you to repair everything when you reconnect to hubitat.
I don't think you would lose anything but I would be very careful. I have an Aeon Zstick attached to a HomeAssistant virtual machine and added as a secondary controller to Hubitat.
I normally have Open Zwave Contol Panel running but if I shut down OZWCP and start-up HA, all the devices in Hubitat show up in HA. I haven't tried actually "adding" anything in HA from what is available on the stick. In my situation, as far as HA is concerned, the stick is not Node 1. In your case, the stick would be Node 1 so you should have no trouble but again be careful.
When in OZWCP I can control the lights, switches etc. and I can continue to control them even when I shut down the Hubitat hub. I should get another switch or something and add it through OZWCP and see if I can control it through Hubitat.
I don't know what you have in mind with HA, but I would leave Zwave and Zigbee with Hubitat. There are lots of other services that you can run on HA and perhaps use MQTT to tie things together with Hubitat And one more time, Be careful.
1 Like
Hey Zarthan, how did you go about adding the Aeon stick to Hubitat? I purchased one so I could to firmware updated and analysis, but can't get it to pair with my system... I keep getting the dreaded "Initializing" screen forever... I actually think there might be an issue with my hub as it doesn't seem to want to pair any z-wave devices lately...
Anyway, does it show up in Hubitat as a device?
Yes:
Because I have 2 hubs with ZWave enabled, I join my Aeon ZStick to one, which sends it all the current DB and then I back that up. Then I join it to my other hub, which clears the Aeon ZStick first, then back that one up.
The Device in the first hub is now an Orphan, so usually I delete them in an hour or two, and let the orphan process in Hubitat do it's thing.
Any particular way you got it to finish pairing? Could be an issue with my hub, but mine never finishes initializing...
I've seen reports of initializing woes.. but as it turns out, I haven't added or changed anything on my set of hubs in a couple weeks, maybe a month. No need to do ZWave Stick backups... yet.
I hope to be completely lucky and be on the 'improved' Firmware by the time I need another Z-device. 
It has been a while since I added the Zstick to the hub but I don't remember that I had any difficulties. It won't pair as a specific device as @csteele mentions.
Coolio... I havn't tried anything since the latest update... I have some new sirens coming this week, so I'll be adding them (hopefully). I'll try to add my stick again...
Are you using OZWCP for analysis?
@csteele I think you said you use or have OZWCP available. The next time you pair your stick, try shutting down the HE hub and then turning lights on and off through OZWCP. The fact that I can control lights while the HE hub is off, suggests that the stick is indeed a secondary controller and hub migration, failover, etc would be possible.
I primarily use OZWCP for the Zwave logging and collecting hop and neighbor information.
Oh.. I KNOW this.. I came to Hubitat-ville a year ago with 4 Hubs joined on a single ZWave network. I know with certainty what it's like... 
Turning on/off lights.. basically the Commanding side.. is absolutely functional. What's deficient in that world is sensors. Contact Sensors for example. Some of the oldest tech in the ZWave world. They send their messages to the Primary hub, only. You can poll them, which I did 2-3 years ago, during automations. They respond back to the querying hub.. no problem.
Been there, done that extensively, don't want to go back. I like my 3 hubs and HubConnect.
I don't care about multiple hubs. I would just like a way to keep a working hub should one fail.
A bit of a dumb question here since nobody else seems to have this problem.
But once the Homeseer Z-Stick is known to Hubitat elevation, what device TYPE do I assign to it?
It didn't pick one up as it was being included in my devices and I cannot find anything that looks like "secondary controller" or "Homeseer z-stick".
Device.
Thanks Ryan. That was what I was looking for.
I ended up having to just use Z-Flash standalone anyway. In the secondary controller mode it could see a bunch of my Jasco switches but it positively refused to pick up the Leviton switch that was the main driver for doing a firmware update.
Standalone it joined to the Leviton no problem. Took probably 30 minutes to actually do the update for the one switch and I'm done. Switch finally responds properly to the Hubitat after re-joining to it.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
