RFXtrx plugin version alpha 8 released

Plugins & Plugin Development USB RFXtrx Transceiver
1

New version alpha 8 of the plugin has just been released.

To download the plugin files, use the Zip archive link at the bottom of this page.
Installation & Setup
Compatible products and limitations
Original topic with information in the first message

What’s new in version alpha 8:

  • Bug fixed: sending new commands failed after 255 commands
  • Init process optimized
  • lots of functions now declared as local functions
2

For people already running version alpha 7, only files I_RFXtrx.xml and L_RFXtrx.lua were updated.

3

Please note that I advice to update to this version as it corrects an important bug.

This version is a candidate for an official release. If I got no negative feedback in the coming days, it will be released on the App store.

4

Quote “For people already running version alpha 7, only files I_RFXtrx.xml and L_RFXtrx.lua were updated.”

Having uploaded only those 2 files - the RFXtrx device shows still as Alpha 7

Should the device be removed and re-added, or should all files be re-uploaded?

5

I don’t know what you have done wrong.
In any case, take the files from the ZIP archive.

6

Only uploaded the two files and after the reload it says Version alpha 8. if you are sure that your upload was correct and the reload didnt work you can try to remove the controllerwidget and reload it but you loose all your connected widgets that way… :o

7

Sorry - I was really stupid

I had only installed the Alpha 7 two days ago, and re-uploaded those 2 files from that version.

Now uploaded the correct ones

Thanks for confirming that it would work with just the 2 files.

  • Andrew
8

Thankyou! Working fine for me also.

On another note, while i am slowly getting to grips with Vera, its interface and Lua (not even looked at this yet but I assume i must at some point to achieve what i want to do), would it be a good idea to start a topic for hardware support requests for your awesome plug-in?
For example I have 5 door sensors that work just fine but show up as Light switches, while this is just cosmetic for me I would assume that this is something that yourself (lolodomo) and the community would like resolved as I can see in the log that there is a separate count for door sensors. It would be nice to arm/disarm these also but again for now this is just cosmetic.

50 11/21/12 19:54:40.123 luup_log:10: RFXtrx: door sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.124 luup_log:10: RFXtrx: motion sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.124 luup_log:10: RFXtrx: light switches: 11 <0x2c295680>
50 11/21/12 19:54:40.124 luup_log:10: RFXtrx: dim light switches: 0 <0x2c295680>
50 11/21/12 19:54:40.125 luup_log:10: RFXtrx: window covering: 0 <0x2c295680>
50 11/21/12 19:54:40.125 luup_log:10: RFXtrx: temperature sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.125 luup_log:10: RFXtrx: humidity sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.125 luup_log:10: RFXtrx: barometric sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.126 luup_log:10: RFXtrx: wind sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.126 luup_log:10: RFXtrx: rain sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.126 luup_log:10: RFXtrx: UV sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.127 luup_log:10: RFXtrx: weight sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.127 luup_log:10: RFXtrx: power sensors: 0 <0x2c295680>
50 11/21/12 19:54:40.127 luup_log:10: RFXtrx: security remotes: 0 <0x2c295680>
50 11/21/12 19:54:40.128 luup_log:10: RFXtrx: remote controls: 1 <0x2c295680>
50 11/21/12 19:54:40.128 luup_log:10: RFXtrx: heating devices: 0 <0x2c295680>

Also I would like to see if I can get my Wattson energy monitor supported within this plug-in. It is detected as an OWL CM113 and I know it is not currently supported within this plug-in but is by RFXtrx443 so I thought this might be an ideal place to start to get my head around Lua, but not being a programmer, I need pointing in the right direction to get started (or even get it to work, or advice to quit if this device is a waste of effort)

Anyway, thanks for this awesome piece of work, it was the reason I purchased a Vera and a RFXtrx443. I have only been at HA for a few weeks now but if this plug-in did not exist I would have gone down a different route.

I hope to be able to contribute in the near future and not just be a requester.

9

Now I will probably not spend a lot of time myself to add support for new hardware. But contributors are welcome.
At least, I will try to follow the RFXtrx firmware versions and add what is easy to add.

For example I have 5 door sensors that work just fine but show up as Light switches, while this is just cosmetic for me I would assume that this is something that yourself (lolodomo) and the community would like resolved as I can see in the log that there is a separate count for door sensors. It would be nice to arm/disarm these also but again for now this is just cosmetic.

