Fredrik Öhrström

The Telegram class has all the already decoded data, so just use t->tpl_sts

Can you make a pull request? It makes it easier for me to see the code. You can write that it is a DRAFT, if you like.

Hi @rattinca ! I updated the ei6500 driver to use correct units for duration and counter. I.e. no longer strings but instead "duration_remove_h":1.3 (for 1.3 hours of removed) and "smoke_alarm_counter":0...

You can read https://github.com/weetmuts/wmbusmeters/issues/367 for how the tpl status byte is included into the "status" field. (PrintProperty::JOIN_TPL_STATUS)

Thanks @ElKaPa ! Yikes, that was a lot of bits. :-) I think I have added them all, but two questions from your table. The dust is 0-15 but you...

The driver is now complete! Many thanks @ElKaPa for helping out! @rattinca Please test. Note that the status field does not report smoke alarm, instead it is the smoke_alarm_date and...

I think we can close this one now!

Hello @landaisbenj ! We can try, but first we need the telegram data. wmbusmeters is the decoder that takes the bytes and understands them, but it does not know how...

You can also participate here: https://github.com/xaelsouth/rtl-wmbus/issues/26

You would do better than the others, if you are more persistent! ;-) It takes a couple of tries to capture suitable telegrams. The best tool is definitely rtl_433 since...