We have moved at community.getvera.com

Author Topic: RFXtrx plugin version beta 3 released  (Read 72822 times)

Offline n0ir

  • Sr. Member
  • ****
  • Posts: 352
  • Karma: +4/-1
Re: RFXtrx plugin version beta 3 released
« Reply #45 on: December 07, 2014, 05:16:17 pm »
Is it possible to backup all created devices somehow? I'm going to buy a Vera Edge and will have to take the plunge from UI5 to UI7. I am a bit worried all my ~30 433MHz devices will vanish (like earlier when I have uinstalled the plugin).
I'm interested in that too. I'd like to try UI7 some day but don't want to reconfigure it all.
There is a backup button somewhere but it is not documented anymore, I don't want to mess with it (my wife would kill me... again :p)

Lolodomo? Any info on backup the setup?

Offline lolodomo

  • Moderator
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: RFXtrx plugin version beta 3 released
« Reply #46 on: December 07, 2014, 05:43:44 pm »
When upgrading a VeraLite or Vera 3 to UI7, when it works well, you keep all your previous devices. So all the devices managed by the RFXtrx plugin will still be there after the upgrade.
Of course, you must do a backup before upgradin,g in case something is going wrong and you would have to downgrade.

Offline hyzteric

  • Jr. Member
  • **
  • Posts: 77
  • Karma: +0/-1
Re: RFXtrx plugin version beta 3 released
« Reply #47 on: December 09, 2014, 07:18:40 am »
Thanks for the info.

Offline n0ir

  • Sr. Member
  • ****
  • Posts: 352
  • Karma: +4/-1
Re: RFXtrx plugin version beta 3 released
« Reply #48 on: December 13, 2014, 07:01:15 pm »
When upgrading a VeraLite or Vera 3 to UI7, when it works well, you keep all your previous devices. So all the devices managed by the RFXtrx plugin will still be there after the upgrade.
Of course, you must do a backup before upgradin,g in case something is going wrong and you would have to downgrade.

Sounds great if you?re upgrading a Vera from UI5 to UI7, but I'm thinking about buying a new Vera Edge. Is it possible to externally backup files from my old Vera Lite and transfer them to the new Vera Edge?

EDIT: Is it possible to use RFXtrx433 with the new Vera Edge at all?!
« Last Edit: December 14, 2014, 03:53:15 am by n0ir »

Offline lolodomo

  • Moderator
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: RFXtrx plugin version beta 3 released
« Reply #49 on: December 14, 2014, 04:30:43 am »
When upgrading a VeraLite or Vera 3 to UI7, when it works well, you keep all your previous devices. So all the devices managed by the RFXtrx plugin will still be there after the upgrade.
Of course, you must do a backup before upgradin,g in case something is going wrong and you would have to downgrade.

Sounds great if you?re upgrading a Vera from UI5 to UI7, but I'm thinking about buying a new Vera Edge. Is it possible to externally backup files from my old Vera Lite and transfer them to the new Vera Edge?

EDIT: Is it possible to use RFXtrx433 with the new Vera Edge at all?!

There are explanations on the forum how to upgrade to VeraEdge. Mainly  you have do do a UI7 backup and then restore it in the Edge.

Someone said that the RFXtrx is not usable with the Edge due to a USB problem. You will have to wait for a firmware fix.

Offline mixedup

  • Jr. Member
  • **
  • Posts: 95
  • Karma: +0/-0
WT0122
« Reply #50 on: December 14, 2014, 06:48:56 am »
Trying to get a swimming pool thermometer WT0122 working.  What would be the Category to select in RFXDeviceController/NewDevice/Category?  I can't actually see anything that would resemble this? 

Plugin version:   beta 3
RFXtrx firmware:   232
My Vera firmware version:  1.6.641

Have put plugged RFXtrx433 into my VeraLite via a powered USB hub (also used for DataMine and CurrentCost).  Controllered seems to come up and be ok (after installing Beta 3 files).  So it's just from this point on.

