[announce] node-red-contrib-rfxcom node package published

[Max Hadley]

My collection of nodes for talking to 433 MHz home automation and sensor devices using the Rfxcom RFXtrx433 & RFXtrx433E USB transceivers are now available to be npm installed. Most of the recent changes have been bug fixes; the biggest enhancement is full support for hot-plugging & unplugging the RFX device without crashing node-RED (it may take a few seconds to reconnect: connection status is shown if enabled in the flows editor)

Enjoy!

Max Hadley

[Julian Knight]

Nice one Max. I'll soon be rebuilding my Pi so I'll give this a go with the brand new installation.

[Mike Biddell]

Max

I can only get about 8 metres range on my 433 mhz receivers..... I've tried several, with pull ups, pull downs, neither, potential dividers etc etc..... I might mess about with an OP amp buffer, but I might adopt your solution. What range do you get with RFXcom??

Mike

[Mike Biddell]

Max

also, could you please tell me the correct model RFXcom and where you bought it ????

cheers

mike

[Julian Knight]

Mike, my RFXCOM gives me range right through our rambling Victorian house. I have it set up in the loft and I can reliable control LWRF switches in the kitchen - 3 floors so at least 15-20m of old floors and at least one full brick wall. I even tried it in our boiler room which is in a brick outhouse attached to the back of the house.

[Mike Biddell]

Julian

Thanks for the response. Sounds wonderful. I am fed up with trying to get a suitable receive range out of cheap receivers !!!!! Are you using Max's flows? Which model RFXcom do you use and where did you buy it?

cheers

Mike 

[Julian Knight]

Hi Mikle, yes I'm using Max's node and it works great. I did need to make a slight code adjustment and I'm not sure if a fix has gone it. I'll be checking that out when I rebuild by Pi. I've been trying to force myself to get some more of the basics right first. Having been using my Synology NAS as a master for a while, I'm realising that I'm overcommiting the NAS so I need to move more stuff back to the Pi, not sure if I'll invest in one of the new Pi's - I probably will.

I'm using the RFXTRX433E, You can get this from a couple of different places but they are all the same price so I don't think it matters.
http://www.uk-automation.co.uk/products/RFXCOM-RFXtrx433E.html

I have it plugged into the Pi though, because it is USB, it could go in the NAS or elsewhere if needed, one of the reasons I went for it. It's expensive but it works very well and seems rock solid.

[Mike Biddell]

Julian

Thanks for the info..... I have just ordered the new PI.... 6 X faster !!!!! The RFXCOM device is expensive, but as you say..... it works. There is something odd about the PI GPIO. Normally the cheap 433 receivers have quite a good range, but when connected to the PI GPIO, they are poor. It must be a drive issue, so perhaps a buffer is required. Normally a decent Input/output system is voltage driven.... but in the case of the PI, I have my doubts !!!!! Or there is something odd about logic 1/0 voltage levels ????

Were there any setup problems with Max's stuff, or was it a simple npm install????

cheers

mike

[Julian Knight]

It wasn't a particularly easy setup though he may have fixed all the oddities now.

Here are my rather cryptic notes from the first time  around:

    RFXCOM
        requires separate version of rfxcom lib to be installed
        Install fails on Synology (686)
        https://groups.google.com/forum/#!topic/node-red/PeEsBssDmZA
        https://github.com/maxwellhadley/node-rfxcom
        https://github.com/maxwellhadley/node-red-nodes/tree/rfxcom

    maxwellhadley/node-red-nodes   --> ONLY /io/rfxcom - special version to work with node-red
        forked from node-red/node-red-nodes
            cd nodes
            git clone https://github.com/maxwellhadley/node-red-nodes.git node2 -b rfxcom
            mv node2/io/rfxcom core/io/rfxcom
            rm -R node2
            cd ..
            npm install https://github.com/maxwellhadley/node-rfxcom/tarball/master
            cd nodes/core/hardware
            wget https://github.com/node-red/node-red/blob/master/nodes/core/hardware/nrgpio
            wget https://github.com/node-red/node-red/blob/master/nodes/core/hardware/nrgpio.py
            chmod +x nrgpio*
            rm 36-rpi*
            wget https://github.com/node-red/node-red/blob/master/nodes/core/hardware/36-rpi-gpio.html
            wget https://github.com/node-red/node-red/blob/master/nodes/core/hardware/36-rpi-gpio.js
           
