Temp/humidity values not processed anymore

I use a Renkforce temp/humidity sensor control a fan in my bathroom. I have this running for over a year without any problems. But last saterday I noticed the fan wasn’t controlled anymore. I looked at the information within the rfxcom plugin. I saw the last received values were from friday evening around 8:15 PM. While these values should be processed every minuut (yes really).

  • disconnected/reconnected rfxcomXL
  • connected rfxcom to my laptop and with the rfxcom manager I saw the values comming every minuut.
  • back to Vera, nothing happens here.
  • rebooted Vera

Still the values were not updated.

I removed the device in rfxcom plugin. Then I did the auto discover. A new device was discoverd, in fact even 2. with ID 57602 and 57610. 602 was updated every minute, 610 was updated with random minutes. I decided to remove 610. After that, it was working again. o btw I changed the Rnkforce to channel 2, instead of 1.

BUT, until yesterday evening, again around 8:15PM. The values were not processed again/seen by the rfxcom plugin.

How is this possible? I didn’t change anything on my Vera! I only have 1 Renkforce.

Ok did some debugging:

In the GUI you see this:

And with debuggin on, I see this every minute in de LUA log:
50 08/25/20 12:37:35.401 luup_log:21: RFXtrx: dbg: Received message: 0A 52 09 DB E1 0A 00 DD 44 01 59 <0x73f21520>
50 08/25/20 12:37:35.402 luup_log:21: RFXtrx: dbg: typeof value: string <0x73f21520>
50 08/25/20 12:37:35.403 luup_log:21: RFXtrx: dbg: setVariable - deviceNum: 21 variable: LastReceivedMsg value: 0A 52 09 DB E1 0A 00 DD 44 01 59 <0x73f21520>
50 08/25/20 12:37:35.404 luup_log:21: RFXtrx: dbg: setVariable - deviceNum: 21 variable: VeraTime value: 1598351855 <0x73f21520>
50 08/25/20 12:37:35.406 luup_log:21: RFXtrx: dbg: findChild-> parentDevice: 21 altid: TH9/57610 deviceType: urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x73f21520>
50 08/25/20 12:37:35.407 luup_log:21: RFXtrx: dbg: devicenum found in table - key: TH9/57610urn:schemas-micasaverde-com:device:TemperatureSensor:1 devicenum: 0 myDevice: false <0x73f21520>
50 08/25/20 12:37:35.408 luup_log:21: RFXtrx: dbg: findChild-> parentDevice: 21 altid: TH9/57610 deviceType: urn:schemas-micasaverde-com:device:HumiditySensor:1 <0x73f21520>
50 08/25/20 12:37:35.408 luup_log:21: RFXtrx: dbg: devicenum found in table - key: TH9/57610urn:schemas-micasaverde-com:device:HumiditySensor:1 devicenum: 0 myDevice: false <0x73f21520>
50 08/25/20 12:37:35.409 luup_log:21: RFXtrx: dbg: actOnCommands:cmds: TH9/57610 Temperature 22.1 TH9/57610 Humidity 68 TH9/57610 CommStrength 5 TH9/57610 BatteryLevel 100 <0x73f21520>
50 08/25/20 12:38:32.409 luup_log:21: RFXtrx: dbg: Received message: 0A 52 09 DC E1 0A 00 DD 44 01 59 <0x73f21520>
50 08/25/20 12:38:32.409 luup_log:21: RFXtrx: dbg: typeof value: string <0x73f21520>
50 08/25/20 12:38:32.410 luup_log:21: RFXtrx: dbg: setVariable - deviceNum: 21 variable: LastReceivedMsg value: 0A 52 09 DC E1 0A 00 DD 44 01 59 <0x73f21520>
50 08/25/20 12:38:32.412 luup_log:21: RFXtrx: dbg: setVariable - deviceNum: 21 variable: VeraTime value: 1598351912 <0x73f21520>

50 08/25/20 12:38:32.414 luup_log:21: RFXtrx: dbg: findChild-> parentDevice: 21 altid: TH9/57610 deviceType: urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x73f21520>
50 08/25/20 12:38:32.414 luup_log:21: RFXtrx: dbg: devicenum found in table - key: TH9/57610urn:schemas-micasaverde-com:device:TemperatureSensor:1 devicenum: 0 myDevice: false <0x73f21520>
50 08/25/20 12:38:32.415 luup_log:21: RFXtrx: dbg: findChild-> parentDevice: 21 altid: TH9/57610 deviceType: urn:schemas-micasaverde-com:device:HumiditySensor:1 <0x73f21520>
50 08/25/20 12:38:32.416 luup_log:21: RFXtrx: dbg: devicenum found in table - key: TH9/57610urn:schemas-micasaverde-com:device:HumiditySensor:1 devicenum: 0 myDevice: false <0x73f21520>
50 08/25/20 12:38:32.432 luup_log:21: RFXtrx: dbg: actOnCommands:cmds: TH9/57610 Temperature 22.1 TH9/57610 Humidity 68 TH9/57610 CommStrength 5 TH9/57610 BatteryLevel 100 <0x73f21520>