I have nothing to identify a light from a motion sensor if you are talking about Chacon for example.
The change is not as easy as you could imagine. I already thought about that several times and I never found what could be the best implementation.

Also I would like to see if I can get my Wattson energy monitor supported within this plug-in. It is detected as an OWL CM113 and I know it is not currently supported within this plug-in but is by RFXtrx443 so I thought this might be an ideal place to start to get my head around Lua, but not being a programmer, I need pointing in the right direction to get started (or even get it to work, or advice to quit if this device is a waste of effort)

You could look at how I managed the 119/160/180 but the 113 is managing three channels and the existing Vera device is not adapted for that. An idea could be to manage several devices, one for each channel ? Or create a new device ?
I think this is the preliminary thoughts to have.

I hope to be able to contribute in the near future and not just be a requester.

You are welcome.

10

This might sound like a bit of a newbie question… but I try not to be a newbie…

I have version 6 currently installed - is there a simple method to update to version 8? When I went from 5 to 6, I somehow corrupted everything, and had to re-create all my devices. Am I missing something?

Thanks

11

Just upload the new files and reload.
No need to delete devices.

12

Hi
I just installed this and it installed great. I have a few issues
The temperature sensors are showing up but are in Celsius, my MIOS otoh is set to Fahrenheit. I saw an earlier post where I thought the issue was rectified, a regression perhaps?
Also I’m only picking up ones that are in close proximity. From the manual it’s range depends on protocols enabled. I’m only using Oregon Scientific equipment , can I just disable the rest.
If that doesn’t help, what’s the max distance you guys see and how long of a USB cable would be ok (trying to position it better / closer to the sensors)

13

[quote=“syyid, post:12, topic:173348”]Hi
I just installed this and it installed great. I have a few issues
The temperature sensors are showing up but are in Celsius, my MIOS otoh is set to Fahrenheit. I saw an earlier post where I thought the issue was rectified, a regression perhaps?[/quote]

No, you have to select Fahrenheit in the Settings tab.

Also I'm only picking up ones that are in close proximity. From the manual it's range depends on protocols enabled. I'm only using Oregon Scientific equipment , can I just disable the rest.

Yes

If that doesn't help, what's the max distance you guys see and how long of a USB cable would be ok (trying to position it better / closer to the sensors)

Oregon sensors can be relatively far from the RFXtrx. Mine are in different rooms of my house without problem.

14

@lolodomo: Thanks a bunch, that worked great :slight_smile:

15

Hi,

Ok - so I am new to this but got Alpha 8 installed ok and it’s picking up all my neighbours switches, remotes and power meters! (is that not a security problem btw?!)

I manually added a lightwaveRF 2-gang power socket and can control it after pairing. The problem is if the sockets are manually controlled from the buttons on the front it doesnt update the status of the device on the vera3… is that expected? if not then what have I done wrong?

I couldnt find any documentation on how to manually add so I simply typed in a remote id and unit code (1,1 and 1,2) then put the corresponing plug into learning mode and then used newly created vera device to turn it on - pairing completed successfully then repreated the process for the second plug.

Thanks in advance,

Sam

16

Yes, I believe. LightwaveRF is probably not bi-directional like Z-Wave is. That would mean that local action is not RF transmitted and so not received by the RFXtrx.

17

oh - thats a big :frowning: then!!

I guess I will abandon LightwaveRF then… seems useless unless it’s bidirectional.

18

http://www.automatedhome.co.uk/reviews/lightwaverf-home-automation-system-in-depth-review.html

Go to the conclusion. Maybe it is possible but not yet available or not implemented in all units ?

19
Strengths •Probably the most stylish suite of home automation components currently on the market. •Competitively priced. •Good range of products and modules for automation, though sensors are core functionality only. •Available in a range of finishes to match your home.

Weaknesses
•One-way communications means there are no acknowledgements or status requests. This may arrive as an update later as it claimed to be supported by the protocol but, it hasn’t arrived yet.
•The one-way communication also means that devices can’t report battery status.
•Point to point radio means it has limited range, without using repeaters.
•No published APIs to enable integration with other systems (though the interfaces have been reverse engineered and published on-line).
•The remote control capbility has a dependency on the LightwaveRF server in the cloud.
•Currently limited to 8 rooms only.
•LightwaveRF is the only developer of the hardware, which has limited the range of devices and its growth.

20

Thanks for clearing that up.

Oh well… back to to zwave and forget about style for a while longer I guess :frowning: