I recently had issues that my Flood Sensor (Fibaro FGFS101) did not send updates.
Therefore I decided to remove it from controller and delete its thing.
I re-included it as a new node (it was detected as 20 and the previous Node 15).
Because I did not run into the same problems (using the old potentially problematic config, I picked Node 20 and it works well.
However, Node 15 always pops up in my inbox since.
I ignored it and removed it, but it’s still popping up.
Is there any way to get rid of this relict?
Does your Fibaro sensor work when you restart openhab, and then stop working at some point? If so, I suggest turning off Network Heal to see if that solves the problem. That’s the only common issue/solution I’ve noted amongst people moving to OH3, but there’s not enough data to conclude that it’s a problem with the OH3 software.
Anecdotally, I wouldn’t say that there are more people experiencing issues with OH3 than with OH2. Bruce would have more insight on that, though.
The logs show, that after a restart the timestamp (set with motion by a rule) does only change from NULL to a date in the past (3 days ago), so I assume that answer is “no” and it’s just restored from persistence on startup.
But I will check again.
What’s irritating is, that the node thing is ONLINE
The nightly heal is really only needed if you physically move a node (device) It has caused some systems to have huge amounts of traffic during the heal process. Especially if there are lots of nodes or nodes with security enabled. Some systems, the traffic eventually causes the systen to lock up and unable to recover.