I have had issues lately with my hue lamps doing the same thing on the hue hub. The lamps are controllable from HE, but the Hue says they are not responsive, yet will flash them when the icon is touched. I am thinking there is something going on with the Hue firmware. I never had a problem with this until these last few days.
1 Like
so yesterday a sparkie mate came by to change some light fittings (to fit HA bulbs - yeah im that guy now) but didnt know when he was coming so had the HE powered down all day. When I got home I powered up the HE with all kinds of issues.
Modes werent changing, did that manually and they came back to life.
my yeelights were BUSTED. on the yeelight app when you clicked on, they turned off. When I turned the VS on in the YL app, then power cycled the bulb, then they were the right way round. But then HE couldnt control them. Then when I looked after the power out all of the LAN control toggles in the YL app were switched off. So switched them back on. THEN... still not HE controllable I had to go into the device bulb and run the config/refresh thing, That then found the right state and we were off.
- in review maybe I should turn all the yeelights off, power cycle the router, then turn the YL back on (dont know if that will help but no other ideas)
My Hue bulbs, one was unresponsive and had to dick around with that. Power cycling etc.
I do have to say my Zigbee bulbs performed alot better than the wifi ones after a power out.
Then this morning the HSM fired off a motion sensor.. but I only have that set to contact sensors as I have 5 people and a cat - a MS trigger is never going to work. It was armed for "night" but the mode was now day (I have them together in the dashboard) so I disarmed HSM, then went back in and turned them all back on (the equivalent of clicking "done"). hopefully thats worked (I dont have a siren so no one was the wiser on that one).
Then one for @mike.maxwell - this is going to sound crazy but bear with me.
Can a zwave MS and a zigbee MS be tied together with Multizone app ?
The reason:
I have an aeon multi 6 tied to a iris 2 MS, and I had it set to the first MZ (forgive me i forget the name) and it seemed I could get them both to fire within 2 seconds to set off the MZ. So then I set it to the third one (forget the name) and then either of the MS would set it off. Not what I wanted. So I set it back to the first one and the zigbee MS stops responding.
Tried to reset it, battery pull, etc etc. I cant get it back to life, and I have a bunch of nulls now on my zigbee routing table.
So i thought fine, they were cheap enough, pulled out another for the 10pk i got off ebay. Set it up the same way, had the same issue with the MZ above, now this little zigbee MS is having the same issue - completely dead to life. I.AM.CONFUSED.
Is there no way @mike.maxwell that the ikea hub be integrated into HE to control ?
https://learn.pimoroni.com/tutorial/sandyj/controlling-ikea-tradfri-lights-from-your-pi
this is also a really annoying part...
nothing on the hubs changed all day.
it tracks me leaving at 759,
doesnt notify at 807 when the mrs leaves,
tracks her at 9am coming back,
doesnt track her at 231 leaving or 308 returning.
it can tell that she has left, because the mode changes, but it doesn't notify all the time.
like wtf..
As of last last 2 days, my system has actually been *stable (touch wood).
And a big part of that was removing One ikea bulb.
This one ikea bulb had been stealing my motion sensors, contact sensors etc etc. I was watching the zigbee table but sometime coming back the table would be right, then the next time upside down.
I dont mean to jinx myself, but all my automations have been ontime and all the battery powered devices seem to be playing nice.
Leaves me to a point I actually dont want to do any software updates cause its taken me so long to get to something stable I just want to enjoy it for abit.
I am up to the point of even trying multi-zone MS which is pretty cool.
I am having an issue where I am calling 2 front bulbs on in white, green and pink for different events, but sometimes one bulb comes on, sometimes both. Sometimes one turns off early, sometime it doesnt. But thats small fish as I am just trying to enjoy my stable system for now lol.
2 Likes
so after this post my zigbee network did poops in the bed, lol
I removed 2 of the 4 wemo bulbs, buying 2 more hues today to rid myself of any zigbee bulbs directly connected to my hub.
Rolled back to a previous backup which got my repeaters back. Not sure whether to try another brand of MS or add more repeaters (I only have <20 devices and 4 repeaters) only other thoughts to change my hue hub channel to something else (HE is set to 20 currently).
my hubs been pretty good otherwise, modes, combined presence, scenes firing off mode changes. Its just the MS firing ML - when that stops (often) I get so annoyed about it.
Has anyone had a similar experience..
I had issues 4 days ago upgrading from 129 to 130, zigbee table went nuts, ML broken, etc etc. So I rolled back to 129 - got my table back in order and went to bed..
So I had this weird thought, why haven't I seen the red dot telling me to update to .130 for the past few days. Go to my hub details to see my hubs been on .130 8hrs after I rolled it back..
I 100% know I rolled back from .130 to .129 (I have a google doc sheet where I document my changes / hub events so i have a record) and I can see at 7.23pm there was a backup of 129..
But at 3.05am the next day my software is back to 130..
I write in my doc when i update, and I haven't hit update. Kinda Weird.
@bravenel - i'll eat humble pie on this one and apologise again. I have been posted under the assumption my system has only been stable as the last software related thing I did was a restore to .129 - it has been on .130 the past 4 days and I haven't had a single zigbee related issue.
1 Like
Is it possible that your attempt to rollback to 129 failed?
I have never needed to rollback so I'm not familiar with the intricacies of the process but I figured it might explain your scenario. Now, if you verified your rollback was successful after the fact, then the only logical conclusion would be "ghost in the machine".
3 Likes
I def didnt check if the rollback worked.
I just clicked restore from my last stable day (2days prior to that update) and when the system came back I had two MS that needed attention - but since then everythings been firing great.
So your theory is possible.
1 Like
Can you verify at settings->hub details? It would be interesting if you were running on one firmware but backing up another.
yeah its def .130
1 Like
All I can say is that weird stuff happens from time to time. Weird enough that I don't know if I messed up or Hubitat hiccuped or just what. I tend to have so many irons in the fire at any one time that I've learned it's almost always me, discovery made after the fact. Talk about eating humble pie: I run to the engineers saying oh crap, this or that failed, and it almost always turns out to be my mistake.
You know the story about the boy who cried wolf...
4 Likes
From your posts it's sound like you rolled back the database? Did you use back up and restore and roll back to a file from a few days before?
I went to backup and restore and just clicked the Restore from the previous date I know I knew it was stable on .129 - no sure if thats a database roll back. I assumed it was a restore from that whole file.
No that's just a database restore. You have to do something else to role back the firmware.
Thought it sounded abit odd. So you must have had a Doggy database when you updated and you restored it to a good one so it worked. Nothing to do with the firmware 
Takes you here
2 Likes
yeah, def Didnt do that - just a database restore then.
Thanks for pointing out the difference, saves me throwing around the wrong info.
2 Likes
gotta say, and ive made this mistake before, but since removing those ikea and wemo bulbs my system has been rock solid.
I haven't lost a motion sensor, not one rule has missed fired and its a joy to come home knowing I dont have to turn on a bunch of logs to fault find where ive gone wrong with something or wonder why something has just stopped responding for no reason.
I have gone back to RM and selfishly pumping out as many RM3s as i can (I have liked SL and ML but I also find with all the extra buttons and bits and pieces I miss things) where with RM I can just strip it down to, when this happens, do this. I know it wont deviate or give me a result (typically) that im not expecting.
now its getting to the point where im layering things (turn this on, and also turn this virtual switch on) and I know it might come unstuck because if the first thing isnt working, now I have another layer ontop of that to check if that also didnt work etc etc.
Fun to think about, and glad to get to the next step, but also hesitant because I know it comes with more risk / effort.
Also to the point where i want to add in TTS and maybe change out my dumb fan switches for smart switches. But thats a whole new kettle of fish.
1 Like
zigbee bulbs on a ZHA network are the devil. 
(yes I know some bulbs work fine on ZHA networks... blah blah blah. I stand by my statement lol).
4 Likes
I think your post has just about convinced me to forget about Zigbee lamps ( I don’t want colour changing etc) and go with micro dimmers in wall. 
Another Hub + more repeaters + new light switches + Zigbee Lamps
Versus
In wall dimmers (use existing Zwave repeaters, existing switches and lamps)
This is for two rooms !
Either way can work. I will say, though, if you just want dimming (not color), I personally prefer to just go with wall dimmers or maybe in-wall micro dimmers).
But there is no 'right or wrong' here.
got so tired of my masking tape life...
went down to bunnings and got some blanks, removed the tape, cleaned up the faces and just used a touch of doube sided tape on the top to stick the new over the old. Much better on my OCD eyes.
plus if i need to access them I can just flip up the face and have access again. Easy Peasy
