Domoticz

I have bunch of cheap Viking temp sensors attached to my system through a Rfxcom433 transciever. They have worked very well for about a year, but all of a sudden my outdoor sensor stopped reporting data. My quess was this was due to low battery, but I couldn't check this until this weekend since it is located at my summerhouse.

Once I got to my summerhouse I found out the battery probably was low. At least it was very difficult to read out the display. So I replaced the batteries and waited for the sensor to start report data again. But nothing happened. Then I tested to "Allow new hardware" for 5 minutes. All of a sudden the temp sensor showed up again with a new id! Before the sensor showed up with id 0c00 and now a new sensor is available with id 1c00.

Does anyone know how the Fineoffset/Viking protocol works? Is the id something the protocol assigns to the device, or is it tied to the hardware? I can't really figure out how this happened. Is it common the id change when you replace the battery?

And one more question. Can I inherit old data so I have the history available under the new sensor id?

ubee wrote: ↑Saturday 17 February 2018 9:08 Does anyone know how the Fineoffset/Viking protocol works? Is the id something the protocol assigns to the device, or is it tied to the hardware? I can't really figure out how this happened. Is it common the id change when you replace the battery?

I use several Crest Temp+Hum sensors and they do exactly the same when when the battery is changed, so this looks like normal behavior. I think you can 'replace' the sensor for another in the edit menu.

SweetPants wrote: ↑Saturday 17 February 2018 9:47

ubee wrote: ↑Saturday 17 February 2018 9:08 Does anyone know how the Fineoffset/Viking protocol works? Is the id something the protocol assigns to the device, or is it tied to the hardware? I can't really figure out how this happened. Is it common the id change when you replace the battery?

I use several Crest Temp+Hum sensors and they do exactly the same when when the battery is changed, so this looks like normal behavior. I think you can 'replace' the sensor for another in the edit menu.

SweetPants is 100% correct in the answer it happens to these sensors and you can replace the sensor as described on page 20 in the Domoticz manual.

To replace the old sensor data to the new device act as follow:

• First, add the new device to the system, and call it for example ‘New Temp Meter’.

• Next press the Edit button on the Old device, select replace and select the new Device. (In this case the devices called
  ‘New Temp Meter’.

• Next press OK.

• Now you can rename the new device back to ‘Temp Meter’.

Ok, it works but it is far from a smooth procedure. Especially when you have the sensor connected to a remote Rasp. Then this change must be propagated over the remote interface as well.

I managed to replace the sensor and the history is now available. But I still have problems to find it on the master device. The new device is enabled on the remote interface under the right user.

If I have to do this every time I change batteries in about 10 sensors, it will keep me busy.... And then I need to check the floorplans as well to see if those are affected!

Hehe it is a hardware limitation. I have about 6 of these sensors. Don't use a remote pi. Have rflink via lan to deal with my coverage issue. And I only change batteries one at a time. Otherwise I don't know what sensor ends up where