@mike.maxwell, I've been using the aurora double sockets and noticed a few issues.
Firstly they periodically do stop responding and although they do appear in HE I can't control them. So I have to remove the devices, power cycle them and re-add them to get them to work again. Any idea what could be happening here?
Secondly, when I power cycle them I can't just power cycle one socket at a time and instead need to do a whole floor of my house. But when I do that all the other sockets (which are working) lose their light colour settings and all of them shone bright again (even though I've set them to low in HE). Can the sockets keep their light settings when they've been power cycled?
Thirdly, (and probably linked) the sockets randomly default back to their bright light colour (even when no power cycling has occured). In HE is still says the light setting is low or off but it is clearly back to its bright setting. Any ideas why HE and the socket don't sync up?
Lots here, if these are falling off the network, it could be a distance to the hub issue or a bad repeater (ie bulbs)
There isn't really a way of detecting a power reset at the device level, so not possible to reset anything since we don't know anything changed.
Hi @mike.maxwell, just to give you some more details I only have these aurora double sockets on my ZigBee mesh and I have about 6-8 in each room (55 in total across the house) and I don't have any bulbs or other bad repeaters which could cause an issue.
But I am still getting the weekly problem of random sockets falling of the ZigBee mesh (yesterday a socket fell of which is one the closest to my hub and which has another 8 plug sockets within two metres of it). So I don't think this is an issue with the ZigBee mesh and devices at the edge falling off - or do you still think it could be?
Ah I see! So if I do have to power cycle a whole floor of aurora devices (just to readd one) then the device itself factory resets to have the light on full (even though they're still on the mesh and the light is turned off in HE). But as HE doesn't know about the power cycle is doesn't know the light has been turned on. And the only way to turn the light off again is to hit Save Device (even though you haven't changed anything) on every device individually to send the message to the device to turn the light off.
Hmmmm, that kind of makes sense but I'm just wondering whether anybody else has had similar issues on any other devices and found an interesting way to automatically save the device settings when the device factory resets. I'm presuming this is a common problem so time for me to dig through these forums! Unless you have any more ideas @mike.maxwell?
Sorry why are you having to reset them? Have you looked at your ZigBee tables to check for mesh strength, from the amount you have it should be very strong but it's worth checking.
Also how old are they did you ever update them with their hub or ST? If you don't have their hub or ST, I won't be surprised with the amount you brought that if you phones support they would happily send you a hub to update the firmware. The great thing about ZigBee of when you factor reset them you can join them to another hub, do the update if needed then delete or factory reset it again and join it back to HE then it will fall back to the original slot.
Other than possible hitting configure after its joined thats all you should have to do.
Wow how many! I have 3 But I do like them, and plan on getting more.
One of mine has dropped, and just happens to be the furthest from the hub, I haven't re-joined it as yet. Its also one which I keep on full brightness, so I wouldn't know if it had been reset.
I'll re-join it and see how it goes. Shame we cant query the current setting of the brightness to see if its dropped. The mesh here is pretty strong, plenty of repeaters and 3 Xbee3's. So I am surprised it did drop in the first place, even if its the furthest away.
I have contacted support for this, it's apparently "by design, for safety reasons" I don't by that, but there it is. So because of this there is not much @mike.maxwell can do.
The only thing if he's willing would be to add a function to be able to call the update from the driver?
Then after we send a power failure in RM we could call the update on these devices to restore the parameter?
I don't have any of the double sockets, but when I first installed the rotary dimmers I had a similar issue with the blue LEDs on them i.e. if you had a power glitch they'd come on even if they were off. Sometimes I found that the device crashed too and restarted, also turning on the blue LED.
As there was no built in driver for them back then, I wrote my own. What I did was
made a setting for the blue LED (just true / false)
bound the on/off cluster on the blue LED endpoint and configured the on/off attribute to report on state change and periodically every 10 minutes
when an attribute report came in compare it to the setting, if it's on and it should be off, send an off. And vice-versa
This seemed to work well as most of the time the power glitch or crash produces an attribute report of the state of the blue LED, so HE can then take action appropriately. Worse case the periodic 10-minute report handles it.
As I said, I've not used the double sockets but assume they work the same way i.e. a separate endpoint for the blue LED. I assume as well as on/off cluster they must also support the level cluster if you can change the brightness (I've never tried that on the rotary dimmers). A lot of assumptions there so apologies if these are way off the mark ....
If my assumptions are correct then it would be a bit of work for @mike.maxwell to replicate similar in the official drivers, so you'd have to ask nicely!
The double switch is almost what I am looking for, just waiting for a reasonable priced double gang uk socket. Companies don't seem that bothered by it, plenty of options in the US market though.
@sandhufamilia I now have a list of current firmware for all their products, it looks like the ST hub isn't up-to-date with the sockets as from the list it looks like mine are out of date. If we can get yours confirmed that might be your issue.
@mike.maxwell I think I asked before is there a way to request the firmware of a ZigBee device please? The "device" driver gives some information but not the firmware version it seems?
Re outlet indicator sync:
I tried to find an event the Outlets generated when they first powered up, nothing usable...
I tried setting reporting on the level cluster, not supported...
So automating the indicator recovery without setting up some sort of internal polling (which I'm unwilling to do) isn't possible right now.
Platform 2.2.5 will include a new app that will allow setting device preferences in bulk, so if one needs to set/reset these at least it won't be so painful...
I think I remember them saying that you can lock off the physical buttons (child lock) is this possible to be added? My kid started pressing the buttons
Sorry folks been a hectic few weeks and only got back around to looking at this today when another switch (that I regularly use in my automations) stopped working. So I've checked the ZigBee tables and although I now have 69 sockets (part of my full house refurb which I've been doing over the last couple of years!) which appear in my Devices on HE, only 31 appear in the Parent Child parameters (15 on the Neighbour Table Entry, 15 on the Route Table Entry, and 1 which appears on both). So it looks like the other 38 have fully dropped off the Parent Child list which looks to be my issue. The 16 on the Neighbour Table Entry all have a LQI over 249 apart from one at 230 and another at 164 so most look to have a decent connection. And it doesn't appear to be devices at the edge of the mesh which appear to be dropping off - it's totally random!
But my current issue is with loads of these sockets dropping off the mesh (but remaining on the Devices list so as I haven't automations running on all of them I was unaware so many had dropped).
I have (and can) exclude and re-add the 38 again but this looks like a reoccurring problem as I've probably done that 20 times already when I just needed the sockets to work quickly!
I've spent most of my HE experience so far learning about zwave and so does anybody else have any other tips on how to resolve these ZigBee issues?
@BorrisTheCat, do you know how I see what firmware the sockets are on? I can check that also to see if that's the problem
Thanks all for the help!
UPDATE: the one switch which stopped working today was on the Route Table Entry when I first posted this but it wasn't responding. But a few hours later (without me doing anything) it now appears on the Neighbour Table Entry and works just fine. Think I need to do some reading up on how ZigBee meshes work!
I'm still missing loads of devices from the Neighbour and Route Table Entry but I'll need to do some digging before fully assessing the impact of this!
I see the occasional zigbee device disappear from the routing table but they are still working just fine.
For me, I don't even look at the table.
I use device watchdog to monitor my devices. Much more reliable than the routing table.
Just my 2 pence worth.
I tried to use the built in driver "device" and watched the logs when hitting the version button but it wasn't clear. @mike.maxwell said he needs to have a look where they store it so that can work correctly.
So for now as I was just joining, I paired it to smart things and read it from the browser page. Obviously this isn't realistic for all your devices but I would expect that they are all on the same firmware so if one is out they all are.
Personally I would contact aurora and tell them your having issues with them. Don't say there on HE because there not "supported" yet on HE by Aurora, instead mention that you believe they are out of date firmware and wondered if a update would fix your issues. Mention how many your have and I think support would be mad not to send you a free hub to update them.
Alternatively, in the past my contact in aurora (who no longer works there) mentioned a willingness to provide HE there firmware for remote updates. But that would depend on @mike.maxwell and @bcopeland as to whether a ZigBee updater is on the cards soon or at all. Then whether aurora were still willing to send them the files?
Just had another important socket drop off the mesh so I was just about to re-add it but I just re-read this and wondered whether I am doing too much work!
What I do is
Remove the socket from any automations/apps
Press the double switch so it goes into pairing mode (not too sure if I need to do this step)
Remove the device from HE
Flip the fuse switch (which power cycles my whole loft)
Add the device back to HE
Add it back to my automations
It doesn't take too long but when you said you add it back to HE and it 'falls back to its original slot' does that mean I can somehow leave the device in HE somehow and stop doing 1, 2,3,5,&6?
Also, I've contacted aurora support about getting one of their hubs to check the firmware but haven't heard back yet - I'll chase them later this week
Yes sounds like you're doing far too much work there!
Start ZigBee pairing on Hubitat
Initiate pairing mode on the socket (which factory resets it)
Hubitat should say it's found an existing device
Because ZigBee devices are predefined with a unique IEEE address at the factory, they always pair as an existing device if they already exist in the ZigBee coordinator.
But I do like them, and plan on getting more.
