Why is updating intervall so unreliable for some devices?

Moderators: rtenklooster, Voyager, BertB, Stuntteam

Post Reply
Message
Author
padrino
Normal user
Posts: 23
Joined: 17 Feb 2019, 15:05

Why is updating intervall so unreliable for some devices?

#1 Post by padrino » 09 Dec 2022, 14:18

Hi,

I use many brands of temperature sensors here (they have just grown with time =)), and in general they work quite well with rflink.
Well, some do more than others. ;)
They update about once a minute, of course sometimes there can go something wrong (maybe some bird in the wrong position ;)), so it might take the second attempt, but that I would still call reliable. :)

This holds for
- Firstline
- LaCrosse
- Oregon_TempHygro,

but not for
- Baldr
- InoValley_SM200
- F007_TH
- Xiron
(for the latter you see an example in the "code" below).

I really wonder, what's going wrong, and if there maybe something could be tweaked in rflink to fix this. :)

Would be great. :D

Greets

Code: Select all

javascript.0	2022-12-09 13:27:52.037	warn	(10995) script.js.common.Wachtür: *** TK:-19.8 (30 Min.) ***
javascript.0	2022-12-09 12:57:28.211	warn	(10995) script.js.common.Wachtür: *** TK:-13.3 (10 Min.) ***
javascript.0	2022-12-09 12:47:01.063	warn	(10995) script.js.common.Wachtür: *** TK:-14.4 (13 Min.) ***
javascript.0	2022-12-09 12:33:43.098	warn	(10995) script.js.common.Wachtür: *** TK:-16.1 (1 Min.) ***
javascript.0	2022-12-09 12:31:49.089	warn	(10995) script.js.common.Wachtür: *** TK:-16.4 (18 Min.) ***
javascript.0	2022-12-09 12:12:49.110	warn	(10995) script.js.common.Wachtür: *** TK:-19.3 (15 Min.) ***
javascript.0	2022-12-09 11:57:37.115	warn	(10995) script.js.common.Wachtür: *** TK:-17.4 (2 Min.) ***
javascript.0	2022-12-09 11:54:46.127	warn	(10995) script.js.common.Wachtür: *** TK:-16.4 (1 Min.) ***
javascript.0	2022-12-09 11:52:52.127	warn	(10995) script.js.common.Wachtür: *** TK:-15.6 (0 Min.) ***
javascript.0	2022-12-09 11:51:55.118	warn	(10995) script.js.common.Wachtür: *** TK:-15.4 (8 Min.) ***
javascript.0	2022-12-09 11:43:22.149	warn	(10995) script.js.common.Wachtür: *** TK:-13 (1 Min.) ***
javascript.0	2022-12-09 11:41:28.141	warn	(10995) script.js.common.Wachtür: *** TK:-13.2 (8 Min.) ***
javascript.0	2022-12-09 11:32:55.150	warn	(10995) script.js.common.Wachtür: *** TK:-13.9 (0 Min.) ***
javascript.0	2022-12-09 11:31:58.152	warn	(10995) script.js.common.Wachtür: *** TK:-14 (3 Min.) ***
javascript.0	2022-12-09 11:28:10.141	warn	(10995) script.js.common.Wachtür: *** TK:-14.4 (3 Min.) ***
javascript.0	2022-12-09 11:24:22.173	warn	(10995) script.js.common.Wachtür: *** TK:-14.7 (11 Min.) ***
javascript.0	2022-12-09 11:12:58.185	warn	(10995) script.js.common.Wachtür: *** TK:-16.3 (21 Min.) ***
javascript.0	2022-12-09 10:51:07.201	warn	(10995) script.js.common.Wachtür: *** TK:-19.4 (14 Min.) ***
javascript.0	2022-12-09 10:36:52.229	warn	(10995) script.js.common.Wachtür: *** TK:-16.5 (19 Min.) ***
javascript.0	2022-12-09 10:16:55.247	warn	(10995) script.js.common.Wachtür: *** TK:-13.4 (5 Min.) ***
javascript.0	2022-12-09 10:11:13.231	warn	(10995) script.js.common.Wachtür: *** TK:-13.9 (5 Min.) ***
javascript.0	2022-12-09 10:05:31.246	warn	(10995) script.js.common.Wachtür: *** TK:-15.3 (4 Min.) ***
javascript.0	2022-12-09 10:00:46.237	warn	(10995) script.js.common.Wachtür: *** TK:-15.9 (32 Min.) ***
javascript.0	2022-12-09 09:28:28.283	warn	(10995) script.js.common.Wachtür: *** TK:-17.8 (3 Min.) ***
javascript.0	2022-12-09 09:24:40.277	warn	(10995) script.js.common.Wachtür: *** TK:-17.6 (0 Min.) ***
javascript.0	2022-12-09 09:23:43.269	warn	(10995) script.js.common.Wachtür: *** TK:-17.4 (1 Min.) ***
javascript.0	2022-12-09 09:21:49.281	warn	(10995) script.js.common.Wachtür: *** TK:-16.9 (2 Min.) ***
javascript.0	2022-12-09 09:18:58.278	warn	(10995) script.js.common.Wachtür: *** TK:-15.6 (1 Min.) ***
javascript.0	2022-12-09 09:17:04.297	warn	(10995) script.js.common.Wachtür: *** TK:-14.5 (13 Min.) ***
javascript.0	2022-12-09 09:03:46.298	warn	(10995) script.js.common.Wachtür: *** TK:-14 (18 Min.) ***
javascript.0	2022-12-09 08:45:43.324	warn	(10995) script.js.common.Wachtür: *** TK:-16.4 (1 Min.) ***
javascript.0	2022-12-09 08:43:49.317	warn	(10995) script.js.common.Wachtür: *** TK:-16.8 (5 Min.) ***
javascript.0	2022-12-09 08:38:07.312	warn	(10995) script.js.common.Wachtür: *** TK:-17.5 (2 Min.) ***
javascript.0	2022-12-09 08:35:16.313	warn	(10995) script.js.common.Wachtür: *** TK:-18.4 (10 Min.) ***
javascript.0	2022-12-09 08:24:49.350	warn	(10995) script.js.common.Wachtür: *** TK:-19.5 (55 Min.) ***

User avatar
Stuntteam
Site Beheer
Posts: 789
Joined: 27 Jan 2016, 16:46

Re: Why is updating intervall so unreliable for some devices?

#2 Post by Stuntteam » 12 Dec 2022, 00:47

Nothing really wrong at RFlink's side but more a side effect from the ASK modulation and the way the transmitters work.
RFlink is listening to radio signals. It will receive whatever comes by.. however, there can only be 1 signal at a single moment in time.
The more devices you have that are transmitting on the same frequency the more likely that you will get 'collisions' and the strongest signal will win.
Even if you start all devices nicely one after another and only use devices that transmit once per minute, you need to know that there are some robust devices that will nicely transmit every minute.
But there are also some cheaper and less strict devices that will transmit 'more or less' every minute.. (eg. 59 seconds, 64 seconds, 62 seconds etc.) which causes a shift in time and will make it impossible to listen to the device when it transmits at the same moment as another stronger device transmits.
and there is much more to it than just this...
-=# RFLink Gateway Development Team #=-
Introduction: http://www.nemcon.nl/blog2/
Generic Support forum: http://www.esp8266.nu/forum/viewforum.php?f=8

Post Reply

Who is online

Users browsing this forum: No registered users and 18 guests