I also noted that while this worked OK on the Pi, the compile failed on the Synology NAS. Not really sure how much of this was actually needed and how much was me messing around :}

You don't need all that just to test that the RFXTRX433E is working though since there are Python libraries that work out of the box.

I seem to remember that the issue I had with the code was that it failed to understand some of the LightwaveRF codes. This was due to an issue in a big switch statement that only took numeric codes though the codes I was seeing were strings. Easily fixed by adding extra tests so that it understood both numeric and text codes.

[Max Hadley]

The NPM version of the nodes should pick up the modified version of node-rfxcom from my github repository automatically when installed. The issue Julian found should have been fixed too. But please let me know any other problems you may find.
I think much of the variability of performance arises from RFI generated by the computer to which the receiver is connected. Using the same RFXtrx433 unit, I can receive a neighbours weather sensor reliably using a cheap Compaq PC, but only occasionally with my iMac or BeagleBone. I have tried a couple of different aerials but they don't make as much difference.
Max

[Mike Biddell]

Thanks very much for the offer of help...... I may struggle !!!!!!! But I have found the support on this group, from various people, you, Julian, Dave etc to be excellent.

[Mark Setrem]

Mike,

Max started this thread by saying that the nodes can now be npm installed which means that you should be able to avoid the route that Julian took that predates this.

If you do install the node, if you go to http://flows.nodered.org search for rfxcom and follow the link it will be take you to the nodes page which includes the latest instructions on how to install.

If you are thinking of purchasing the rfxtrx it's worth checking that the devices you want interact with are supported, there's a long list on the rfxcom website.

[Julian Knight]

I thinkl you are right about the RFI Max. I am using the RFXTRX433E at the end of a fairly long USB lead well way from any of my computers.

When I connected up a listener flow for electricity sensors, I started picking up neighbours electricity monitors! Made me remember to filter the incoming signals anyway so that did me a favour. :)

On Saturday, 4 April 2015 20:37:02 UTC+1, Max Hadley wrote:

[Julian Knight]

I've now built my new Pi & have the rfx nodes installed.

However, I'm getting a couple of oddities.

Firstly I added a single rfx-sensor node connected to a debug. When I deployed, the rfx was picked up and I was getting messages but the indicator on the node stayed yellow "connecting". When I added the other nodes and redeployed, they stay as disconnected though I still get messages at least on the sensor node.

On Tuesday, 31 March 2015 22:03:14 UTC+1, Max Hadley wrote:

[Max Hadley]

I've seen the stuck at connecting issue myself, but it seems to be only the first time after a reboot for me. I don't think there is anything actually going wrong. When you redeploy, are you redeploying just changed nodes, or the whole flow? I tend to always use the whole flow option. Finally, can you check what happens when you disconnect the rfx while mode-red is running, and reconnect? It should give you 'disconnected' immediately, 'connecting' a few seconds after reconnecting, and 'OK' 5.5 seconds after that.

Max

[Julian Knight]

Hi Max, in normal operation, I rarely see better than the "connecting" status. If I pull the plug on the rfx and then put it back, that does work correctly (showing status of "OK (firmware 231)"). If I do a full deploy, it goes back to disconnected and stays there - though the system is working correctly.

[Max Hadley]

OK I'll look into this when I get home - holidaying on a boat on the Thames at the moment!
Cheers,
Max

[Julian Knight]

Nice! Enjoy the holiday.

Things seem to have settled down and appear to be working OK anyway at present. Probably because I've been restarting NR repeatedly.