Hello everyone,
I will put several questions here in this one post. Please bear with me.
Yesterday I managed to installed rtl_433 and rtl_433 MQTT Auto Discovery and today after hooking up RTL-SDR Blog V3 R820T2 via USB extension cable, I got info from three ThermoPro TX-2. sensors.
Here is the log from rtl_433
:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting rtl_433 with rtl_433.conf...
[rtl_433] rtl_433 version 21.12-101-g9eec4611 branch at 202204282249 inputs file rtl_tcp RTL-SDR
[rtl_433] Use -h for usage help and see https://triq.org/ for documentation.
[rtl_433] Publishing MQTT data to core-mosquitto port 1883
[rtl_433] Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
[rtl_433] Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
[rtl_433] Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
[rtl_433] Registered 186 out of 218 device decoding protocols [ 1-4 8 11-12 15-17 19-23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 163-168 170-175 177-197 199 201-215 217-218 ]
[rtl_433] Detached kernel driver
[rtl_433] Found Rafael Micro R820T tuner
[rtl_433] Exact sample rate is: 250000.000414 Hz
[rtl_433] [R82XX] PLL not locked!
[rtl_433] Sample rate set to 250000 S/s.
[rtl_433] Tuner gain set to Auto.
[rtl_433] Tuned to 433.920MHz.
[rtl_433] Allocating 15 zero-copy buffers
My first couple of questions:
It seems that some of the channels are skipped, particularly 162 - protocol 162 # ThermoPro-TX2 temperature sensor
which is the one I have - see next section - but apparently, it still works. But how do I enable it and even should I?
Secondly, only 433mhz signals are decoded.
Here is the log from rtl_433 MQTT Auto Discovery
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
mqtt found in this Home Assistance instance.
Starting rtl_433_mqtt_hass.py...
INFO:root:Discovering all devices
INFO:root:MQTT connected: Connection Accepted.
INFO:root:Subscribing to: rtl_433/+/events
INFO:root:Published Prologue-TH/9/1/102: time, channel, battery_ok, temperature_C, humidity, button
INFO:root:Published Prologue-TH/9/2/150: time, channel, battery_ok, temperature_C, humidity, button
INFO:root:Published Prologue-TH/9/3/105: time, channel, battery_ok, temperature_C, humidity, button
So I understand that Prologue-TH/9
is how devices are named and /1, /2 /3 are the channels they operate, so you know where are they. Good.
A question here - is there a way to rename them so I can have a little bit more human-friendly description in the dashboard?
When I looked at the Lov Viewer, I saw the following entry repeating number of times:
: Invalid datetime: sensor.prologue_th_9_1_102_utc provides state '2022-08-09 13:35:00', which is missing timezone information
I went back to rtl_433
and in the configuration file added "time:utc"
in it. After restart, the above logs entry stopped appearing, but now I see output from the sensons logged constantly:
time : 2022-08-09 14:11:40
model : Prologue-TH subtype : 9 id : 102
Channel : 1 Battery : 1 Temperature: 25.10 C Humidity : 41 % Button : 0
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
How do I stop logging it?
Also, adding time did not help to fix the ‘unknown’ error in the dashboard
Suggestions are welcome how to address all the above.