I’m seriously considering getting a second Veralite and I was wondering if there was a way that would allow both Vera’s to share the same rfxtrx433 device.
All the information would be going into Vera but I would like the option to use different Vera’s for different task, both of which benefit from the auto device creation etc.
Thought process is that I would have one vera dedicated to heating (so temp readings and thermostats etc) with the other using motion/lights (e.g LWRF) etc.
[quote=“parkerc, post:3, topic:180110”] i know Bert would like that - but to keep costs down
I was curious if something could be done with some of the installed software like ser2net etc. or maybe running externally?
I recall you mentioning something about that ages ago…[/quote]
It is possible to use a RFXtrx remotely in case you have the right software locally. I was able to make it work with the RFXtrx connected to a PC and the PC running a particular software (I don’t remember which one).
But that is not what you ask…
The question is about sharing a single rfxrrx433 between two Vera, ideally this would be done with it connected to one and feeding the other too. (To save having another machine running or buying a second transceiver
So I’m just thinking out loud and seeing what yours and others reading this thoughts are about the possibilities.
Your plugin currently captures everything that comes in, could that data be forwards to another Vera for it to use too?
No with only the current code.
But the plugin already include one action to receive a message and one action to send a message to the RFXtrx.
So relaying all received messages to another Vera and a “virtual” RFXtrx device should be doable using a UPnP call to invoke the action from the other Vera. Same thing to relay a command from the “virtual” device to the real device on the other Vera.
That would require 2 changes in the plugin:
defining new settings to identify the other Vera and the other Vera device to be adressed, and implemnting the relay of received messages through a UPnP call
defining a new mode for the plugin: no connection to a real RFXtrx but relaying of commands to another Vera through a UPnP call.
I think you’ve got it - thats sounds like it would allow someone to use one transceiver between two Veras[/quote]
I should check first that it is possible to invoke an UPnP action in a distant Vera…[/quote]
I hoped I could use the UPnP utility library used by the Sonos/DLNA plugins to invoke an action on another Vera.
Unfortunately, my code to parse the UPnP description file (XML) is not enough robust and does not work to analyze as I would like the description file returned by one Vera.
So I could not go further until I fix this issue.
But without this issue, I should have probably succeeded in invoking an action from the RFXtrx plugin on another Vera with only few lines of lua code !
There is certainly another way to do it, using a HTTP request. Maybe easier.
[quote=“parkerc, post:10, topic:180110”]Thanks for looking into it @lolodomo
How would the http request approach work?[/quote]
The general approach remains unchanged but the way to trigger the remote action is different, either a standard UPnP call (my initial idea) or a Vera specific HTTP request.
The HTTP request would be similar to this one but with another action and another parameter.
http://ip_address:3480/data_request?id=action&output_format=xml&DeviceNum=6&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1
A first request + a XML parsing will probably be necessary to identify the right device id of the RFXtrx device in the remote Vera, assuming only one RFXtrx device was created…
http://ip_address:3480/data_request?id=sdata&output_format=xml
Best Home Automation shopping experience. Shop at Ezlo!
i know Bert would like that - but to keep costs down