Lights randomly turning on !!!!

[alex88 71]

Today's problem is that lights have started turning on randomly throughout my house. I have changed very little in my system for the past 3 months so it's not down to something I could have done.

 

I am literally sitting at the HC2 web interface turning a light circuit off in my bedroom only to see it automatically turn itself back on again. I have removed 5 bulbs from my sons bedroom (who now won't go back to sleep, thank you very much for that little weekend gift Fibaro) and will have to remove 10 or so bulbs from my bedroom before I go to bed tonight.

 

Maybe Fibaro have released a hot fix for away from home presence simulation .. haha!

 

On top of all of the other daily trauma that we have to put up with by supporting this company, has anyone else experienced this?

 

I am running 3.590 beta.

 

EDIT: 3 hours later, another Saturday night wasted and still lights are turning on in the house in 4 rooms. Reverted to  2 older backups, spent ages turning off scenes and even did a complete mesh rebuild. Now I have to get back on a ladder to remove bulbs. Thank you Fibaro!

[alex88 71]

Who knows what it is. It felt like the modules were incorrectly associated to themselves and were somehow sending messages to each other when perhaps reporting back to the HC2. This would explain the problem persisting when the hc2 was turned off. Of course it is possible that someone in the Poland tech support/development team is laughing at the idea as they know how the modules communicate to the HC2 and between themselves and they probably understand all the reasons why that is impossible. That said, there is no explanation for what happened. The only assurance is that I did diagnose that my HC2 was faulty.After a complete clean rebuild to v4.040 the problem persisted. A new HC2 fixed that in the end. It took a long time to get to the bottom of it, but thankfully Fibaro support (Adam Bewsher from UK support in particular) kept working through the early diagnosing stage, followed by the complete rebuild of my system from scratch, followed by diagnosing the faulty HC2 and then through to the second rebuild of the faulty HC2. 

 

Not much more I can say other than it was an awful experience that I would never want anyone to go through and that I am relieved that it is over now.

[SHorsham 0]

Glad it's ok for you but very strange that it happens when the hub is switched off

[alex88 71]

Yes, very strange and unless it happens to someone else we will never know why it happened. Let's hope that day never comes.

[robmac 173]

It has happened to Dean.

[alex88 71]

It has happened to Dean.

 

 

The exact same symptoms?

 

Dean, what version where you running? If you have the same symptoms as me then I would strongly recommend a complete rebuild. I can assure you the problem will not go away. It will just get worse.

[deanrparry 19]

Aleks my box was stable until I backed up!

Yes you heard correct... I pressed the backup button!

All downhill from there...

You will all follow suit eventually its just a matter of when... Not if!

Good luck on you Manual Automation projects though! x

[alex88 71]

If you are experiencing random events it sounds like you need to do a complete rebuild.

 

I guess you are on v4, so is your HC2 old? My HC2 was bought back in 2012. I guess one of the problems for me was faulty hardware. Doing a complete rebuild on fresh hardware to v4.040 has completely resolved the problem.

 

That said, I now have all of the v4 problems to deal with.

[robmac 173]

Generic zwave issue ?

Please login or register to see this link.

So are some modules broadcasting and not properly handling network ID? This is not an HC2 issue but bigger? Impacts other controllers. Even the fabled purple system.

The new HC2 would have new network ID but as a controller that can be a secondary clearly the network id can be overridden so is there a risk that we could all be using the same network id rather than a global unique value.

By design there should be no cross talk but is this what we are seeing? Poor implementation in some devices or corruption?

[deanrparry 19]

Mine left a log robmac but for some strange reason Fibaro could not see it! It was definately HC2 that told the device to trigger... but it is not associated to any other devices or scenes or anything... it was purely a klaxon siren in a popp plug! I wanted full control over it as it is 127db! Not the sort of thing you want switching on at 4am!

 

OR when your away from home

Please login or register to see this image.

/emoticons/default_icon_sad.gif" alt=":-(" />

 

But hey... it is done now and the response I got was typical mis-communication maybe it is the lingo? but it was BLATANT in the event viewer!

 

At least this will save a few trips to the gym... I have to lift my arms to switch lights on now!

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

[alex88 71]

Dean,

 

On the proviso that you are experiencing the same issue that I was, from my experience if you do not do a complete rebuild you will keep experiencing this over and over again. It will seem to go away and then come back, but in the end it will get worse and worse until you can't bear it. 

 

I went device by device and deleted them from my old HC2 and then my new HC2 and then I added them to the new HC2 until the whole system was rebuilt.

 

I spent a lot of time with tech support and they simply could not figure out the true source of the issue. They did help me get up and running again for which I am grateful, but unless they are holding back they don't know what's going on.

 

Cheers

Aleks

[PepsiMac 17]

Today's problem is that lights have started turning on randomly throughout my house. I have changed very little in my system for the past 3 months so it's not down to something I could have done.

 

I am literally sitting at the HC2 web interface turning a light circuit off in my bedroom only to see it automatically turn itself back on again. I have removed 5 bulbs from my sons bedroom (who now won't go back to sleep, thank you very much for that little weekend gift Fibaro) and will have to remove 10 or so bulbs from my bedroom before I go to bed tonight.

Hi Everyone,

 

Just seen this post and thought I would mention that I had the same problems. What I noted is that the devices that switch on unexpectedly do not update the Web interface. One area of research indicated that the mySQL file used by Fibaro as the "devices database" may have been corrupted. Also, when you delete a device, it seems to retain information about the device ("Automatic Z-wave chip backup after Removing Device.") in the system and this can cause problems. My suspicion is that the devices are being activated when polled from the MySQL database and the corruption has meant their last status is not properly identified by another database. 

 

Restoring and older backup only brings back the same corrupted database, it would be nice if Fibaro allowed for a rebuild of the MySQL files that it uses to ensure matches and verifications. I am in the process of moving all the devices I use from one HC2 to another and am putting all dodgy devices such as the POPP weather and Aeotec 6  on a separate HCL or HC2 so I can disconnect them whenever and will only add to the main controller when templates are available and the information written to the database has had some sort of structural integrity checking as a result.

 

I am not sure if it would also be useful to all us to use the "Z-Wave chip backup feature" as it appears unclickable in the "Remove Device" option and may leave all sorts of extraneous "rubbish" in the controller.

 

As to switching to another controller, I would suggest that even Smartthings is on "caveman v0.1" and we are the mavericks and pioneers of what is still a very young market with minimal investment thus far.