greensha

I'm now leaning towards it being a bad Z-wave dongle. I repositioned the dongle to another USB port on the eisy and rebooted the eisy. I then tried to add a thermostat. It was partially successful. I could see the thermostat in the device tree, but there were no options to adjust any parameters (either in the Thermostat device or the device responder - that useless device that gets added with most Z-wave devices) I was able to successful exclude the thermostat from the eisy and then I tried re-adding it. Here's what I got after re-adding" So it got a bit more in terms of parameters. I couldn't do anything with them though. I tried another exclude which failed. I moved the eisy from about 10 feet away to about 15 inches and tried again, but no luck. Prior to all this happening, the devices were working perfectly with absolutely no communication issues. I really don't think it's a range issue, otherwise it would have manifested itself prior to this.

Either I've got a batch of devices that all went bad at the same time, or I really have no idea what I am doing. I deleted a couple of a the Zooz 4-in-1 700 sensors from the device tree in the eisy. I was able to factory reset and then add them back - that looks like it worked. I took them back upstairs to check they would work there and they both showed the green "1011" tag. I tried waking them up per the Zooz instructions and writing updates, but that didn't work. There was no data showing in the motion detection or other data fields in the admin console. I tried to exclude them, but there was no evidence of them being seen by the eisy (at this point, I had transferred the eisy upstairs). I deleted them again and tried a factory reset - not sure if this was successful as the Zooz devices don't seem to be reliable/consistent with the LED flashes. No matter what I try, I am unable to get the eisy to respond to them. I then switched my attention to the thermostats that had lost contact with Z-wave. I did a factory reset and then tried to add one back. No luck. The eisy was about 15 inches from the thermostat at this point. I tried another thermostat after resetting that, but again, nothing. I tried with "Secure Inclusion" turned off, that didn't work. I then tried with the mobile app, again nothing. I've got ticket in to UD, but I've not heard anything back. Here are the last logs from trying to add the sensors: [2025-04-06 11:35:47.193] [I] [...] Adding job: Enable Smart Start [2025-04-06 11:35:47.204] [D] [...] SENDING: ( 01 04 00 4A 09 B8 ) [2025-04-06 11:35:47.205] [D] [...] RECEIVED ACK [2025-04-06 11:35:47.205] [I] [...] Job 0x4a (Enable Smart Start): Done [2025-04-06 11:35:47.205] [D] [...] Job 0x4a (Enable Smart Start): success [2025-04-06 11:35:47.205] [I] [...] Removing job: Enable Smart Start [2025-04-06 11:35:49.446] [I] [iox] ZMatter Rest Command 2 : connected=T enabled=T [2025-04-06 11:35:49.446] [I] [...] Adding job: Remove node from network [2025-04-06 11:35:49.448] [D] [...] SENDING (cb 0x9e): ( 01 05 00 4B C1 9E EE ) [2025-04-06 11:35:49.450] [D] [...] RECEIVED ACK [2025-04-06 11:35:49.452] [D] [...] RECEIVED: ( 01 07 00 4B 9E 01 00 00 2C ) [2025-04-06 11:35:49.452] [D] [...] SENT ACK [2025-04-06 11:35:49.452] [D] [...] SETDATA controller.data.lastIncludedDevice = Empty [2025-04-06 11:35:49.452] [D] [...] SETDATA controller.data.lastExcludedDevice = Empty [2025-04-06 11:35:49.452] [I] [...] Job 0x4b (Remove node from network): Ready to remove - push button on the device to be removed [2025-04-06 11:35:49.452] [D] [...] SETDATA controller.data.controllerState = 5 (0x00000005) [2025-04-06 11:35:49.452] [I] [iox] [CM_CB] Current State = 5 [2025-04-06 11:36:07.355] [D] [...] Job 0x4a: deleted from queue [2025-04-06 11:36:07.366] [D] [...] Job 0x4a: deleted from queue [2025-04-06 11:36:07.377] [D] [...] Job 0x4a: deleted from queue [2025-04-06 11:36:17.700] [I] [iox] ZMatter Rest Command 5 : connected=T enabled=T [2025-04-06 11:36:17.700] [I] [...] Removing job: Remove node from network [2025-04-06 11:36:17.700] [I] [...] Adding job: Remove node from network [2025-04-06 11:36:17.705] [D] [...] SENDING (cb 0x00): ( 01 05 00 4B 05 00 B4 ) [2025-04-06 11:36:17.706] [D] [...] RECEIVED ACK [2025-04-06 11:36:17.706] [I] [...] Job 0x4b (Remove node from network): Stop done [2025-04-06 11:36:17.706] [D] [...] Job 0x4b (Remove node from network): success [2025-04-06 11:36:17.706] [I] [...] Removing job: Remove node from network [2025-04-06 11:36:17.706] [D] [...] SETDATA controller.data.controllerState = 0 (0x00000000) [2025-04-06 11:36:17.706] [I] [iox] [CM_CB] Current State = 0 [2025-04-06 11:36:17.706] [I] [...] Adding job: Enable Smart Start [2025-04-06 11:36:17.717] [D] [...] SENDING: ( 01 04 00 4A 09 B8 ) [2025-04-06 11:36:17.719] [D] [...] RECEIVED ACK [2025-04-06 11:36:17.719] [I] [...] Job 0x4a (Enable Smart Start): Done [2025-04-06 11:36:17.719] [D] [...] Job 0x4a (Enable Smart Start): success [2025-04-06 11:36:17.719] [I] [...] Removing job: Enable Smart Start

