[mysensors] puzzled by so tragic domoticz rain sensor
Posted: Wednesday 08 October 2025 12:45
Version: 2025.1
Build Hash: 89d5c900d
Compile Date: 2025-05-05 09:02:49
dzVents Version: 3.1.8
Python Version: 3.13.3 (main, Aug 14 2025, 11:53:40) [GCC 14.2.0]
Active User: admin
Platform: ubuntu 25.04
Plugin/Hardware: mysensors, rain sensor V_RAIN/S_RAIN
Description:
OMG it could not be more complicated... than domoticz rain sesors.
I am very flustrated by the understandong how it is supposed to work.
OK,my sensor is reporting incremental rain mm value - volume of my rain guage bucket. Every time the bucket switch the magnetic switch the sensor send incremented value by 0.2 which rain rate mm/m2 corresponding to my bucket and guage size.
When I list the db...
sqlite3 ~/domoticz/domoticz.db "SELECT Date, Total, Rate FROM Rain WHERE DeviceRowID=43 ORDER BY Date DESC LIMIT 50;"
2025-10-08 10:35:00|13473.2|20
2025-10-08 10:30:00|13473.2|20
2025-10-08 10:25:00|13473.2|20
2025-10-08 10:20:00|13473.2|20
2025-10-08 10:15:00|13473.2|20
2025-10-08 10:10:00|13473.2|20
2025-10-08 10:05:00|13473.2|20
2025-10-08 10:00:00|13473.2|20
2025-10-08 09:55:00|13473.2|20
2025-10-08 09:50:00|13473.2|20
2025-10-08 09:45:00|13473.2|20
2025-10-08 09:40:00|13473.0|0
2025-10-08 09:35:00|13473.0|0
2025-10-08 09:30:00|13473.0|0
2025-10-08 09:25:00|13473.0|0
2025-10-08 09:20:00|13473.0|0
2025-10-08 09:15:00|13473.0|0
2025-10-08 09:10:00|13473.0|0
2025-10-08 09:05:00|13473.0|0
2025-10-07 16:40:00|13472.8|100
2025-10-07 16:35:00|13472.8|100
2025-10-07 16:30:00|13472.8|100
2025-10-07 16:25:00|13472.8|100
2025-10-07 16:20:00|13472.8|100
2025-10-07 16:15:01|13472.8|100
2025-10-07 16:10:00|13472.8|100
2025-10-07 16:05:00|13472.8|100
2025-10-07 16:00:01|13472.8|100
2025-10-07 15:55:00|13472.8|100
There are visible three events - at
#1 0.2mm - 2025-10-07 16:40:00
#2 0.2mm - 2025-10-08 09:05:00
#3 0.2mm - 2025-10-08 09:45:00
1) the domoticz logs FALSE EVENTS in the db - WTF?
2) how this looks in chart?
- OK I have no ide how upload image to this forum... but not by the image icon above or paste from my clip board... tragic again
I will describe it :
- daily chart
- x axis is divided by 2 hours (OK)
- now is Oct 8 12:36 ... so lot of time to get the chart updated
- two columns in daily chart :
Oct 7 16:00 - first column 0.2mm high
Oct 8 9:00 - second column 0.2mm high (0.4 expected?????)
WTF again - not as you could expect - two columns, first at #1 0.2mm high, second #2,#2 at 9h 0.4mm high
3) I would appreciated to have in the db at least time when the controller got the rain event message.
4) There is obviously some strange calculation behind it - WTF why?
5) How someone can this expect useful ?
6) Could be the calculation can be done later?
All this is tragic, why not just drop the event in the db and make a calculations as you wish...
7) I do try to visualize the chart in dashticz because the domotiz layout is again so tragic... But it is so overcomplicated the thousands of CSS to override color and chart definition is so complicated and not-working.
I am sure many others have the SAME FEELINGS. Or is there some secret idea behind this?
Thank you for your time...
Captain's log - Wednesday :I spent several days on this already... no solution or even small improvements.
Build Hash: 89d5c900d
Compile Date: 2025-05-05 09:02:49
dzVents Version: 3.1.8
Python Version: 3.13.3 (main, Aug 14 2025, 11:53:40) [GCC 14.2.0]
Active User: admin
Platform: ubuntu 25.04
Plugin/Hardware: mysensors, rain sensor V_RAIN/S_RAIN
Description:
OMG it could not be more complicated... than domoticz rain sesors.
I am very flustrated by the understandong how it is supposed to work.
OK,my sensor is reporting incremental rain mm value - volume of my rain guage bucket. Every time the bucket switch the magnetic switch the sensor send incremented value by 0.2 which rain rate mm/m2 corresponding to my bucket and guage size.
When I list the db...
sqlite3 ~/domoticz/domoticz.db "SELECT Date, Total, Rate FROM Rain WHERE DeviceRowID=43 ORDER BY Date DESC LIMIT 50;"
2025-10-08 10:35:00|13473.2|20
2025-10-08 10:30:00|13473.2|20
2025-10-08 10:25:00|13473.2|20
2025-10-08 10:20:00|13473.2|20
2025-10-08 10:15:00|13473.2|20
2025-10-08 10:10:00|13473.2|20
2025-10-08 10:05:00|13473.2|20
2025-10-08 10:00:00|13473.2|20
2025-10-08 09:55:00|13473.2|20
2025-10-08 09:50:00|13473.2|20
2025-10-08 09:45:00|13473.2|20
2025-10-08 09:40:00|13473.0|0
2025-10-08 09:35:00|13473.0|0
2025-10-08 09:30:00|13473.0|0
2025-10-08 09:25:00|13473.0|0
2025-10-08 09:20:00|13473.0|0
2025-10-08 09:15:00|13473.0|0
2025-10-08 09:10:00|13473.0|0
2025-10-08 09:05:00|13473.0|0
2025-10-07 16:40:00|13472.8|100
2025-10-07 16:35:00|13472.8|100
2025-10-07 16:30:00|13472.8|100
2025-10-07 16:25:00|13472.8|100
2025-10-07 16:20:00|13472.8|100
2025-10-07 16:15:01|13472.8|100
2025-10-07 16:10:00|13472.8|100
2025-10-07 16:05:00|13472.8|100
2025-10-07 16:00:01|13472.8|100
2025-10-07 15:55:00|13472.8|100
There are visible three events - at
#1 0.2mm - 2025-10-07 16:40:00
#2 0.2mm - 2025-10-08 09:05:00
#3 0.2mm - 2025-10-08 09:45:00
1) the domoticz logs FALSE EVENTS in the db - WTF?
2) how this looks in chart?
- OK I have no ide how upload image to this forum... but not by the image icon above or paste from my clip board... tragic again
I will describe it :
- daily chart
- x axis is divided by 2 hours (OK)
- now is Oct 8 12:36 ... so lot of time to get the chart updated
- two columns in daily chart :
Oct 7 16:00 - first column 0.2mm high
Oct 8 9:00 - second column 0.2mm high (0.4 expected?????)
WTF again - not as you could expect - two columns, first at #1 0.2mm high, second #2,#2 at 9h 0.4mm high
3) I would appreciated to have in the db at least time when the controller got the rain event message.
4) There is obviously some strange calculation behind it - WTF why?
5) How someone can this expect useful ?
6) Could be the calculation can be done later?
All this is tragic, why not just drop the event in the db and make a calculations as you wish...
7) I do try to visualize the chart in dashticz because the domotiz layout is again so tragic... But it is so overcomplicated the thousands of CSS to override color and chart definition is so complicated and not-working.
I am sure many others have the SAME FEELINGS. Or is there some secret idea behind this?
Thank you for your time...
Captain's log - Wednesday :I spent several days on this already... no solution or even small improvements.