Mysensors combined sensors keep changing (likely fixed)

[kisse66]

This topic was touched under another one, but I think this needs new topic:

I' m using latest dev branch on RPi (now 3.9139). Have multiple Mysensors nodes some of which have temp+hum, one has temp+hum+baro. My nodes report using separate child IDs for each sensor. One uses temp 2 hum 3, another temp 1 hum 2 baro 3 (no multiple same type). Those got initially nicely automatically combined and I added them to dashboard. Worked for about a day and suddenly without any changes except re-starting domoticz the combined device stopped getting updates. The sensors still send as before and was not even re-started. The separate devices were getting updates, but somehow the combined one got separated.

Next day I pulled the latest git (a few days forward), rebult and started. Deleted the problematic sensors and after some time got the combined ones working again. This worked for two days until I had to re-boot the RPi. Took a day to notice, but after that the combined weather sensor stopped getting updates, again the separate sensors still get data. I deleted that sensor and all the related devices. Got back the separate devices as the values arrived, but not the combination. Left it runnig over night (updates every 20min), still no combination in the morning. Then I re-started domoticz and after a while seemed to again got the combination back!

So been trying to read discussion and look at the code a bit, but I can't understand why things change by themselves. I can change my sketches if there's something to fix, but what? Any help or ideas welcome.

[kisse66]

Happened again last night, weather sensor stopped updating. This time I might (?) have a clue of what's happening - weather sensor seems to do this mostly. It is far away and I have seen occasional dropped updates. It sends 5-7 values and sometimes one or two of those get lost. Has not been an issue with my older simple logging setup. How about Domoticz, can it "forget" the combined sensor, if some values are not seen every time ? Like temp+hum only sends temp a few times? At least the last update did have all the values, but the combined sensor is not coming back to life. Nothing special in logs.

This time I also did not re-start anything, so it may have been a co-incidence earlier.

[kisse66]

Seems to be a monologue, but I think the issue was found - my sensors might send >100% RH values. It's been raining and I just looked more carefully into the data. There was 102% values for long time (for the two sensors that keep disappearing). This likely confuses Domoticz. I added a 100% limit to my sketch and it has now been running fine several days.

[gerardvs]

Seems to be a monologue

At least thanks for sharing

[gerardvs]

Is your problem really solved? I have the same problem, Domoticz keeps messing up, like combining unrelated sensors or not updating sensors anymore while finding new ones. In my case mysensors is configures through MQTT and shows all the correct values in Setup-->Hardware-->Gateway-->Setup.

Hope someone can help.

--Gerard

[gerardvs]

I see, there is a design flaw in the code (/hardware/MySensorsBase.cpp). For types V_TEMP and V_HUM the code searches for other children. This ludicrous. Since a mysensor node can have many sensors (in my case 12) it is likely that there is absolutely no relationship between multiple (hum/temp) sensors.
Hopefully this will change over time but for now I will make a minor change to the code and compile Domo myself.

[NeoMod]

Having the same issue with my Domoticz+MySensors installation: it's driving me crazy from months now. After reading everything on this matter I stumbled, multiple times on different searches, on this topic. Hence I thought It may be useful leaving a note: I'm going to change controller, this is the only viable solution if you want things to work and/or you want to rely on mysensors data. IMHO this "dissonance" between Domoticz and MySensors is borderline idiotic, and I believe they should respectively drop the support from each other: this way no more users get confused and frustrated over this issue. (issue, by the way, well know from years and also documented in every flavour. but never addressed.)