I've tried every which way. Putting the device in linking mode first, selecting "remove a device" first. I've reset the device and tried again. As far as I can tell, the Z-Wave device isn't seeing anything. To clarify what I said earlier. The night before last, I was able to reset and re-add two plugin modules (dimmer and on-off switch) after first resetting them and then adding them. At that time, the eisy was in its usual place in the basement on my network rack. That is quite a long way from the devices upstairs. I am now upstairs with the eisy (and the Z-Wave module plugged in of course) connected to power and to my network. I can reach the admin console, so it looks that that part is correct. The devices I am trying to add back now are some Zooz motion sensors and Trane thermostats. All these devices worked perfectly until the "glitch" happened. I can't tie the glitch to any particular event. All the Insteon devices are working with out any issues.

Yes, that's the module I'm using. Here is the "About" information that shows the 21100 after the Z-Wave module. Not sure if that is significant though.

The firmware and UI are both v5.9.1. The Z-Wave module is 21100. I've brought the eisy upstairs to within a few feet of the devices that are not working. I've tried removing them from the Z-wave network, but the dialog box just sits there with the "Listening for Z-Wave devices" dialog box. Here is the Z-Wave log when I tried to remove then re-add a 4-in-1 Zooz motion sensor: [2025-04-03 13:31:28.249] [I] [iox] ZMatter Rest Command 5 : connected=T enabled=T [2025-04-03 13:31:28.250] [I] [...] Removing job: Remove node from network [2025-04-03 13:31:28.250] [I] [...] Adding job: Remove node from network [2025-04-03 13:31:28.258] [D] [...] SENDING (cb 0x00): ( 01 05 00 4B 05 00 B4 ) [2025-04-03 13:31:28.260] [D] [...] RECEIVED ACK [2025-04-03 13:31:28.260] [I] [...] Job 0x4b (Remove node from network): Stop done [2025-04-03 13:31:28.260] [D] [...] Job 0x4b (Remove node from network): success [2025-04-03 13:31:28.260] [I] [...] Removing job: Remove node from network [2025-04-03 13:31:28.260] [D] [...] SETDATA controller.data.controllerState = 0 (0x00000000) [2025-04-03 13:31:28.260] [I] [iox] [CM_CB] Current State = 0 [2025-04-03 13:31:28.260] [I] [...] Adding job: Enable Smart Start [2025-04-03 13:31:28.271] [D] [...] SENDING: ( 01 04 00 4A 09 B8 ) [2025-04-03 13:31:28.272] [D] [...] RECEIVED ACK [2025-04-03 13:31:28.272] [I] [...] Job 0x4a (Enable Smart Start): Done [2025-04-03 13:31:28.272] [D] [...] Job 0x4a (Enable Smart Start): success [2025-04-03 13:31:28.272] [I] [...] Removing job: Enable Smart Start [2025-04-03 13:31:34.707] [D] [...] Security S2 send timeout event [2025-04-03 13:31:34.707] [I] [...] Job 0x13 (SwitchBinary Set to node 35): Security S2 failed to prepare S2 packet [2025-04-03 13:31:34.707] [D] [...] Job 0x13 (SwitchBinary Set to node 35): fail [2025-04-03 13:31:34.707] [I] [iox] [ZW-FAIL 00037 35.0 ] [ZY035_1] Binary Switch Set val=0 duration=255 [2025-04-03 13:31:34.707] [I] [...] Removing job: SwitchBinary Set to node 35 [2025-04-03 13:31:44.553] [I] [iox] ZMatter Rest Command 1 : connected=T enabled=T [2025-04-03 13:31:44.553] [I] [iox] ---- Start Adding Devices - S2 Standard --- [2025-04-03 13:31:44.553] [I] [iox] [ZWAVE-INCL-S2STD] Start Include with S0/S2 or non-secure [2025-04-03 13:31:44.553] [D] [...] SETDATA controller.data.smartStart.includingDSK = byte[0] [2025-04-03 13:31:44.553] [D] [...] ( zero-length buffer ) [2025-04-03 13:31:44.553] [I] [...] Adding job: Add/re-include node to network [2025-04-03 13:31:44.553] [I] [iox] [ZWAVE-INCL-S2STD] Added 'CommandAdded' callback 0x205504038e8 [2025-04-03 13:31:44.562] [D] [...] SENDING (cb 0x82): ( 01 05 00 4A C1 82 F3 ) [2025-04-03 13:31:44.564] [D] [...] RECEIVED ACK [2025-04-03 13:31:44.566] [D] [...] RECEIVED: ( 01 07 00 4A 82 01 00 00 31 ) [2025-04-03 13:31:44.566] [D] [...] SENT ACK [2025-04-03 13:31:44.566] [D] [...] SETDATA controller.data.lastIncludedDevice = Empty [2025-04-03 13:31:44.566] [D] [...] SETDATA controller.data.lastExcludedDevice = Empty [2025-04-03 13:31:44.566] [I] [...] Job 0x4a (Add/re-include node to network): Ready to add - push button on the device to be added [2025-04-03 13:31:44.566] [D] [...] SETDATA controller.data.controllerState = 1 (0x00000001) [2025-04-03 13:31:44.566] [I] [iox] [CM_CB] Current State = 1 [2025-04-03 13:31:48.418] [D] [...] Job 0x4b: deleted from queue [2025-04-03 13:31:48.429] [D] [...] Job 0x4b: deleted from queue [2025-04-03 13:31:48.439] [D] [...] Job 0x4a: deleted from queue [2025-04-03 13:31:54.855] [D] [...] Job 0x13: deleted from queue [2025-04-03 13:32:52.098] [I] [iox] ZMatter Rest Command 5 : connected=T enabled=T [2025-04-03 13:32:52.098] [I] [...] Removing job: Add/re-include node to network [2025-04-03 13:32:52.098] [I] [...] Adding job: Add/re-include node to network [2025-04-03 13:32:52.108] [D] [...] SENDING (cb 0x00): ( 01 05 00 4A 05 00 B5 ) [2025-04-03 13:32:52.109] [D] [...] RECEIVED ACK [2025-04-03 13:32:52.109] [I] [...] Job 0x4a (Add/re-include node to network): Stop done [2025-04-03 13:32:52.109] [D] [...] Job 0x4a (Add/re-include node to network): success [2025-04-03 13:32:52.109] [I] [...] Removing job: Add/re-include node to network [2025-04-03 13:32:52.109] [D] [...] SETDATA controller.data.controllerState = 0 (0x00000000) [2025-04-03 13:32:52.109] [I] [iox] [CM_CB] Current State = 0 [2025-04-03 13:32:52.109] [I] [...] Adding job: Enable Smart Start [2025-04-03 13:32:52.120] [D] [...] SENDING: ( 01 04 00 4A 09 B8 ) [2025-04-03 13:32:52.122] [D] [...] RECEIVED ACK [2025-04-03 13:32:52.122] [I] [...] Job 0x4a (Enable Smart Start): Done [2025-04-03 13:32:52.122] [D] [...] Job 0x4a (Enable Smart Start): success [2025-04-03 13:32:52.122] [I] [...] Removing job: Enable Smart Start I don't see any obvious error messages there, but I'm not really sure what I should be looking for. The dialog box gave no indication of anything happening. Thanks!

