better handling of new sensors and after battery change (sensors sending new battery flag) #3

New issue

Open

opened 2024-12-28 15:15:32 +01:00 by Flo · 0 comments

Flo commented

2024-12-28 15:15:32 +01:00

(Migrated from git.flokra.at)

Therefore when replacing the batteries on an existing sensor, it must be configured to it´s new ID every time.

Despite this there is another problem about this: sometimes a sensor will choose an ID that is already used by another sensor, leading to wrong published/logged data.

Enhancements:

check ID of every sensor sending the new battery flag against existing configured sensor IDs and:
- filter data from new sensor with existing ID
- send a notification when a new sensor is sending on an existing ID
send a notification whenever a new sensor with non existing ID is detected

Difficulties:

sensors seem to send the "new battery" flag for an extended time (more than 1h if not much more)

LaCrosse sensors select a random ID on every battery change. They then send a "new battery" flag for some time so that the console can be "paired" to that specific sensor by inserting their batteries. Therefore when replacing the batteries on an existing sensor, it must be configured to it´s new ID every time. Despite this there is another problem about this: sometimes a sensor will choose an ID that is already used by another sensor, leading to wrong published/logged data. Enhancements: - check ID of every sensor sending the new battery flag against existing configured sensor IDs and: - filter data from new sensor with existing ID - send a notification when a new sensor is sending on an existing ID - send a notification whenever a new sensor with non existing ID is detected Difficulties: - sensors seem to send the "new battery" flag for an extended time (more than 1h if not much more)