Domoticz

I'll appreciate any hint on how to troubleshoot this.
My domoticz system has been running on a RPI2 with the razberry card since almost 2 years flawlessly. And growing to almost a hundred devices.
Recently bought a RPI3 and tried to make it work just moving the razberry and sdcard to it. it didn't work.
So in order not to break the current system, which is still on v 2.3530 I installed a new SD from scratch using 4834.
All went well, for a while.
Suddenly the blinds in the kitchen started to open and close when the fibaro motion in the kitchen detected motion. None of my scripts do that. Avoided the issue temporarily taking the fibaro battery out.
Then in one of the rooms. When the fibaro (different one) detected motion it switched on all lights in the house. It ended up without battery and in a drawer until I find the time to understand what's wrong.
Today the living room. As soon as the fibaro there detects motions, switches on all lights in the house and opens all the blinds. When removed it battery some sort of alarm was enabled so all the lights in the house started blinking. My house was like a Christmas tree for many minutes.

Tired of it I've moved the razberry card back to my old RP2. Started it, put the battery back into one of the fibaro motion and there it goes, all lights on all blinds up.

What I have done:

+ Tested in both the RPI2 with 3530 and RPI3 with 4834, same behavior
+ Removed temporarily all the scripts, left it naked, only devices and associations (a couple, and unrelated). same behavior
+ Checked the same oddness happens with the 3 fibaro motion sensors, so don't think it is related to a single device malfunctioning
+ Thought about some possible corruption, but I repro it in both systems.

Only common thing is the razberry card and the domoticz database. I've used the same original one from the 3530 in the 4834. Funny thing is all continue to work smooth if I just keep the fibaro motions out of the system.

Any clue where I should be looking? I've started to admit will need to rebuild all from scratch, but even in that case as all is working fine without the fibaros, I'm worried the problem might be somewhere else and will get into the same situation.


thanks in advance for any hint.

J

I read something about RPi3 not being fully compatible with RPi2 when it comes to using the Razberry card. I read it here: viewtopic.php?f=24&t=10964&p=83362&hili ... pi3#p83362 . Maybe it has something to do with the problem.

thanks, yes they are not, I had to go through that to set it up initially and got it running (no BT but not an issue). Odd thing is those several fibaro motion now apparently sending ALL ON commands widely the moment I put their batteries back on. I'm puzzled.

It looks like your zwave-network has some direct associations between motion sensors and (all) switches. This is independent from the RPI. You can change that in the zwave-control panel. If that doesn't work, the the best action is to exclude the motion sensors first and then (perhaps also do a RPI restart to make sure) include them again.

good hint, thanks. several of my devices now got mysteriously an ID 255 in all their association groups. removing them now to see if that has a positive effect. no clue how those got there which is another worrisome thing. thanks very much for the hint.

Mmm, if you Google at zwave association group 255 you will find similar stories. Removing it should help.