I've recently had a problem with Z-wave which I think it might be related to a transient eisy issue. A few weeks ago I noticed that a Z-wave plugin module that I used to control some drapes had stopped working. I figured the module had gone back as I was unable to delete it from the network. I tried to use another plugin module that had already been added to the network, but wasn't currently in use, but I couldn't get that to work either. I just assumed that I was forgetting how to go about adding and deleting Z-wave devices and put them aside to deal with later. Fast forward another couple of weeks - I noticed that the Z-wave thermostats on the upper floor were not responding. Do have some Z-wave motion sensors on that floor that are working. So something must have happened. I have a fairly recent system backup, if I restore that will it restore my Z-wave devices, or am I better off just readding them? Thanks!

I did eventually get everything working. It turned out that the main issue I was having what that the bulb wasn't actually registered in the Hue plugin, but the room that it was in was registered. I was mistakenly trying to send commands to the room rather than the device. Once I realized that and was able to add the Hue bulb to the plugin and resynchronize the eisy with the plugin, everything worked as expected. In short, you can use a keypad (in this case, I'm using an i3 keypad) to dim up and down on alternate press-and-holds just as @oberkc stated. Enrolling the devices directly as Zigbee devices doesn't work as well as some features are missing. Most notably the ramp rate when the device is turned off. Hopefully, this will get fixed at some point. The meta problem with all this is the significant lack of accessible, accurate, complete and up-to-date documentation. Sure, it's mostly all there somewhere; but some is in forum posts, like this one. Sometimes it's buried in a wiki page and on occasion nowhere to be found.