Here are logs (grep'ed on rfx).  Seems to have picked up a power device I see, which I'm guessing is my CurrentCost system I happen to use (it has it's own plugin) and separate USB connection.
Code: [Select]
root@MiOS_35202858:~# tail -f /tmp/log/cmh/LuaUPnP.log | grep -i rfx
02 12/14/14 22:06:03.094 luup_log:28: RFXtrx: warning: Bad starting message; ignore byte 89 <0x2ec0a680>
02 12/14/14 22:06:09.333 Device_Service::MatchupUpnpServices no upnp service for upnp-rfxcom-com:serviceId:rfxtrx1 <0x2b11a000>
02 12/14/14 22:06:09.333 Device_Service::MatchupUpnpServices no upnp service for urn:rfxcom-com:serviceId:rfxtrx1 <0x2b11a000>
09 12/14/14 22:06:14.963 JobHandler_LuaUPnP::Run device 29 RFX Power ELEC2/26322 room 0 type urn:schemas-micasaverde-com:device:PowerMeter:1 id PM/ELEC2/26322 parent 28/0xbbfa10 upnp: 0 <0x2b11a000>
09 12/14/14 22:06:14.964 JobHandler_LuaUPnP::Run device 28 RFXtrx controller device room 0 type urn:schemas-rfxcom-com:device:rfxtrx:1 id  parent 0/0xbb6120 upnp: 0 <0x2b11a000>
50 12/14/14 22:06:23.896 luup_log:28: RFXtrx: loading library L_RFXtrx ... <0x2ba4d680>
50 12/14/14 22:06:24.144 luup_log:28: RFXtrx: library L_RFXtrx loaded __LEAK__ this:413696 start:1363968 to 0x104d000 <0x2ba4d680>
50 12/14/14 22:06:24.145 luup_log:28: RFXtrx: Starting RFXtrx device: 28 <0x2ba4d680>
50 12/14/14 22:06:24.146 luup_log:28: RFXtrx: Serial port is connected <0x2ba4d680>
50 12/14/14 22:06:24.146 luup_log:28: RFXtrx: Baud is 38400 <0x2ba4d680>
50 12/14/14 22:06:24.147 luup_log:28: RFXtrx: RFXtrx is ready <0x2ba4d680>
50 12/14/14 22:06:25.103 luup_log:28: RFXtrx: Tree with number child devices: 1 <0x2ca4d680>
50 12/14/14 22:06:25.103 luup_log:28: RFXtrx:        door sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.104 luup_log:28: RFXtrx:      motion sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.104 luup_log:28: RFXtrx:       light sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.104 luup_log:28: RFXtrx:      light switches: 0 <0x2ca4d680>
50 12/14/14 22:06:25.105 luup_log:28: RFXtrx:  dim light switches: 0 <0x2ca4d680>
50 12/14/14 22:06:25.105 luup_log:28: RFXtrx:     window covering: 0 <0x2ca4d680>
50 12/14/14 22:06:25.105 luup_log:28: RFXtrx: temperature sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.106 luup_log:28: RFXtrx:    humidity sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.106 luup_log:28: RFXtrx:  barometric sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.107 luup_log:28: RFXtrx:        wind sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.107 luup_log:28: RFXtrx:        rain sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.107 luup_log:28: RFXtrx:          UV sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.108 luup_log:28: RFXtrx:      weight sensors: 0 <0x2ca4d680>
50 12/14/14 22:06:25.108 luup_log:28: RFXtrx:       power sensors: 1 <0x2ca4d680>
50 12/14/14 22:06:25.108 luup_log:28: RFXtrx:    security remotes: 0 <0x2ca4d680>
50 12/14/14 22:06:25.109 luup_log:28: RFXtrx:     remote controls: 0 <0x2ca4d680>
50 12/14/14 22:06:25.109 luup_log:28: RFXtrx:     heating devices: 0 <0x2ca4d680>
50 12/14/14 22:06:25.109 luup_log:28: RFXtrx:           RFXMeters: 0 <0x2ca4d680>
06 12/14/14 22:06:27.132 Device_Variable::m_szValue_set device: 28 service: urn:rfxcom-com:serviceId:rfxtrx1 variable: LastReceivedMsg was: 11 5A 01 16 66 D2 00 00 00 00 00 00 00 6E 88 52 4C 89  now: 0D 01 00 01 02 53 E8 00 0C 27 01 03 00 00  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e498680>
50 12/14/14 22:06:27.133 luup_log:28: RFXtrx: RFXtrx433 at 433.92 MHz <0x2e498680>
50 12/14/14 22:06:27.134 luup_log:28: RFXtrx: Firmware v232 <0x2e498680>
50 12/14/14 22:06:27.134 luup_log:28: RFXtrx: RFXtrx setup to receive protocols: <0x2e498680>
50 12/14/14 22:06:27.136 luup_log:28: RFXtrx:    - La Crosse <0x2e498680>
50 12/14/14 22:06:27.137 luup_log:28: RFXtrx:    - Hideki / UPM <0x2e498680>
50 12/14/14 22:06:27.138 luup_log:28: RFXtrx:    - Oregon Scientific <0x2e498680>
50 12/14/14 22:06:27.138 luup_log:28: RFXtrx:    - AC <0x2e498680>
50 12/14/14 22:06:27.139 luup_log:28: RFXtrx:    - ARC <0x2e498680>
50 12/14/14 22:06:27.139 luup_log:28: RFXtrx:    - X10 <0x2e498680>



« Last Edit: December 14, 2014, 07:12:56 am by mixedup »

Offline lolodomo

  • Moderator
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: RFXtrx plugin version beta 3 released
« Reply #51 on: December 14, 2014, 07:37:12 am »
The device creation is only automatic for this kind of device (when a message is received). So you have to keep automatic creation ... at least until the device is created.
As explained in RFXtrx433 user manual, you have to enable "FineOffset" receiving protocol for this device.
« Last Edit: December 14, 2014, 07:38:58 am by lolodomo »

Offline mixedup

  • Jr. Member
  • **
  • Posts: 95
  • Karma: +0/-0
Re: RFXtrx plugin version beta 3 released
« Reply #52 on: December 15, 2014, 04:01:11 am »
The device creation is only automatic for this kind of device (when a message is received). So you have to keep automatic creation ... at least until the device is created.
As explained in RFXtrx433 user manual, you have to enable "FineOffset" receiving protocol for this device.

tks lolodomo - I've setup "fineOffset" (and turned off other protocols), however I'm not getting auto-creation.  Looking at the RFXtrx433E however I am noting that the YELLOW LED on it is NOT flashing when the WT0122 flashes, so I'm assuming this is highlighting the fact the RFXtrx433E is not detecting the temperature update?  The WT0122 (433.9MHz) is working in that the remote that comes with it is measuring the temperature correctly. 

Any tips?  I'm on a Mac, however should I get a Windows OS running under VMWare and try to run up the "RFXmngr test program" to see if I can prove to myself the RFXtrx433E will pick up the signal?   




Offline lolodomo

  • Moderator
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: RFXtrx plugin version beta 3 released
« Reply #53 on: December 15, 2014, 02:09:01 pm »
Take care that it is not a problem of distance between your sensor and the RFXtrx.

Yes please check with RFXmngr if you can.

Offline mixedup

  • Jr. Member
  • **
  • Posts: 95
  • Karma: +0/-0
Re: RFXtrx plugin version beta 3 released
« Reply #54 on: December 15, 2014, 04:06:17 pm »
Hi lolodomo - I have them sitting right next to each other so should be ok.  I've got RFXmngr working, and I can see the ClearCost inputs coming in, but no WT0122 unfortunately... 

Any other ideas?  Time for a support ticket to http://rfxcom.com/ to ask for some help perhaps?

Code: [Select]
[font=courier]
16/12/2014 7:01:06 AM= 115A010466D2000000000000006E88524C89
Packettype    = ENERGY
subtype       = ELEC2 - OWL CM119, CM160
Sequence nbr  = 4
ID            = 26322
Count         = 0
Instant usage = 0 Watt
total usage   = 8291057.8 Wh
Signal level  = 8
Battery       = OK
================================================
Get Status:0D 00 00 12 02 00 00 00 00 00 00 00 00 00
------------------------------------------------
16/12/2014 7:01:17 AM= 0D0100120253E8040C2501030000
Packettype        = Interface Message
subtype           = Interface Response
Sequence nbr      = 18
response on cmnd  = Get Status
Transceiver type  = 433.92MHz
Firmware version  = 232
Hardware version  = 1.3
Undec             off
X10               enabled
ARC               disabled
AC                enabled
HomeEasy EU       disabled
Meiantech         disabled
Oregon Scientific enabled
ATI               disabled
Visonic           disabled
Mertik            disabled
AD                disabled
Hideki            enabled
La Crosse         enabled
FS20              disabled
ProGuard          disabled
BlindsT0          disabled
BlindsT1          disabled
AE                disabled
RUBiCSON          disabled
FineOffset        enabled
Lighting4         disabled
RSL               disabled
Byron SX          disabled
RFU               disabled[/font]

Offline agame

  • Sr. Newbie
  • *
  • Posts: 24
  • Karma: +0/-0
Re: RFXtrx plugin version beta 3 released
« Reply #55 on: December 16, 2014, 10:56:31 pm »
I am thrilled that the plugin works well supporting both receiving and sending [for the first time] messages to the A-OK blind controllers. UI15 hopefully upgrading soon.

There is one problem: I have three blinds and use 4 channels (1,2,3 for each respective blind; and 4 to control all simultaneously).

the plugin appears to recognise any channel interchangeably (only one device is created, but the state changes regardless of which channel is selected on the multi channel remote). However commands sent only work on the blind registered to channel 1.


update: a second instance of the controller has appeared. both work but both control blind 1.

Is there a way to configure multiple devices operating on different channels? Or is this a limitation at the RFXTRX end?

cheers.
« Last Edit: December 17, 2014, 01:10:03 am by agame »

Offline lolodomo

  • Moderator
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: RFXtrx plugin version beta 3 released
« Reply #56 on: December 17, 2014, 01:50:48 am »
I see nothing in the SDK relative to channels for A-OK.

Offline agame

  • Sr. Newbie
  • *
  • Posts: 24
  • Karma: +0/-0
Re: RFXtrx plugin version beta 3 released
« Reply #57 on: December 17, 2014, 07:02:54 am »
thx for following up. evidently didn't anticipate multi channel remotes.

Offline Yevgen

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
Re: RFXtrx plugin version beta 3 released
« Reply #58 on: December 24, 2014, 05:17:51 am »
Hi,

I own Livolo 1gang switches (no dimmer), Rfxtrx433E (beta3, f/w 233) and Vera3 (UI7). Switches able to run 'All Off' command (to be switched off for sure). In Rfxmngr this command available, but can't find it in RFXtrx devices settings on Vera. Can plugin run All Off?
« Last Edit: December 24, 2014, 05:22:36 am by Yevgen »

Offline lolodomo

  • Moderator
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: RFXtrx plugin version beta 3 released
« Reply #59 on: December 24, 2014, 08:12:39 am »
Hi,

I own Livolo 1gang switches (no dimmer), Rfxtrx433E (beta3, f/w 233) and Vera3 (UI7). Switches able to run 'All Off' command (to be switched off for sure). In Rfxmngr this command available, but can't find it in RFXtrx devices settings on Vera. Can plugin run All Off?

If I correctly remember, the OFF button should trigger an all Off action while the ON button should trigger a toggle ON/OFF.