Alecto WS1200 - 40 degrees temperature offset
Posted: Tuesday 01 March 2016 21:04
Hi,
My Alecto WS-1200 shows a temperature offset of +40 degrees celsius in Domoticz. I had this problem for a while now and added a -40 offset in Domoticz. The only problem is that for temperatures below zero, the +40 offset is absent and the temperatures are reported correctly, but because of the offset setting in domoticz these values are now being reported 40 degrees too low.
I read in the firmware release notes that some work was done on the Alecto V3 protocol so Last night I flashed the r37 release of the RFlink firmware but the offset is still present for positive temps
Furthermore, in my device list in domoticz I noticed two Alecto V1 temp sensors (not owned by me) which are reporting temperatures of 56 and 53 degrees Celsius which I guess should be 16 and 13 (Netherlands in house).
I'm using Domoticz v2.3768 on a Rpi. It said there weren't any updates but I just checked the site are there's a much newer version, so I will try this also, but it seems to me like this is a RFlink firmware issue (something to do with that Alecto V3 uses a base value of -400?)
My Alecto WS-1200 shows a temperature offset of +40 degrees celsius in Domoticz. I had this problem for a while now and added a -40 offset in Domoticz. The only problem is that for temperatures below zero, the +40 offset is absent and the temperatures are reported correctly, but because of the offset setting in domoticz these values are now being reported 40 degrees too low.
I read in the firmware release notes that some work was done on the Alecto V3 protocol so Last night I flashed the r37 release of the RFlink firmware but the offset is still present for positive temps
Furthermore, in my device list in domoticz I noticed two Alecto V1 temp sensors (not owned by me) which are reporting temperatures of 56 and 53 degrees Celsius which I guess should be 16 and 13 (Netherlands in house).
I'm using Domoticz v2.3768 on a Rpi. It said there weren't any updates but I just checked the site are there's a much newer version, so I will try this also, but it seems to me like this is a RFlink firmware issue (something to do with that Alecto V3 uses a base value of -400?)