the remote control provided seem to be a universal tv tuner associated with tv pc card compatible with win XP,7,8 .After searching with Nooelec I found this technical reply. The purpose of the remote that I received with my NESDR is only to be used for DVB video, it is not designed for SDR purposes. It can be used anywhere that there are DVB signals, but you won’t find these in the USA or Canada. In North America, we use ATSC signaling, which is not compatible with this device.
Very informative. I have not been able to find out if the conf file is required. Also, a little confused about the setup of it with the "next" version coming from the prior. The part that starts here. s[/type][/model][/subtype][/channel][/id],events=rtl_433/9b13b3f4-rtl433/events,states=rtl_433/9b13b3f4-rtl433/states. What model, subtype, channel, ets. How is this setup? Any idea what the difference is with it/without?
I have ended at MQTT binding in HA, I do not see any RTL_433 device under MQTT - any advice please? In the 433 (not next!) i see the discovered sensors... with 433 (next) i see error only
The downside I found with doing 433mhz sniffing uaing Home Assistant is you end up with thousands on entities that it finds. Home Assistant doesnt allow you to bulk delete entities so you need to do this one at a time. The cream on the cake is that if you have intgrated Alexa with Home Assistant you can end up with all these 433mhz found entities in your alexa device list. Again no way to bulk delete these devices. My view is dont do this on your production Home Assistant!!
RTL_433.conf is a configuration from the project merbanan/rtl_433 . For me its located in /etc/rtl_433/rtl_433.conf . You select the protocol you intend to listen to from the list of 256 protocol available. Simply copy the lines you interested in and only those device will be reqistered for listning by HA
the remote control provided seem to be a universal tv tuner associated with tv pc card compatible with win XP,7,8 .After searching with Nooelec I found this technical reply. The purpose of the remote that I received with my NESDR is only to be used for DVB video, it is not designed for SDR purposes. It can be used anywhere that there are DVB signals, but you won’t find these in the USA or Canada. In North America, we use ATSC signaling, which is not compatible with this device.
I cant not see anything on the broker side. do you need to configure the USB dongle ?
Very informative. I have not been able to find out if the conf file is required. Also, a little confused about the setup of it with the "next" version coming from the prior. The part that starts here. s[/type][/model][/subtype][/channel][/id],events=rtl_433/9b13b3f4-rtl433/events,states=rtl_433/9b13b3f4-rtl433/states. What model, subtype, channel, ets. How is this setup? Any idea what the difference is with it/without?
Nice idea
Can it be used without MQTT??
im sure it can be but i am not aware of how
MQTT does not show anything, is there any conf_file needed? Please, help
I have ended at MQTT binding in HA, I do not see any RTL_433 device under MQTT - any advice please? In the 433 (not next!) i see the discovered sensors... with 433 (next) i see error only
I have similar issue. I see the discovered/sniffed devices in log of rtl(next) add-on but mqtt does not see anything.
The downside I found with doing 433mhz sniffing uaing Home Assistant is you end up with thousands on entities that it finds. Home Assistant doesnt allow you to bulk delete entities so you need to do this one at a time. The cream on the cake is that if you have intgrated Alexa with Home Assistant you can end up with all these 433mhz found entities in your alexa device list. Again no way to bulk delete these devices. My view is dont do this on your production Home Assistant!!
you are correct.
RTL_433.conf is a configuration from the project merbanan/rtl_433 . For me its located in /etc/rtl_433/rtl_433.conf . You select the protocol you intend to listen to from the list of 256 protocol available. Simply copy the lines you interested in and only those device will be reqistered for listning by HA