greensha

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!