Hi
I've been trying to make the Rfxcom work with my BBQ thermometer, a Thermopro 20, but no luck. Anyone know if this is possible? I know that someone has made this (https://github.com/merbanan/rtl_433/releases) work with it, so maybe there is hope that this too could get into a future update of rfxcom?
br
RFXCOM and ThermoPro 20
Moderator: leecollings
-
- Posts: 7
- Joined: Tuesday 27 September 2016 9:56
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: RFXCOM and ThermoPro 20
Just bumping this. If anyone has ANY information about making the Thermopro devices working with Rfxcom I'd greatly appreciate it.
br
br
-
- Posts: 583
- Joined: Wednesday 16 December 2015 19:13
- Target OS: NAS (Synology & others)
- Domoticz version: 2022.2
- Location: Netherlands
- Contact:
Re: RFXCOM and ThermoPro 20
i would ask this question on the rfxcom site. they are the ones which need to integrate support
did you try all the protocols on the rfxcom to make sure it is not supported already?
did you try all the protocols on the rfxcom to make sure it is not supported already?
- JackD
- Posts: 68
- Joined: Monday 02 November 2020 20:53
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: RFXCOM and ThermoPro 20
Contact rfxcom. I did with a other device. They were very happy to take a look at my device to see if they could make it function with the rfxcom transceiver.
Or order a RTL-SDR receiver, cost you about €35,- I run both side by side without any problems.
Or order a RTL-SDR receiver, cost you about €35,- I run both side by side without any problems.
Re: RFXCOM and ThermoPro 20
I've ended up disconnecting Domoticz and Home Assistant from my USB dongles.
I now use Node-Red instead for all inbound wireless events (plus some outbound ones), and it's a breeze, it's much faster to setup, you just install Node-Red (through a Docker image on my Raspberry Pi, in my case), then the additional packages corresponding to all your wireless protocols and dongles (RfxCom, Enocean, Z_wave, Zigbee/Hue and so much more...).
Then you just create or update a flow, for all these protocols there is a node-red node for listening to wireless events, such as rfx-sensor or rfx-lights-in, then you link it to a debug node, it will then listen and show all data for the wireless events in the debug pane, then you can catch the values you want, transform it or pass it either to another API, and/or forward it elsewhere through an MQTT message.
When I receive an rfx event, I catch it from Node-Red by USB, then forward it to Domoticz and Home Assistant APIs to update the corresponding the virtual sensors in it, and send a copy of the event to my custom middleware API (PHP and Node.js) containing all my home logic.
This way all I can easily try, shutdown or remove any home automation app, since all the events are to and from node-red and my custom app.
Plus you can implement and refactor a good amount of logic at will, visually, within Node-Red flows, it's flexible, due to its low code context. Node-Red is awesome IMO.
I now use Node-Red instead for all inbound wireless events (plus some outbound ones), and it's a breeze, it's much faster to setup, you just install Node-Red (through a Docker image on my Raspberry Pi, in my case), then the additional packages corresponding to all your wireless protocols and dongles (RfxCom, Enocean, Z_wave, Zigbee/Hue and so much more...).
Then you just create or update a flow, for all these protocols there is a node-red node for listening to wireless events, such as rfx-sensor or rfx-lights-in, then you link it to a debug node, it will then listen and show all data for the wireless events in the debug pane, then you can catch the values you want, transform it or pass it either to another API, and/or forward it elsewhere through an MQTT message.
When I receive an rfx event, I catch it from Node-Red by USB, then forward it to Domoticz and Home Assistant APIs to update the corresponding the virtual sensors in it, and send a copy of the event to my custom middleware API (PHP and Node.js) containing all my home logic.
This way all I can easily try, shutdown or remove any home automation app, since all the events are to and from node-red and my custom app.
Plus you can implement and refactor a good amount of logic at will, visually, within Node-Red flows, it's flexible, due to its low code context. Node-Red is awesome IMO.
Who is online
Users browsing this forum: No registered users and 0 guests