I am using Thermosensor Renkforce E0001TA https://www.conrad.at/de/thermosensor-renkforce-e0001ta-1404106.html - The sensor is sending data every 5:42 minutes.
To check when data are updated i created a DummyPresenceSensor (“check-ta”) with an autoreset after 10 seconds
So i trigger the DummyPresenceSensor pulses by a rule:
when $e0001ta.temperature gets updated then set presence of check-ta present
I verified the pulses in the Graph against the eventslog
BUT: I even get additional pulses within the events listed in the eventslog
I cannot find any correlation betwenn the additional pulses and any other events
The shortesrt time difference between the additional pulses is typical 57 seconds
Do you have any idea where they are triggered by ?
-
Problem with gets updated within a rule
-
@NoFrog said in Problem with gets updated within a rule:
Do you have any idea where they are triggered by ?
Did you check the log for homeduino RF pulses received? Are sure the interval is that long? Maybe it is sending pulses at shorter intervals but homeduino cannot receive all of them. I am just asking as 57 secs is close to a commonly used interval of 60 secs by some of these sensors.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
5:42 minutes is 6 x 57 seconds. I’m guessing that you’re actually missing pulses, instead of receiving additional pulses. What happens when you put the device closer to the receiver?
-
Thx for your input
The eventlog tells me that the shortest time between the events is 5:40, sometimes longer but never shorter.
Following your theory, that the updates come within 57 seconds:
All logged timespaces divided by 57 secs result in an integer numbers greater than 5 (in the example above from 6 to 8 )
That would mean that only ervery 6th, … 8th pulse is listed in the eventlog.
Maybe all other ones are received, but without valid data ?
I will investigate some time in analysing Messges Debug loggingI’ll stick to it
-
@NoFrog said in Problem with gets updated within a rule:
The eventlog tells me that the shortest time between the events is 5:40
You still didn’t clarify which log data you’re referring to (see my earlier post). Which data are you using to create the data log spreadsheet? Are you filtering the homeduino event log messages? If not have a look at those messages as it will tell you exactly which pulse have been received and when (you may need to enable debug logging for homeduino to get all the details). It would also be helpful to share them for inspection.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
OK, the log data from Events filtered to the device e0001ta All Attrinutes
Not filterd there is only one dataset e0001ta within the 50 lines, because a lot of other events are runningTime Device Attribute Value 10.03.2017 15:53:32 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 15:46:52 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 15:41:10 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 15:34:31 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 15:27:53 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 15:22:10 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 15:16:28 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 15:07:55 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 15:02:13 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 14:56:31 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 14:48:55 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 14:43:13 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 14:35:37 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 14:29:55 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 14:22:19 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 14:13:47 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 14:07:07 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 14:01:25 E0001TA (e0001ta) Temperature 20.3 °C 10.03.2017 13:55:44 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 13:50:01 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 13:43:22 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 13:37:40 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 13:31:58 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 13:24:23 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 13:18:40 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 13:12:58 E0001TA (e0001ta) Temperature 20.4 °C 10.03.2017 13:07:16 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 13:00:37 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 12:54:55 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 12:49:13 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 12:41:37 E0001TA (e0001ta) Temperature 20.7 °C 10.03.2017 12:35:55 E0001TA (e0001ta) Temperature 20.7 °C 10.03.2017 12:30:13 E0001TA (e0001ta) Temperature 20.7 °C 10.03.2017 12:24:31 E0001TA (e0001ta) Temperature 20.7 °C 10.03.2017 12:16:55 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 12:10:16 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 12:03:38 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 11:57:55 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 11:52:13 E0001TA (e0001ta) Temperature 20.7 °C 10.03.2017 11:46:31 E0001TA (e0001ta) Temperature 20.7 °C 10.03.2017 11:39:52 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 11:33:13 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 11:27:31 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 11:21:49 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 11:14:13 E0001TA (e0001ta) Temperature 20.5 °C 10.03.2017 11:08:31 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 11:02:49 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 10:57:07 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 10:49:31 E0001TA (e0001ta) Temperature 20.6 °C 10.03.2017 10:43:49 E0001TA (e0001ta) Temperature 20.5 °C
-
I did deactivate all other RF-Devices and placed the receiver nearer to the thermosensor
Messages Debug All results:
Most of the pulses every 57 seconds are received correct and trigger the rule,
only a few ones are different (shown in magenta) or even lost
53 packets received (marked green)
49 of them started the rule (marked yellow or blue)
BUT: only 10 of them are listed in the Events Log (marked blue) filterd by device e0001taAll data ispected can be found at: https://drive.google.com/open?id=0B-K7wJkdEhqkY1NGZjFFaGVYV2M
The example below shows the typical behavior
Debug […] Time deltatime eventlog len
09:28:34info [pimatic]: rule test-e0001ta: set presence of check ta to present 09:28:34 19.6 °C 09:28:34debug [pimatic-homeduino]: weather18: { id: 173, channel: 1, temperature: 19.6 } 09:28:34 09:28:34debug [pimatic-homeduino]: received: [ 484, 976, 1948, 3892 ] 0201020102020102020101010101010102020101010201010202020202020202010201010003 [ 484, 976, 1948, 3892 ] 09:28:34 76 09:28:34debug [pimatic-homeduino]: data: "RF receive 484 1948 976 3892 0 0 0 0 0102010201010201010202020202020201010202020102020101010101010101020102020003" 09:28:34 02:51 09:25:43debug [pimatic-homeduino]: received: [ 516, 948, 1880, 3820 ] 02010201020201020201010101010101020201010102010102001120202020201210201010003 [ 516, 948, 1880, 3820 ] 09:25:43 77 09:25:43debug [pimatic-homeduino]: data: "RF receive 516 1880 948 3820 0 0 0 0 01020102010102010102020202020202010102020201020201002210101010102120102020003" 09:25:43 00:00 09:25:43info [pimatic]: rule test-e0001ta: set presence of check ta to present 09:25:43 #NV 09:25:43debug [pimatic-homeduino]: weather18: { id: 173, channel: 1, temperature: 19.6 } 09:25:43 09:25:43debug [pimatic-homeduino]: received: [ 492, 964, 1940, 3900 ] 0201020102020102020101010101010102020101010201010202020202020202010201010003 [ 492, 964, 1940, 3900 ] 09:25:43 76 09:25:43debug [pimatic-homeduino]: data: "RF receive 492 1940 964 3900 0 0 0 0 0102010201010201010202020202020201010202020102020101010101010101020102020003" 09:25:43 01:54 09:23:49info [pimatic]: rule test-e0001ta: set presence of check ta to present 09:23:49 #NV 09:23:49debug [pimatic-homeduino]: weather18: { id: 173, channel: 1, temperature: 19.6 } 09:23:49 09:23:49debug [pimatic-homeduino]: received: [ 496, 960, 1936, 3888 ] 0201020102020102020101010101010102020101010201010202020202020202010201010003 [ 496, 960, 1936, 3888 ] 09:23:49 76 09:23:49debug [pimatic-homeduino]: data: "RF receive 496 1936 960 3888 0 0 0 0 0102010201010201010202020202020201010202020102020101010101010101020102020003" 09:23:49 00:57 09:22:52info [pimatic]: rule test-e0001ta: set presence of check ta to present 09:22:52 #NV 09:22:52debug [pimatic-homeduino]: weather18: { id: 173, channel: 1, temperature: 19.6 } 09:22:52 09:22:52debug [pimatic-homeduino]: received: [ 500, 960, 1936, 3888 ] 0201020102020102020101010101010102020101010201010202020202020202010201010003 [ 500, 960, 1936, 3888 ] 09:22:52 76 09:22:52debug [pimatic-homeduino]: data: "RF receive 500 1936 960 3888 0 0 0 0 0102010201010201010202020202020201010202020102020101010101010101020102020003" 09:22:52 00:56 09:21:56info [pimatic]: rule test-e0001ta: set presence of check ta to present 09:21:56 19.6 °C 09:21:56debug [pimatic-homeduino]: weather18: { id: 173, channel: 1, temperature: 19.6 } 09:21:56 09:21:56debug [pimatic-homeduino]: received: [ 500, 960, 1932, 3888 ] 0201020102020102020101010101010102020101010201010202020202020202010201010003 [ 500, 960, 1932, 3888 ] 09:21:56 76
-
PS: Is it poosible that Log - Events Shows data as “Average values of 5min.” ?
Like shown in Graps****