I don't often use the dimmer feature, but it's important that it works when needed. I do have some other lights that just transition from one level to another based on a schedule, I can probably use Hue bulbs in those. It just irks me a little that it works so well with the other Zigbee devices that I have and not with the Hue bulbs. I can't help but think it's a programming issue with IoX rather than a intrinsic limitation of the Hue devices.

That's why I gave up on the programs. I had originally tried that with the CCT controller but found that putting it in a scene worked very well. I don't seem to get the same behaviour from the Hue bulbs.

I've tried using programs to control the Hue lights, specifically trying to get them to fade up and down, but this doesn't work (or at least I've not been able to figure out the correct commands to use). I've put them in scenes and again, this doesn't work. I've tried both with the Hue plugin and directly linking them to the eisy. If the bulbs were linked directly to the eisy, they were first deleted from the plugin so that there was no potential conflict.

I am using the Insteon dimmers to control them via scenes or programs. They will not be connected to the Insteon dimmers via the load wire, they will be connected directly to the line wire in the junction box. The Insteon dimmers will not be controlling the Hue bulbs directly.

No, I should have said. The Hue bulbs have power 100% of the time. I am using the Insteon dimmers to control them via scenes (or programs if that will work, but so far I've not been as successful with programs).

I would love to convert my old incandescent lamps to LED lamps, specifically Hue (because that's what I have a few of). I have exclusively Hue bulbs in my basement (set up as a bar and TV room) and they are currently recognized by the eisy via the Hue plugin. However, these lights are manually controlled as and when needed. We are renovating the kitchen on the main floor of the house and currently all the bulbs on that floor are incandescent and control via Insteon switches and plug-in modules. These lights are also on a series of timers that turn the lights on in the evening and then gradually dim as it gets later in the evening. As a test, I've tried replacing a couple with Hue bulbs linked directly to the eisy and while they work ok on the scheduled timers, I have difficulty controlling them manually if needed. I can set a ramp rate for each Hue bulb, but that only works when they are turned on. The ramp rate is instant when they are turned off. However, I can toggle them on and off and the off ramp rate works ok then. If they are controlled by the Hue plugin, the ramp rate works as expected. The other problem is that if I put then in a scene that is controlled by an Insteon dimmer, I can't get them to fade up or down. This is the case whether they are linked directly to the eisy or via the Hue plugin. I have a Zigbee CCT controller that I and going to use for under-counter LED lighting. I can link that directly to the eisy and it works just like another Insteon device when it comes to fading and ramp rates, so I know it can be done. Am I doing something wrong, or is this something that will be added down the road?

Thank you! I look out for the update.

I have my lights schedule to dim at various times in the evening. For the past two nights, the 9 o'clock program that was supposed to dim the lights has not worked. The first time it happened, I used the UD mobile app to trigger the "Run Then" option for the program which then ran the program and the lights dimmed. Last night, when the same thing happened, I triggered the "Run Then" option and got the following error message "Could not get Variable Params". I resynced the mobile app. Rebooted the eisy. I resynced again. None of these steps would make the error go away. I used the IoX Launcher to bring up the Java interface and I was able to trigger the program correctly then. I can control the devices on the system with no issues, so I know it's not a communication program with between the eisy and UD Mobile. Any thoughts on how to troubleshoot? Thanks!

I am trying to figure out how I can use my existing scenes, which gradually dim the lights in the house as it gets later in the evening, to set all the devices in the scene to their set levels instantly. When I am not home, most of the lights stay off (based on state variables tied to motion detectors). If I come home at night, I would like the house lights to come on at their appropriate levels straight away. The inefficient way to do this, would be to have two scenes for each set of light levels. One would decrease the light level gradually, the other instantly. I've tried using "fast on", but that just sets all the lights to 100%. Each scene has around 20 devices. Am I missing something obvious?

I'm trying to get away from having multiple boxes control things. I currently use the Hue hub for all my basement lights, but it's not very flexible. The rest of the house is controlled by the eisy and Insteon. I'm using incandescent bulbs with the Insteon devices and I'm trying to migrate to LED bulbs for the power saving.

This worked. Thank you!

I have been trying to add a Hue bulb to my eisy. I followed the directions found here https://www.universal-devices.com/nohub-hue/, but the bulb is not added. I am running 5.8.3 on the eisy and my UD Mobile app is version 1.1.61. When I try to add the bulb, which is powered on, using the app, I see a dialog box appear in the eisy console (see attachment) but that's as far as I get. I cycled power to the bulb and tried again (several times) with the same result. The bulb is right next to the eisy. I do have the dongle attached and can control Z-wave devices without any issues. Any ideas?

I'm pretty sure this question has been already asked and answered, but I can't find it anywhere. What can you do with all the extra "devices" that are added with a Z-wave device? I know some of them contain extra information about sensors, etc, but what about the the Scene Responders and Assoc Only devices? Thanks!

Is it possible to batch add devices to a scene and then write all the links? This would save a lot of time if possible. Thanks!

I want to change some of the controllers in my scenes to responders (mostly KPL buttons) so I can better control their actions with programs. Is there a way to change them in the scene or do I have to delete them and re-add them as a responder? Thanks!

Thank you! That did the trick.

I was able to upgrade the eisy to 5.5.2, but it only did the firmware and not the admin console. I can access the admin console if I use the cloud option to launch the eisy. I can't figure out how to update the admin console so I can launch it from the eisy. When I launch the console from the cloud, I do see the migrate to ZMatter-Z-Wave button, but my Z-Wave dongle is not responding. I see that other people are having similar issues, so I guess I'll have to wait until UD sort this out. Thank you!

The ZMatter dongle is plugged into the eisy. I think part of the problem might be that the ZMatter board isn't being recognised by the eisy. The 994i firmware and UI versions are 5.3.3 and the eisy versions are 5.4.5. I don't see a migration button option in the configuration tab. I'm attaching some screenshots that may, or may not, be helpful.