Z-wave Device List

0 views

Skip to first unread message

Melany Odeh

unread,

Aug 3, 2024, 1:53:31 PM8/3/24

to lupensmafa

I am brand new to Hubitat and Zwave - trying to migrate from using and accumulating X-10 devices for 40 years. Anyway, I have successfully installed about 30 devices (module and wall dimmers and switches) over the last couple of weeks, but it's all very new to me. My problem is this - I installed and included a wall dimmer in the mesh, and then uninstalled the device from the wall after an issue arose. I believe I then removed (force "removed") the device. Everything was fine - Device List has the same list of devices as the "Z-wave Details" page. I then later reinstalled the switch in the wall, but have been unable to include or set it up. The device now appears on the Z wave Details page, but not on my Device List. It has no device name, only a "Discover" button - and also an option to "Refresh" and "Repair" in the status column. Nothing happens when I hit "Discover" or "Refresh." If I hit repair, it tells me it has been repaired.

Thank you SO MUCH for your quick reply! I'll remove the switch again from the house wiring this weekend and follow the procedure you outlined. I'll report back with the results. Thanks again! I'm sure I'll have lots more questions about the platform as I move forward.

Yes, these are called ghosts. Any time you have a failed pairing STOP! Check your z-wave devices page for the device. Exclude the device, and as @Sebastien outlined hit refresh till you can remove. Do not attempt to pair anything else until this is done. Then you can go ahead and start pairing again.

Agree 100% - even w/a new protocol to learn (Z-Wave) your description of the events leading up to problem was well beyond noob. You probably saved all of us (you included) an hour of "So what did you do again?" questions.

Finally able to get back to this today. Good call on flipping the breaker. I feel stupid for not thinking of that. Anyway, I did that, refreshed several times, and was then finally able to remove the ghost. I then tried adding it again as a device. When I do so, the hub finds it quickly and begins initializing, but then nothing ever happens. I get the following message - "Found Z-Wave device with id 2C, initializing..." and then time runs out. Any thoughts?

Well - I feel like a nube. I was very proficient with X-10 and had an extremely reliable setup. But I had been using HA Bridge to allow my Alexa devices to control my X-10 stuff. About 55 modules/switches combined. This has worked great for a couple of years, but Amazon keeps changing support for the bridge access, and it finally stopped working. By that time, I was hooked on voice control for everything, so upward and onward. Transitioning from the X-10 interface to Rule Machine, etc., has been pretty challenging. But I'll keep at it.

Got it this time. Ghost showed back up after failure to initialize. I flipped the breaker, refreshed the ghost listing in Z wave settings until it gave me the option to remove, then removed it. This time I went back into Devices and hit Exclude, toggled the switch, and was able to exclude it - referenced as an "unnamed device." Then I was able to add it and configure it normally. THANKS AGAIN to all for the helpful guidance!

Glad you got it. Ghosts are a pain. They will cause a lot of problems with your mesh. Also if you wanna clear things out now that it's fixed. Shutdown the hub from the settings menu, unplug at the wall (not the hub) for 10 mins and power back up. That will clear your z-wave radio. (Can't hurt)

Basically what @ritchierich said. If you go into the instance of MakerAPI that you have set up and exposed devices to Node-RED, you can click on the "Get All Devices", you will get a list of all devices exposed via that instance of MakerAPI.

Just a heads up - I use HE's logsocket to grab the log events using the websocket node in Node-RED. I ran into an issue where the websocket connection was not established when HE was rebooted (but Node-RED was not). I worked around that by creating a flow that redeploys NR flows if there is no log entry in the last 15 minutes. Not sure if this has been fixed or is an issue with eventsocket.

I ran into an issue where the websocket connection was not established when HE was rebooted (but Node-RED was not). I worked around that by creating a flow that redeploys NR flows if there is no log entry in the last 15 minutes. Not sure if this has been fixed or is an issue with eventsocket.

No easy way that I know of. You need to open the suspected devices in the API Browser+, or AWA to find the ID. A few drivers like @philh30 's list the device numbers on the detail page for Z-wave devices in the mobile app.

I had the hub in the room where the Theater fan is located so that route makes sense. The Zooz Zen20 Power Strip is what I am having issues with. I just purchased and installed a Zen72 Dimmer, which is the long range Z-Wave Plus model, hoping to make the powerstrip jump on it by excluding it and adding it back. I figured it would jump on that for a repeater because it relatively close to the power strip. Still had issue.

I move the hub twice and did Z-Wave repairs both times. I found some issues and got those worked out but the power strip is still acting up. However, whenever I put the hub close to it, it works as it should. I thought for certain that it was a direct connection to the hub.

This is not the case with most Z-Wave switches and devices. Most controllers loop through each device on the Z-Wave network and check their status. So the more devices on the network, the slower the status updates. This is a real issue when you want to use switches to trigger other devices. I had three switches. One switch turned on the other two. Worked great. Then I added a bunch of other switches to the Z-Wave network and it slowed down to as much as 30 seconds. Hardly reasonable. Could have been a very costly mistake on my part.

Only for switches that have been made after the Lutron patent expires/expired. All those Z-Wave switches on the market today (non-proprietary) give no feedback to the controller, the controller has to ask for the device status.

So I'm looking at options for motorized shade control. I've noted that Bali shades (they're cheaper than the Lutron) have a built-in Z-wave module. With the introduction of z-wave compatibility to Control4, will there be direct control of these shades instead of using the URTSI bridge, which seems to be not great? I see that there is a Somfy driver, but it's not clear if that applies to Bali.

Thanks. In looking at it more closely, the new Bali Autoview motorized control shades apparently show up in Wink as a standard Z-wave dimmer, giving you percentage control, etc. Given that, i suppose one way to do it is to get a Wink hub for 99 bucks and integrate that with C4.

So would the following module work basically like a Control4 wireless outlet switch capable of turning on/off a light or similar appliance? This seems much cheaper and more versatile than the larger C4 outlet module.

Devices listed here are confirmed to have worked with Hubitat, but this does not mean the device will be guaranteed to work with Hubitat. Support cannot assist you with pairing devices with the hub. Building a proper mesh network with repeaters is required to make most Zigbee and Z-Wave devices work with Hubitat.

Zigbee and Z-Wave devices require the correct drivers to work properly with the hub. LAN and cloud devices connect using the specific integration app listed (or sometimes only a driver) and may require an additional bridge device to communicate.

While most compatible devices work with any model of hub, note that Iris v1 (AlertMe) devices are not compatible with hub model C-8 or C-8 Pro (only models C-7 and earlier). Specific devices below may also have other notes.

While this list includes devices known by Hubitat to work, there are countless other devices users have running on their hubs. Visit our Community Devices Page to see other devices users have running on their hubs. Some of these devices use custom drivers, for which Hubitat does not offer official support but the driver author or manufacturer may.

I'm continually frustrated by the fact that if you look at something in the event viewer that it says the device is zw_004 or similar, but the only way to figure out what that is is to click on each and every device to see.

Right now I'm messing with the beta firmware versions and even though I keep turning freeze nodes on it somehow keeps getting turned off and I get more and more ghost nodes. So for example today I open the AC to find a new node that says ZW 038 Home Security Alarm. So all of my devices have names that say what and where they are...I don't leave the zw038 in the name. So I'm looking for a way to be able to quickly tell what zw038 is.

Okay to answer my own question...after working in the AC I noticed that if you click on the folder named "Network" that it will list all of your devices and in this display is a column named Address which will give the info I was looking for. You can also click on the top to sort. So if I am looking for a zwave device ID I can click the address column to sort and them scroll down and they are listed in order. Same for insteon and node servers.