Since this afternoon, it seems that there is something on my zwave network happening that is causing all lights/switches/relays to act up. I have a fibaro double relay, a fibaro dimmer 2, 2x aeotec multisensors and aeotec zwave stick as main controller connected to my hass instance.
I know this has pretty much nothing to do with hass, but I guess it couldn’t hurt asking around here.
I noticed that several lights start flashing when one of the multisensors detect motion. The led on the multisensor stays on for several seconds longer than otherwise, and I can only seem to switch it off my turning the lights on.
I guess the devices are responding to some sort of error report, but how do I figure out what it is and how to remedy the cause?
Does anybody have any pointers? I see some command_class_error frames in the ozw log but I cannot determine from that info if/what is going wrong…
Hope someone can help, this really messes with the acceptance factor of the others in the household
Is the load connected to the Dimmer 2 flashing och flickering? If the load is steadily flashing the dimmer could be responding to General Alarm in accordance with Parameter 40.
thanks @fuse, I figured it is a response to an alarm of some kind. I noticed that the related parameters are set to “flashing” by default. But, I don’t know where the alarm is originating, nor how to remedy it… all fibaro stuff and the aeotec sensors are behaving differently, so I guess they are all responding to the alarm, but where it comes from, no idea…
If you’ve recently played around with the settings for the multi-sensor to alert for motion then the fibaro dimmer will react to this by flashing the lights. Take a look at your config for the sensor and you should be able to turn off sending an alert to other nodes within your network.
I’ve had the same problem. When a sensor sensed motion it would change the state of all connected zwave devices. I hadn’t changed any settings and no recent changes to HASS for a few days before the change happened.
I still haven’t figured it out and ended up having to take the batteries out of the sensor.
That sounds very much like my situation as well @Jtmoore81. I have been tweaking my HA config a lot, but did not touch the zwave stuff as that is working fine. I have unplugged the sensors for now and will see what happens when I plug them back in tonight.
I’ll go through the paramters like you suggested @benji87, but I am certain that I did not change any of those for the multisensors. I know I can disable the response of zwave devices to alarm frames, but that is just fighting the symptoms, not the root cause. If there really is something wrong (e.g. overheating of one of the devices), I would like to know about it, but preferrably without flashing the whole house lighting Also, I did not notice any other value in the HA sensors _alarm_level and alarm_type for any of the zwave stuff, but I may have missed them as they happened.
Am I right in assuming that those alarm_level and alarm_type sensors will be the places in HASS where any alarms would be visible? That way I can write a notification if there is anything other than 0, right?
See the fibaro dimmer module info here: http://manuals.fibaro.com/dimmer-2/ specifically the section titled “Operating alarm data frames” which makes me think the flashing is a reaction to a sensor being triggered and not overheating. If the module detects overheating or a current surge then it will attempt to shut of the lighting.
If you can remember the time/date when the lights flashed then you could always check the zwave log to try and track down the node that triggered the action.
I think you were right, it seems that both the fibaro dimmer 2 as well as the double relay modules were responding to the General Alarm reports that the multisensors generate when detecting motion.
I have updated the configs for the fibaro modules, but I am still stumped how this behavior was introduced as I said, I have not touched anything zwave related in a while, until now.
So, what must have changed is either:
both multisensors started sending alarm reports (where I thought it was just a basic command class (or something like that), but not an alarm)
or
both fibaro modules I have, started responding to “General Alarm” reports. Which would have required me explicitly setting those parameters.
Can it be that something was changed in openzwave or something that may have been triggered or changed in the config?
Hi, I know this is some months old but, the same happend to me yesterday, I’ve got a z-wave network with around 15 nodes, 2 of them are fibaro double switch and other two Aeotec motion multisensor.
Yesterday it starts to fail, every time the aeotec motion sensors detects motion the two fibaro doubble swtiches starts to blink… it is very weird for me, the network have been working for 9 months without any trouble…
@aetjansen did you find a solution? or more important the root cause of the problem?
I am sorry to hear you are running into these issues also. I don’t think I have ever found the root cause, although after an upgrade of hass, I believe the (then current) zwave control panel software had upgraded or moved and the zwcfg xml file I thought I was using, was no longer the one used.
But, I ended up installing everything from scratch. Not necessarily because I could not find the cause, but also because I got new hardware at the same time to run HASS on, so sorry that I cannot be more specific.
Be aware though that at the time I was experiencing issues, it was not possible yet to edit zwave parameter directly through hass.
Thanks for your replay this is indeed a strange and annoying problem, I was able to stop the alarm by disabling the two Aeotec multisensor, but the day after another z-wave switch and a non zwave plus Fibaro motion sensor start to send alarms too (or someone thinks it where)
I’ve been reading the OZW logs with not too much succeed, the messages looks ok and I can’t understand why it is happening.
I start thinking that the zwave network/hass got corrupted somehow and is misunderstanding the messages… I decided to migrate my hass to a more powerful system and reinstall everything, I hope everything works well again.
Before you spend (a lot?) of money on new hardware, the performance of HA is probably not the cause, I think. But, you may want to “heal network” from the settings->zwave panel in HA and see what that does for you.
Not a lot money i was already in my plans to move from RPI3 to Z83 (a nice 80€ Atom w/ 2Gb Ram). I’ve moved already all the network and it is working fine so far (as it did for the first 9 months with the RPI3)
I’ve tryed to use “secure inclusion” for all devices in first place, but it was not working good, the switches in the network saturates and took too long to switch the loads (lights in this case) (2/3sec)
So, now i’m working with not secure inclusion and all my nodes installed and it is ok
Glad its working then, but what do you mean with “the switches in the network saturates”? I notice my fibaro lightswitch module seems to take a few seconds to switch on as well, hence the question
I dont know what happend, but my guess is that the encryptation is “too much work” for the switches processor and when many mensages are sent too quickly the switch is not able to respond in “real time” (not even usefull time)
My fibaro switches respond well to the first command and sometimes even the second, but eventualy it will hang for 4 or 5 seconds before respond to the next command and it is way too much for a responsive domotic system.
Also, I did not notice any other value in the HA sensors _alarm_level and alarm_type for any of the zwave stuff, but I may have missed them as they happened.