Rain sensor report time is wrong?
Posted: Tuesday 15 March 2016 23:24
version 3.4967
I have Sensor Timeout at 180 minutes(3 hours)
I am only using MySensors nodes
I have a node that reports how many times I have start my car each day, http://forum.mysensors.org/topic/3355/count-car-starts
This means that I will only report between once a day up to maybe 3 times a day.
I have now seen that if nothing has been reported I get red Label on my sensor in Domoticz, this is normal and is OK i ignore that.
Is seems to be that if nothing is reported for 3 hours it will stop write to SQL database, maybe this is normal.
Lets say that this is my use of the car
14/3 21.00, I start my car, i drive away from home so I store 1 in EEPROM.
14/3 21.30, I start my car, i drive away from home so I add 1 to EEPROM.
14/3 23.00, I start my car and when I come home it will report 3 starts, this one and two other.
15/3 08.00, I start my car, i drive away from home so I store 1 in EEPROM.
15/3 08.30, I start my car, i drive away from home so I add 1 to EEPROM.
15/3 09.30, I start my car, i drive away from home so I add 1 to EEPROM.
15/3 12.30, I start my car, i drive away from home so I add 1 to EEPROM.
15/3 16.00, I start my car and when I come home it will report 5 starts, this one and four other.
When I report for Day 1 it will be OK since that is the first item that is reported to the system. Problem is for Day 2. At Day 1 19.00 it will stop written to MYSQL so when I report for Day 2 at 16.00 it will start to write to MYSQL again, time stamp in MYSQL is correct but the graph will be wrong.
Below is what I see in MYSQL
And this is the graph for same data
It shows that I have been starting the car 5 times between 13/3 ~23.00 until 14/3 20.30, but actually it was o the 15/3.
I know that there is no time stamp for exact date and time but if I send the value 5 at 2016-03-15 16:20 it shall not show 2016-03-14 20:30, or?
And why does it stop written to MYSQL after 3 hours, save space on harddrive? If it has been saving same value until a new value was reported it should worked as I wanted it. Maybe it is only me that need this function or am I doing something wrong?
I am using the Rain sensor because it will be reset every midnight
I have Sensor Timeout at 180 minutes(3 hours)
I am only using MySensors nodes
I have a node that reports how many times I have start my car each day, http://forum.mysensors.org/topic/3355/count-car-starts
This means that I will only report between once a day up to maybe 3 times a day.
I have now seen that if nothing has been reported I get red Label on my sensor in Domoticz, this is normal and is OK i ignore that.
Is seems to be that if nothing is reported for 3 hours it will stop write to SQL database, maybe this is normal.
Lets say that this is my use of the car
14/3 21.00, I start my car, i drive away from home so I store 1 in EEPROM.
14/3 21.30, I start my car, i drive away from home so I add 1 to EEPROM.
14/3 23.00, I start my car and when I come home it will report 3 starts, this one and two other.
15/3 08.00, I start my car, i drive away from home so I store 1 in EEPROM.
15/3 08.30, I start my car, i drive away from home so I add 1 to EEPROM.
15/3 09.30, I start my car, i drive away from home so I add 1 to EEPROM.
15/3 12.30, I start my car, i drive away from home so I add 1 to EEPROM.
15/3 16.00, I start my car and when I come home it will report 5 starts, this one and four other.
When I report for Day 1 it will be OK since that is the first item that is reported to the system. Problem is for Day 2. At Day 1 19.00 it will stop written to MYSQL so when I report for Day 2 at 16.00 it will start to write to MYSQL again, time stamp in MYSQL is correct but the graph will be wrong.
Below is what I see in MYSQL
Code: Select all
"102" "18.0" "0" "2016-03-14 20:25:01"
"102" "18.0" "0" "2016-03-14 20:30:01"
"102" "23.0" "0" "2016-03-15 16:25:01"
"102" "23.0" "0" "2016-03-15 16:30:01"
"102" "23.0" "0" "2016-03-15 16:35:02"
"102" "23.0" "0" "2016-03-15 16:40:01"
"102" "23.0" "0" "2016-03-15 16:45:01"
"102" "23.0" "0" "2016-03-15 16:50:02"
"102" "23.0" "0" "2016-03-15 16:55:01"
"102" "23.0" "0" "2016-03-15 17:00:01"
"102" "23.0" "0" "2016-03-15 17:05:01"
"102" "23.0" "0" "2016-03-15 17:10:01"
"102" "23.0" "0" "2016-03-15 17:15:01"
"102" "23.0" "0" "2016-03-15 17:20:01"
"102" "23.0" "0" "2016-03-15 17:25:01"
"102" "23.0" "0" "2016-03-15 17:30:01"
"102" "23.0" "0" "2016-03-15 17:35:01"
"102" "23.0" "0" "2016-03-15 17:40:01"
"102" "23.0" "0" "2016-03-15 17:45:01"
"102" "23.0" "0" "2016-03-15 17:50:02"
"102" "23.0" "0" "2016-03-15 17:55:02"
"102" "23.0" "0" "2016-03-15 18:00:02"
"102" "23.0" "0" "2016-03-15 18:05:02"
"102" "23.0" "0" "2016-03-15 18:10:02"
"102" "23.0" "0" "2016-03-15 18:15:01"
"102" "23.0" "0" "2016-03-15 18:20:02"
"102" "23.0" "0" "2016-03-15 18:25:02"
"102" "23.0" "0" "2016-03-15 18:30:02"
"102" "23.0" "0" "2016-03-15 18:35:02"
"102" "23.0" "0" "2016-03-15 18:40:02"
"102" "23.0" "0" "2016-03-15 18:45:02"
"102" "23.0" "0" "2016-03-15 18:50:02"
"102" "23.0" "0" "2016-03-15 18:55:02"
"102" "23.0" "0" "2016-03-15 19:00:02"
"102" "23.0" "0" "2016-03-15 19:05:01"
"102" "23.0" "0" "2016-03-15 19:10:01"
"102" "23.0" "0" "2016-03-15 19:15:02"
"102" "23.0" "0" "2016-03-15 19:20:02"
- carcount.png (85.91 KiB) Viewed 1005 times
I know that there is no time stamp for exact date and time but if I send the value 5 at 2016-03-15 16:20 it shall not show 2016-03-14 20:30, or?
And why does it stop written to MYSQL after 3 hours, save space on harddrive? If it has been saving same value until a new value was reported it should worked as I wanted it. Maybe it is only me that need this function or am I doing something wrong?
I am using the Rain sensor because it will be reset every midnight