RFXcom new entity id every time thermometer starts

Configuration
1

I have a 433 MHz BBQ thermometer (Maverick ET-732) that I would like to connect to HA as a sensor. I can connect to it successfully using an RFXtrx433E but the problem is that every time I start the thermometer it gets a new entity id. So far I have the following entity id listed in HA.

sensor.0a4e010517460017fdec69_temperature
sensor.0a4e011327840018001879_temperature
sensor.0a4e011e5f230017002079_temperature
sensor.0a4e012563200017002269_temperature
sensor.0a4e013709b60023001c79_temperature
sensor.0a4e015a37040024001879_temperature
sensor.0a4e017bc83a0020001879_temperature
sensor.0a4e017c67000021001879_temperature
sensor.0a4e017d6fe10022001879_temperature
sensor.0a4e017ed8ba0022001879_temperature
sensor.0a4e017f9e0e0022001879_temperature
sensor.0a4e018029f40019001779_temperature
sensor.0a4e0181aecc001e001a79_temperature
sensor.0a4e0182fcd8001f001c79_temperature
sensor.0a4e01832d750020001d79_temperature
sensor.0a4e01846f400020001d79_temperature
sensor.0a4e0185cc1a0021001e79_temperature

Is there any way around this problem or will I just have to accept that every time that I start the thermometer I will have to edit the configuration in HA?

Another question is if there is any way to delete the obsolete sensors from the “Current entities” list beside deleting the whole database?

Regards
Bjorn

2

If you want to fix the issue, you will have to add a fix to the rfxtrx library we are using: https://github.com/Danielhiversen/pyRFXtrx

3

I have the same problem with a garden temperature sensor it gives a new id every time I put in new batteries.
Daniel are you saying add your code into the Hass dep folder to fix this problem?

4

Which fw are you running on your rfxcom?
I had this problem before with my Maverick and I think it became better when changing FW

5

@frelev Thank you for your suggestion but I am running the latest 1019 version of the EXT2 firmware. Do you know wich version you are running?

@Danielhiversen Could you please tell us some more about this? I am not a software developer but I am willing to have a look at it if you could push me in the right direction.

6

I switched from Ext2 to Type1. Can’t remember version number.

7

Just for the record it is the same problem with EXT firmware. Different id’s whenever starting up which is verified with RFXmngr from RFXcom.

Packettype = BBQ
subtype = BBQ1 - Maverick ET-732
Sequence nbr = 0
ID = 2725 decimal:10021
Sensor1 temp = 21 °C
Sensor2 temp = 22 °C
Signal level = 7 -64dBm
Battery = OK

Packettype = BBQ
subtype = BBQ1 - Maverick ET-732
Sequence nbr = 13
ID = B60C decimal:46604
Sensor1 temp = 22 °C
Sensor2 temp = 16 °C
Signal level = 7 -64dBm
Battery = OK

Packettype = BBQ
subtype = BBQ1 - Maverick ET-732
Sequence nbr = 22
ID = 6FE1 decimal:28641
Sensor1 temp = 23 °C
Sensor2 temp = 26 °C
Signal level = 7 -64dBm
Battery = OK

8

Since you are doing some testing.
Do you have the same problem with Type1?

From readme:

RFXtrx433-Type1 and RFXtrx433-Type2 firmware will operate in the RFXtrx433 and RFXtrx433E.
RFXtrx433-Ext and RFXtrx433-Ext2 firmware will only operate in the RFXtrx433E.
1 Like
9

That’s interesting. With Type 1 firmware the ID is always reported as zero. This is not ideal but at least it stays the same

Packettype = BBQ
subtype = BBQ1 - Maverick ET-732
Sequence nbr = 6
ID = 000 decimal:0
Sensor1 temp = 22 °C
Sensor2 temp = 22 °C
Signal level = 7 -64dBm
Battery = OK

Need to look further into this but perhaps this helps.

10

Did you get this to work stable?

I have problems with retrieving the updates to HASS
Don’t know if the distance is too far (30 m) but I even have a bigger antenna on my rfxcom

11

I decided to do it a bit differently. I connect the RFXtrx to Node-RED instead and then send the sensor values to Home Assistant via MQTT. This way I can present the same sensor name to HA whatever happens on the RFXtrx side.

I have only done some testing so unfortunately I can not comment anything about the reach of the signal yet.

1 Like
12

Could you give a quick overview of how you pulled that off? Am looking at Node-RED for the first time in more than two years, and I could need a push in the right direction.

Best regards
/tonkin

13

Sorry for the late reply but here is a quick description on how I did it.

  • I am using node-red-contrib-rfxcom which is installed to Node-RED

  • Using a rfx-sensor node I now can see all data that is decoded by RFXtrx433E by making an connection to a debug node

  • Using a switch node to filter out the signals that are of interest (msg.topic contains MAVERICK)

  • I then pass it to a function node that convert the value to something to pass on to MQTT. I also detects if a probe is not connected and in that case set the value to 0.

    // Correct values if probe not detected

    if (msg.payload.temperature.value[0] > 400){
    msg.payload.temperature.value[0] = 0;
    }

    if (msg.payload.temperature.value[1] > 400){
    msg.payload.temperature.value[1] = 0;
    }

    var bbq = {payload: {“bbq_meat”: msg.payload.temperature.value[0], “bbq_grill”: msg.payload.temperature.value[1]}};
    bbq.topic = “ha/sensor/bbq”;
    return bbq;

  • I then connect it to a MQTT output

  • In Home Assistent I set up a MQTT sensor that listens to specific topic

1 Like