So, the correct/real/actual values are received by Vera every minute, but for some reason the Vera or better said the devices are not updated with the new values.

Other thing I noticed: This morning the last update was somewhere about 22 hours. When I wanted to debug just now, the values were updated 22 minutes ago. It also seems that it was updated when I set the rfxcom to debuggin, but after this no updates in the interface anymore.

Why o why is this suddenly happening, again nothing changed in my Vera (or it must have been something automaticly, but don’t know what.

All 433Mhz sensors transmit an ID as part of the message they transmit to the transceiver. For most battery operated devices the value of this ID is created randomly when a battery is first installed - or when a battery is replaced. So if a device is used to trigger a scene and the battery in the device fails this is often the reason the scene is no longer triggered; the device ID has changed and is no longer recognized.
I have 20 temperature/humidity sensors connected to my RFXtrx transceiver. If I select the “Temperature and Humidity Sensor Data” tab of the RFXtrx device it shows the min and max values collected AND the time since the last data was received from that device; the “Age” value. Usually this value is never more than a few minutes and is often less than 1 minute.
If the battery in a battery powered device has been changed the device’s new ID has to be found. The best way to do this is to enable AutoCreate and wait for new devices to appear. In your case look for a new device beginning with TH9/. Note the numeric part of the device ID that follows TH9/. If more than one device is created it’s usually not difficult to determine the correct one. Often, some device messages will not be received often enough to decode sensor values or values displayed will be obviously incorrect. Once you have noted the new ID value, turn off AutoCreate and using the RFXtrx interface delete all of the newly created devices - including the correct one. This will cause an luup reload. Once that completes (watch the LEDs on the Vera) go to the sensor device that was no longer being updated and edit the numeric part of the altid (in Advanced -> params) to match the numeric part of the ID noted previously. If this is both a temperature and humidity sensor you’ll need to do this for both devices.

Are you saying the battery died? As the interface is still stating 100%. And the issue occured NOT after doing something with batteries. IT suddenly occured.

I just checked. Lua log is talking about TH9/57610 and the device altid is HS/TH9/57602. What to do? Should I change to exactly match the logs? I tried both but still no updates:

Still wondering, why did it work with the same batteries for more then 24 hours and then suddenly the GUI is not updated anymore?

As said, I deleted ALL yesterday, including the old one and started from scratch.

All I can tell from the screen shot is that messages from devices 135 and 136 have not been received in more than 3 hours. If I assume that the sensor or RFXtrx have not been moved then it could indicate weak batteries or it could mean that the transmitted device ID has changed. Again, this usually only happens when batteries are replaced but if the battery contacts are not clean or the battery is weak or the sensor is bumped and the battery loses contact just briefly. Can you tell me the model number of this Renkforce sensor? The RFXtrx User Guide only mentions a Renkforce smoke detector.

If the model number is FT007TH that is similar to Ambient Technology’s F007TH. The two devices look exactly the same. This also matches Telldus FT007TH.
I have 6 of the Ambient devices. They work well but sometimes I get transient readings - very high or very low temperatures. This may point to a need for improvement in how the RFXtrx decodes messages from these devices.

Yes indeed it’s the F007TH.

But when I tail (SSH) the Lua log I see the current and thus correct values being logged. While the interface is saying it has not been updated in the last 3 hours. And that is NOT true looking at the logs.
So, the battery is ok, else it wouldn’t sent updates to the Vera every minute.

I just deleted all the devices created for this F007TH. And auto created a new one. Now the ID is TH9/8705 and only 1 is created. I also placed new batteries in the unit. The last hour, the age is 0 or sometimes max 1 minute.

I will let you know.

In the future keep in mind that if you have scenes triggered by these sensors and you delete the device then you will have to re-create those scenes. The original scenes may still exist but they will not work Although it is tedious it’s best to use the method I described above when the batteries are changed in a sensor type device.

Hopefully is has been fixed now and thanks for the information about the ID.

I don’t use it in scenes, I only use it with the plugin Reactor. And there I had to re-add the newly created devices.

O btw any update about the 1.96 version as I had to downgrade to 1.87, because of the Somfy issue?

One year later, and exact the same issue pops up. All by itself it gets a new ID. I tried as @tinman said. I looked up the new ID with a ssh session in the logs. But it when I change the altid into the new value, it won’t update with new values. In the end, I deleted the old devices and auto created new ones.

Best Home Automation shopping experience. Shop at getvera!

© 2021 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules