Most of my network is Zwave and I am far less sure of how my ZigBee mesh works as far as neighbors are concerned but I would still look at how your devices are situated and who they might be taking to. (That sentence deserves a TL;DR)
Perhaps @mike.maxwell could comment on how to read the
http://hub_ip/hub/zigbee/getChildAndRouteInfo results so we can all learn something.
@zarthan and @mike.maxwell
I have removed all the Iris V1 devices from my setup. As soon as the Hubitat finishes rebooting, I am going to try pairing the ERIA button controllers (can't really call them switches) again. If the system behaves, then the problem would likely be in how the Iris V1 devices interface with the system. If the problem recurs, then it is likely something else entirely.
Initial test: No Iris V1 devices on Hubitat Zigbee mesh.
Connected both ERIA buttons.
Initial tests are positive with the lights responding much faster than before to button presses. Now to see if everything else stays connected or whether things start dropping off the network again.
Good luck with this. I have my fingers crossed because that always helps. 
I have the Lightify 4 button switch and have no issues with my Zigbee network. It has been solid since the changes were made for the @srwhite issues. But I have no Iris V1 devices. I do have V2 and V3 devices.
1 Like
I just got home and hit the button on the first ERIA to turn on the lights. It took about 8 seconds with the light flashing green, then red, then green. The same thing happened with the second switch. Again, once I have pressed a button and "woken up" the ERIA, subsequent button pushes do not have this delay. This is after removing all the V1 devices. However, this time, it appears like all my other devices have stayed connected and working.
I have taken advantage of the current sale on HE hubs $89 plus tax with free shipping on the Hubitat site. It should be the C5 hub. That will be my primary hub when it arrives and will have all my home security items. My current C4 hub will than have all my home automation devices. Hopefully, that will solve the issues I have been having.
Update: This morning I tried the ERIA devices again. They behaved as expected with response of less than a second. I have not clue as to what happened to cause them to behave properly this morning. I did add in two Iris V1 smart plugs, SPG-800 but not the motion sensors or contact switch that I had hooked up. This morning, I will try connecting the two V1 motion sensors. If it continues responding properly, I will have ruled out them as a problem. If so, I will try the V1 contact sensor. If that works, I will be left with a mystery as to why it was misbehaving before and is behaving now. I also will have reduced the need to connect a second hub at this time so the one I ordered will be a spare.
I added the two V1 motion sensors this morning. As of this evening, things appear to still be working well. I was going to add the V1 contact sensor, but will wait until the morning to be sure.
This morning, I checked and the ERIA devices were working great. I added one V1 contact sensor and tested the ERIA again and encountered the problem of delayed reaction. It appears that the Iris V1 contact sensor I had connected is the problem device. @zarthan @mike.maxwell
1 Like
nice work!.
Was this particular sensor migrated from your Iris setup?, or a new to you device...
And if new to you, was it used?, or NIB...
Unpaired from Iris, factory reset, then paired with Hubitat. I bought it originally.
I suspect this was the problem I was having when I tried the Sylvania Lightify 4-button switch controller as well. I have 4 of the V1 contact switches that I bought for use with Iris. They were used with the V1 hub, migrated to the V2 hub, unpaired and factory reset. They are now sitting in a bag along with 2 V1 keyfobs. My wife likes the V1 keyfob better so I may give that a try again to see if it will be okay or cause similar problems. Since I am fairly confident that this issue is resolved, I ordered another ERIA 4 button "wireless dimming switch." If I had known, I would likely have been able to keep the Sylvania device, but that is a moot point as they were already returned.
Edit: I ended up having to remove the V1 motion detectors again also. They had stopped responding this morning when I had installed the contact sensor but I did not notice it until this evening. I will likely try re-pairing them again and see if they stay working without the contact sensor interfering.
Edit: I am still having issues with the ERIA with delayed reaction. I also have noticed that the tile on my dashboard seems to be getting out of sync with the proper status of the dimmer switch. If I change it with the ERIA, the tile will not change. I have now removed all Iris V1 devices from my Hubitat. I have rebooted the Hubitat again and I will see if it is now stable.
Also, I have received my C5 hub that I ordered. I will begin to transition all Iris V1 devices to be on one hub which will be my home security hub and to put the other items on the other hub which will be my home automation hub.
@mike.maxwell @zarthan @bertabcd1234 Continuing this saga, I purchased a second hub. I removed all Iris V1 devices from my first hub which will remain my primary hub (C4). The new hub (C5) now has two Iris V1 motion detectors and two Iris V1 smart plugs installed. Hub link/Link to Hub is installed and working.
My ERIA smart dimmer switches appear to be running great now that there is no Iris V1 device on the same hub. Having them on the second hub does not appear to interfere with their operation.
Bottom line analysis seems to indicate that something in the way the Iris V1 devices communicate interferes with the smooth operation of the Zigbee mesh. Having them on their own Zigbee mesh seems to be the current best answer.
1 Like
I got one of the ERIA Dimming Switches (Remote) and have it configured as in the pic. I have an ERIA CT bulb that I am using to test with. The on and off work fine but if you use up or down dimming it does not do anything using the 'held' as in the pic. It is configured in the Button Controller.
Anyone get the 'held' part to work or is the Button Controller configuration wrong?
Go to the device page for the Eria bulb. Do you see startLevelChange and stopLevelChange buttons (commands)? If so, do they work as expected? Pressing the "start" one should begin dimming in the specified direction, and "stop" should stop it there. If the answer to any of these is "no," your configuration won't work because the device doesn't support those commands, so you'll have to use "adjust dimmer" (with a step up or down) instead.
Otherwise, it looks like your configuration should work. However, I'd recommend adding a "stop raising/lowering" on button 2 and 3 release, otherwise all you'll do is dim the bulbs all the way up or down. By adding this, they'll just dim as long as the button is held.
If all else looks good, have you verified that the button is actually sending "held" events? The logs or event history should show this. You do have to hold the button down foe longer than I've seen on any other button device (probably about 1 second), otherwise it only sees a push. If it doesn't register, try pressing the "Configure" button--you shouldn't have to if it chose the right driver when paired, but it can't and did help me once, but I think that was a now-fixed bug.
Thanks @bertabcd1234, I do see those commands in the bulb device page and they do work. I can raise and lower them but like you said it goes from full to lowest with down and lowest to full with the up button. I put in the stop changing on release and it is very tricky to get it to stop somewhere in the middle, but it works.
Thanks, I tried this approach and it works. A lot of button pushes but not a problem.
You could do both: "adjust dimmer" on button 2 and 3 pushed, and what you tried first with the start/stop level change on held. This device sends either a "pushed" event or a "held" then "released" event for buttons 2 and 3, depending on how long you hold them down for, so all could work. Then you can press the button to precisely dim it by your specified amount, or you can hold it to effectively dim while held.
Yes the only tricky part is how long you hold it down but both ways do work. I didn't think of trying to have buttons 2 and 3 do held, released and pushed +10,-10.
@bertabcd1234 Something changed on the device page for the ERIA Dimmer. It used to show the Brightness Level under current states but now has disappeared when I set it up as the pic below.
Also I see in the device page for the dimmer it has a duplicate for In Use By. Why does it show the same thing twice?
The dimmer is just a button device and should have never shown level. You should only see that on the bulb. If you were using a different or custom driver before, you may have seen it then.
For the duplicate apps, clicking into each should take you to that app. You can remove the one you don't want, assuming they are different (check the URLs if you're not sure). The exact same app twice would probably be a bug. If you started setting up one app but never finished, it might be "orphaned" and will get automatically cleaned up soon enough, or at least that wasn't the case in the hub's early days--not sure if that has changed.
Yea, my bad I should have said the bulb. The bulb has the brightness by the way so all is good.
The first app turned out to be started but unfinished. I deleted it and that fixed that. So thanks for the reply.
