Newbie here and just received my Vera Lite and RFXtrx433 this afternoon. Superb work by lolodomo on the plugin! I have both units at the latest firmware i.e. RFXtrx at 49 and Vera Lite at 1.5.408. I have followed the instructions and installed the RFXtrx files from lolodomo’s alpha5 page. I haven’t installed any of the wind or UV files.
I cannot seem to get the system to recognise my LightwaveRF items. I have tried some ByeByeStandby items and they automatically appear but the LightwaveRF controller doesn’t even trigger the yellow receive led on the RFXtrx unit. I tried the RFXmngr.exe and can capture the LightwaveRF signals and in turn control switches and lights.
Is there something I have to set to enable the LightwaveRF on the plugin?
Any help would be greatly appreciated.
Thanks.
Update: I manually added a couple of LightwaveRF items via the plugin and they can now be controlled by vera. I basically copied the handheld controller ID so didn’t need to pair the items to the Vera. The Vera still does not catch that the handheld controller has turned items on or off so something stil isn’t right. I must be doing something stupid.
I’ve got several LightwaveRF magnetic contacts, remote controls, and a dusk/dawn sensor. They all work really well with this plugin. As soon as you activate a remote or sensor then a binary switch device is created automatically (e.g. for each on/off button). I don’t have any switch devices, so I’m only using the receive functionality.
I can’t recall what protocols I enabled for LightwaveRF with the RFXtrx433 using the utility program. One thing I did do was update the firmware on the RFXtrx433 before connecting it to Vera.
Thanks jtmoore for your help. I had another play this morning and now have it working as expected. Basically, I disabled all protocols I didn’t need leaving only AD and ARC enabled. It works superbly well. Some of the other protocols must have been preventing the LightWaveRF from working.
Thanks again to lolodomo for his plugin.
@apmcconv
See chapter 2.3 in the RFXtrx User Guide.pdf (on the RFXCOM download page)
The LightwaveRF (AD) protocol is blocked if the ATI protocol is enabled.
On the other hand, the enabled AD protocol will influence some other protocols. For example some Oregon 3.0 sensors are no longer received if AD is enabled.
Development idea/suggestion. Would it be possible to create another tab on the RFxrftx Controller Device that shows you all the information being received by the transceiver? Currently I have to detach the device and plug it into my PC to check what sort of information rfxmngr is seeing?
Development idea/suggestion. Would it be possible to create another tab on the RFxrftx Controller Device that shows you all the information being received by the transceiver? Currently I have to detach the device and plug it into my PC to check what sort of information rfxmngr is seeing?[/quote]
At my opinion, not possible with the Vera UI using flash. I don’t know if it would be possible with JavaScript.
What I could do easily is log all messages. But it would generate more traffic in the log file. Would it help ? I could make it as an option (through a parameter).
@lolodomo - thanks so much for responding, you’re right, writing to the logs would add alot of traffic, plus you would also need to be logged in via SCP to view the files. (not very end user friendly)
I like your idea of having an ‘option’ to enable logging, and that may be the way to go, but out of curiosity, could you write the rfxrtx data to its own dedicated log file? And if you could do that, is there any reason why that log file could not be made visible via the UI (with a refresh option)?
I did look at the datamine plugin in, to see if that tool was an option, but it looks like it only captures the variables of existing devices, so I would nit be ble to see all the details that the Rfxrtx receives if I wanted to any troubleshoot etc…
[quote=“parkerc, post:489, topic:170604”]@lolodomo - thanks so much for responding, you’re right, writing to the logs would add alot of traffic, plus you would also need to be logged in via SCP to view the files. (not very end user friendly)
I like your idea of having an ‘option’ to enable logging, and that may be the way to go, but out of curiosity, could you write the rfxrtx data to its own dedicated log file?[/quote]
The free space available in /tmp is I imagine very small. It would not be possible to let the file grow too much. So that would be something additional to manage.
And if you could do that, is there any reason why that log file could not be made visible via the UI (with a refresh option)?
With the flash UI, there is no field type to match a file content. You have labels, buttons, input fields, …
[i]I did look at the datamine plugin in, to see if that tool was an option, but it looks like it only captures the variables of existing devices, so I would nit be ble to see all the details that the Rfxrtx receives if I wanted to any troubleshoot etc..
[/i]
What would be probably doable is to keep in a variable for example the last 20 commands received. The variable would be updated each time a new command is received. And in bonus, it should be possible de display the content of this variable in the UI (in an input field) in case of the multiline is possible (to be checked).
Sounds very interesting, and if like you said, you could present the variables in a similar way to rfxmngr - that’s it! You could then see what the transceiver is seeing to help check or troubleshooting anything
I’ve found my old ATI RF Remote Wonder, so if you want to implement the functionality and have someone test it for a future release - just let me know.
I’ve found my old ATI RF Remote Wonder, so if you want to implement the functionality and have someone test it for a future release - just let me know.[/quote]
I will try to finish security and remote stuff this week-end…
I’ve been absent from my home for 6 month (my son was born in the Miami recently), going back soon
There are plenty of LWRF remotes in my possession, and it could be very nice to use them to control all my Z-Wave && LWRF stuff - they are so much cheaper than any Z-Wave remote…
May be I missed something - but is possible at all? (bearing in mind your latest plugin improvements)
I’ve been absent from my home for 6 month (my son was born in the Miami recently), going back soon
There are plenty of LWRF remotes in my possession, and it could be very nice to use them to control all my Z-Wave && LWRF stuff - they are so much cheaper than any Z-Wave remote…
May be I missed something - but is possible at all? (bearing in mind your latest plugin improvements)[/quote]
Hi Shapa (and congratulations).
Please read the last message in the previous page, I have done changes last week for a better management of remotes. This is not yet finished (not all buttons are managed, only light/switch ON and light/switch OFF buttons). I initially explected to do it last week-end but finally I finally had other activities. I will certainly update the plugin during the week ane hope to be able to release a new alpha version next week-end.
Got my usb rfxtrx today and I like it already, however for some reason it only detects one button on my Elro ab440R remote,
this creates a device and when i put the switch on that combo on remote D, it works, however can’t seem to create the other devices.
When i go into the settings I see I can add a device but the UI is all messed up (see screenshot) so seems I can not set the values correct.
Can i assume that the on the remote the D off is code K15 that all the rest is K14 K13 K12 ?
Nothing to do with the ELRO AB400 receiving but see also chapter 2.3 which receive protocols are degraded or even stop receiving if another protocol is enabled.
And for the second problem (UI all messed up), this is the known firmware bug introduced by MCV in version 1.5.408.
So either you return to firmware version 1.5.346 and it will work well, or you wait for a new firmware update.
You can remind MCV of the problem sending a new message in the topic dedicated to the firmware 1.5.408. I have already done in the past but I hope this will not be forgotten by MCV…
Sounds very interesting, and if like you said, you could present the variables in a similar way to rfxmngr - that’s it! You could then see what the transceiver is seeing to help check or troubleshooting anything ;)[/quote]
But the message logged will be a non-decode message.
I am not really sure to understand what could the usage…
