The Vera Community forums have moved!

Advanced => Plugins & Plugin Development => Programming => USB RFXtrx Transceiver Plugin => Topic started by: lolodomo on February 20, 2012, 04:07:19 pm

Title: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on February 20, 2012, 04:07:19 pm
A new USB RFXCOM is available.
http://www.rfxcom.com/transceivers.htm#12103
USB 433.92MHz receiver + transmitter at lower price than before.

To download the plugin files, use the Zip archive link at the bottom of this page (http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha8#).
Installation & Setup (http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#InstallationSetup)
Compatible products and limitations (http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#Compatibleproductsandlimitations)

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

What's new in version alpha 7:
- Support for Blyss added
- Support for OWL CM180 added
- Manual creation of Hasta (old models) added
- Support for A-OK motors added
- Support for weighting scale (BWR101/102, GR101) added (Ap15e contrib)
- Support for Mertik-Maxitrol thermostats added (nirb contrib)
- New callback SendMessage added
- Last received message logged + stored in the variable "LastReceivedMsg" + displayed at the bottom of the Settings tab
- New variable "AdjustMultipler" added to let the user apply a multiplier coefficient on weather data
- Variable "Assocation" renamed "Association"
- Error messages shown to the user in the status zone of the dashboard (blue zone at the top middle of the screen)

What's new in version alpha 6:
- Plugin is up to date with RFXtrx firmware v49
- Child devices management revisited (fixed and enhanced)
- Support for X10 security remotes added
- Support for Meiantech/Atlantic security remotes added
- Support for KD101 smoke detector added
- Support for RUBiCSON temperature sensor added
- Support for Viking 02035, 02038 humidity sensors added
- Support for TFA 30.3133 temperature sensor added
- Support for Hasta blinds added
- Support for Philips SBC lighting added
- New devices created to match remote controls and give ability to trigger Vera scene from remote buttons, plus new buttons to send specific commands like group off, dim, bright, mood, ... etc
- LightwaveRF panel suppressed from the main plugin device; replaced by a new dedicated device
- Support for ATI and Medion remotes added
- Setup of received protocols updated
- "Logs" and "Notifications" panels added to barometer, rain, wind and UV devices
- Ability to adjust reported values for temperature, humidity, UV and barometric sensors using the variable "AdjustConst"
- Ability to repeat ON and OFF events for BinaryLight devices setting the variable "RepeatEvent" to 1
- Callback added to simulate receiving of message (for testing purposes)
- Support added for USB RFXtrx connected to a remote machine providing an IP access to a local serial port (using VSPE on Windows for example)

What's new in version alpha 5:
- plugin is up to date with RFXtrx firmware v45
- add support for Ikea Koppla
- add support for La Crosse WS2300 (temperature, humidity, rain and wind sensors)
- add support for chime command (ARC protocol)
- add support for Visonic PowerCode door/window sensors and motion sensors
- add partial support for X10 security remotes (light management)

What's new in version alpha 4:
- plugin is up to date with RFXtrx firmware v42
- RollerTrol supported (including a new setting to enable or disable receiving + a new button to create manually the Vera device)
- UV sensors supported
- Viking 02811 temperature sensor supported
- Chris's code relative to X10 security added ("tripped" status is now updated for X10 door sensors and X10 motion sensors)
- fix for DisplayStatus definition in json files for better compatibility with Automator app

What's new in version alpha 3:
- plugin is up to date with RFXtrx firmware v41
- new devices supported: Honeywell TS15C (temperature sensor), UPM WT450H (temperature and humidity sensor), UPM RG700 (rain sensor), UPM WDS500 (wind sensor), OWL CM119/CM160 (energy usage sensor), RisingSun (switch power)
- barometer, rain and wind devices include now UI5 events and so can be used as triggers in a scene
- X10 security is partially supported (door and motion sensors are created but status is not updated; arm/disarm is not yet implemented)

What's new in version alpha 2:
- you can now create manually switch device, dimmable light device and window covering device using a new tab
- Harrison curtain is now managed (device creation + Open/Stop/Close commands)
- For LightwaveRF, a new tab includes 5 mood buttons (the command must have been received first one time; then it can be send by the Vera/RFXtrx)
- conversion of device between binary light device, dimmalbe light device and window covering device  is done automatically by the plugin depending on the received messages, or can be done manually by the user using the new tab (buttons "add xxx")
- you can now associate several devices using the "Association" variable. This is interesting when you have several controllers for one receiving device. One device for each controller will be automatically created by the plugin but then you can keep only one device and put the "id" of each others in the "Assocation" variable of the remaining device. The different "id" must be separated by comma. The "id" must be the altid minus the 3 first characters (suppress the "LS/" or "DL/" or "WC/"). Then, commands coming from different controllers will impact one unique device.


Here are the scene numbers to be used in a scene trigger:
-- ON (activated) / OFF (deactivated): 1-16
-- SET LEVEL: 17-32
-- LOCK (activated) / UNLOCK (deactivated): 33-48
-- OPEN: 49-64
-- CLOSE: 65-80
-- STOP: 81-96
-- GROUP ON (activated) / GRUP OFF (deactivated): 100
-- GROUP SET LEVEL: 101
-- DIM: 102
-- BRIGHT: 103
-- ALL LOCK: 105
-- MOOD1: 111
-- MOOD2: 112
-- MOOD3: 113
-- MOOD4: 114
-- MOOD5: 115
-- PANIC (activated) / END PANIC (deactivated): 120
-- ARM AWAY: 121
-- ARM HOME: 122
-- DISARM: 123
-- PAIR (KD101): 124
-- CHIME (ARC protocol only): 131-146
When a range of values is mentionned, it means the number depends on the unit code of the device (from 1 to 16).


My updated TODO list is now:
1 - create a description/help page
2 - release a first version to have the plugin available in the app store
Title: Re: New USB RFXCOM
Post by: Quinten on February 20, 2012, 05:32:52 pm
I'm very interested to find out the answers to this...  I've been uhm-ing and ah-ing over an RFXcom for ages, and this new stick may have just won me over...
Title: Re: New USB RFXCOM
Post by: lolodomo on February 20, 2012, 07:10:55 pm
Here is what evanes said in the RFXCOM topic:

Quote
the plugin is made for socket (LAN) communication. I have no experience with usb serial communication but the code should be easily adapted for this type of communication.  I think usb however limits your possibilities and I therefore advise you to buy the networked devices.

I take a quick look to the code + the code of other plugins using serial port, and yes this is probably very simple to adapt.
But with USB RFXCOM, I imagine that we have only one communication channel to receive data and to send orders (instead of 2 in the case of the RFXLAN). I don't know how are managed acknowledgments of orders. Are they "mixed" with normal data receiving ?
Title: Re: New USB RFXCOM
Post by: lolodomo on February 21, 2012, 08:32:21 am
Bert (RFXCOM) told me he already delivered a USB RFXtrx433 to someone who will try to make a plugin for the Vera.
By curiosity, is it someone here present on the forum ?
Title: Re: New USB RFXCOM
Post by: Quinten on February 21, 2012, 12:07:11 pm
It's not me, but I do may have one incoming to help out.... ;)
Title: Re: New USB RFXCOM
Post by: lolodomo on February 22, 2012, 07:19:24 am
I got confirmation from Bert (RFXCOM) that the new RFXtrx use a new protocol, different from the one used by RFXLAN in particular. This new protocol will be used in the future by new RFXCOM products.
That being said, that means we have to develop a new totally RFXCOM plugin that will handle the new RS232 protocol. I think I should be able to initialize this new plugin, even if I have until now no experience with lua/Vera development.
First I have to buy the new RFXCOM products + few Oregon sensors.
Title: Re: New USB RFXCOM
Post by: redeyedrob on February 22, 2012, 01:41:54 pm
I suspect I'm the chap Bert was referring to regarding the Vera plugin, I was in touch with RFXCOM with a few tech queries and ended up being lucky enough to get hold of the new transceiver last week.

You're right in that it uses a new protocol (in my opinion simpler), however it's very well documented.  I've been pretty much hobbled with work and am ashamed to say I've barely had a chance to try out the transceiver, never mind start coding a plugin.

While I was waiting to receive the new RFXCOM stick, I did have a look at the existing plugin code.  I'm not hugely familiar with Lua/Luup but from an initial look it will need a reasonable rewrite - the LAN unit it's written for used 2 different IP addresses for send and receive messages, it's also operating at a slightly lower level than will be required with the USB stick.

My current plan is to have the RFXCOM installed on a PC somewhere with a small server side listen app running on the PC to check for signals from the Vera.  The plugin will then take the IP address of the server PC and communicate with the server side app which will in turn communicate with the RFXCOM box as appropriate.

This of course is a stupid arrangement because the Vera has 2 USB ports - obviously it would be far better to have the RFXCOM plugged straight in.  My problem with this is my unfamailarity with Lua/Luup, I think I've got a reasonable understanding i.e. I can see the code to steal from other plugins ;) of sending and receiving messages and am therefore confident I can get this working, however I've not looked at talking direct to the USB ports on the Vera - maybe it's easy, maybe it needs firmware support?  I'm also partly keen on taking the server side app route initially as I've got a Tellstick / Dovado combo at the moment and it's got a nice simple UDP API - if I develop this way then I can easily fork the plugin and have support for both.

If I'm realistic it will be the weekend at the earliest before I can lock myself away and start coding.

I'll post anything usable as I develop it, if anyone writes anything in the meantime I'm happy to assist with testing / debug etc.
Title: Re: New USB RFXCOM
Post by: lolodomo on February 22, 2012, 03:16:58 pm
Mine has been purchased few minutes ago. I will receive it only in few days (one week or 2).

Could you please at least check that serial/USB is recognized by the Vera when you connect the RFXtrx to the Vera ?
 (open a SSH session and check the result of dmesg command)

Regarding the plugin, it seems to be easier to handle RS232 through USB than through IP. There is no setting to add to the plugin, no connection to open (this is done automatically).

I will work on the plugin too. We can share our work if you wish. Even without any experience on lua, I think it is relatively easy to create the skeleton of the new plugin, taking examples from existing RS232 plugins.
On my side, I will implement in priority the decoding of temperature and humidity sensors (I will have only Oregon sensors).
On your side, what are the devices you manage with RFXCOM ?

Implementing all the protocol defined by RFXCOM is not something little but this can be done step by step.
Title: Re: New USB RFXCOM
Post by: redeyedrob on February 22, 2012, 03:54:02 pm
No probs to check if the Vera is recognising the RFXtrx, might not be tonight though, still at work - maybe I'd get home sooner if I stopped checking forums ;)

I'm happy enough to go down the RS232 route, I only bought the Vera once I'd bought the RFXtrx so wasn't sure how easy that would be, more comfortable with IP myself.

I've exclusively got HomeEasy(UK) kit, but that's going no where in terms of development.  Currently controlling it via Tellstick but I was looking into both LightwaveRF (nice and cheap) and ZWave, got in touch with RFXCOM to confirm they supported all the HEUK kit and they told me about the RFXtrx which supports both HEUK and LWRF.  Was not actually planning on buying anything but when I figured I could get the Vera and the RFXtrx and therefore control all my current gear and be able to control LWRF and ZWave kit from the same interface I emptied out my piggy bank..

Happy to work together on plugin, my main problem at the moment is finding free time to do it.
Title: Re: New USB RFXCOM
Post by: lolodomo on February 24, 2012, 05:09:46 pm
No probs to check if the Vera is recognising the RFXtrx, might not be tonight though, still at work - maybe I'd get home sooner if I stopped checking forums ;)

Did you try finally ?

PS: apparently, I will receive my RFXtrx sooner than expected, probably Monday or Tuesday. 8)
Title: Re: New USB RFXCOM
Post by: redeyedrob on February 25, 2012, 07:33:39 am
Eventually!  ;)

Looks like it's recognised :

Quote
hub.c: new USB device 00:03.0-1.2, assigned address 3
usbserial.c: FTDI FT232BM Compatible converter detected
usbserial.c: FTDI FT232BM Compatible converter now attached to ttyUSB0 (or usb/tts/0 for devfs)

Good news about getting yours earlier - mine took about 5 working day (to UK)

Next step - talking to it..
Title: Re: New USB RFXCOM
Post by: lolodomo on February 25, 2012, 08:38:04 am
Eventually!  ;)

Looks like it's recognised :

Quote
hub.c: new USB device 00:03.0-1.2, assigned address 3
usbserial.c: FTDI FT232BM Compatible converter detected
usbserial.c: FTDI FT232BM Compatible converter now attached to ttyUSB0 (or usb/tts/0 for devfs)

 8)

Quote
Next step - talking to it..

The easiest way might be to start from the code of the existing RFXCOM plugin.
Unfortunately, this is not very clear if the current RFXCOM plugin is working or not with UI5, and I would like to start from a clean and working basis.
Title: Re: New USB RFXCOM
Post by: bfromdruten on February 25, 2012, 06:06:42 pm
The rfxcom plugin doesn not work correctly uder UI5.
Title: Re: New USB RFXCOM
Post by: redeyedrob on February 27, 2012, 05:31:39 am
Managed to find a little time to play last night.  Being a "first princliples" sort of guy I thought I'd start off with some command line serial port comms, move onto Lua and then eventually graduate to Luup.

Unfortunately I didn't really achieve anything apart from confirming my inexperience with OpenWrt, however on the offchance it saves someone else 2 minutes, here's what I learned :


Having failed at the bottom up approach I thought I'd try top down and find an RS232 Plugin and hack that at bit, however it was getting late and not seeing anything blindingly obvious I called it a night.



Title: Re: New USB RFXCOM
Post by: utz on February 27, 2012, 09:06:27 am
I looked at the datasheets of the rfxcom and the existing plugin over the last days (I was thinking of using it but ended up starting building my own transmitters/receivers for a different frequency band ...). I would say that the existing plugin is too different to mod it to fit the usb variant. I would start new, maybe using some elements. If made generic it would give a lot of great options (for example the lightwaverf stuff)
Title: Re: New USB RFXCOM
Post by: lolodomo on February 27, 2012, 06:42:24 pm
I received today my RFXtrx. Not yet connected to the Vera. I just used the RFXCOM test application on my PC and unfortunately only 1 of my 3 new Oregon THGR122NX sensors is detected by the RFXtrx :-[ I don't understand what could be wrong...

Edit: the RFXtrx firmware dated the 7th of March correct my problem 8) My 3 THGR122NX are now detected.
Title: Re: New USB RFXCOM
Post by: redeyedrob on February 28, 2012, 03:51:14 am
RFXCOM guys are pretty quick on tech support - hopefully they can look into it.  There's a msgcode for "undecoded packet" in the SDK, maybe you could catch them and forward.

Tellsticks now support Oregon and they've got big compatibility issues too.

Also - it's worth trying limiting the packets it's receiving i.e. limit the different kinds of hardware it's scanning for, however I'd suspect this would be a reliability issue rather than a recognition one.
Title: Re: New USB RFXCOM
Post by: lolodomo on February 28, 2012, 08:00:06 am
RFXCOM guys are pretty quick on tech support - hopefully they can look into it.  There's a msgcode for "undecoded packet" in the SDK, maybe you could catch them and forward.

Tellsticks now support Oregon and they've got big compatibility issues too.

Also - it's worth trying limiting the packets it's receiving i.e. limit the different kinds of hardware it's scanning for, however I'd suspect this would be a reliability issue rather than a recognition one.

I tried to check "undecoded packet" but I got no additional information.
I have already setup the RFXtrx to receive obly Oregon and La Crosse.
I hope that a new RFXCOM firmware could solve the issue.

I hope these 2 new sensors are working well, I have nothing to test them exceopt the RFXtrx.
Title: Re: New USB RFXCOM
Post by: lolodomo on February 28, 2012, 03:14:03 pm
Eventually!  ;)

Looks like it's recognised :

Quote
hub.c: new USB device 00:03.0-1.2, assigned address 3
usbserial.c: FTDI FT232BM Compatible converter detected
usbserial.c: FTDI FT232BM Compatible converter now attached to ttyUSB0 (or usb/tts/0 for devfs)

What is the version of your Vera ?

Here is what I get:

Code: [Select]
+usb 2-1: new full speed USB device using rt3883-ohci and address 2
+ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
+usb 2-1: Detected FT232RL
+usb 2-1: Number of endpoints 2
+usb 2-1: Endpoint 1 MaxPacketSize 64
+usb 2-1: Endpoint 2 MaxPacketSize 64
+usb 2-1: Setting MaxPacketSize 64
+usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

And it is recognized even behind my new little Amazon USB hub:

Code: [Select]
+usb 1-1: new high speed USB device using rt3883-ehci and address 2
+hub 1-1:1.0: USB hub found
+hub 1-1:1.0: 4 ports detected
+usb 1-1.2: new full speed USB device using rt3883-ehci and address 3
+ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
+usb 1-1.2: Detected FT232RL
+usb 1-1.2: Number of endpoints 2
+usb 1-1.2: Endpoint 1 MaxPacketSize 64
+usb 1-1.2: Endpoint 2 MaxPacketSize 64
+usb 1-1.2: Setting MaxPacketSize 64
+usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
Title: Re: New USB RFXCOM
Post by: lolodomo on February 28, 2012, 07:14:23 pm
Ok, after reading few parts of the wiki and go through few existing plugins (RFXCOM, Onkyo, Denon, Panasonic, Pioneer, ...), I think I have now the minimum basics to understand how it works and what is the role of each file.

I would say that the existing plugin is too different to mod it to fit the usb variant. I would start new, maybe using some elements. If made generic it would give a lot of great options (for example the lightwaverf stuff)

What is exactly your idea when you think of making it generic ?
We have to define child devices, but it seems it is already what is done by the current RFXCOM plugin. Do you imagine a different architecture to make it even more generic than that ?
Title: Re: New USB RFXCOM
Post by: lolodomo on February 29, 2012, 08:53:31 am
Here is how I see the plugin to be as generic as possible. This is not very structured !
There will be a main device with files D_RFXtrx.xml D_RFXtrx.json I_RFXtrx and S_RFXtrx files. We could implement in particular the reset function on this device.
Then there will be one child device for each kind of message managed by the RFXtrx. For example, for the TEMP2 message, we will define a TEMP2 device with files D_RFXtrx_TEMP2.xml and S_RFXtrx_TEMP2.xml files. An additional json file will be required for other kind of message. This device will of course implement the generic temperature service too.  The RFXtrx_TEMP2.xml will define all the variables included in the TEMP2 message. Decoding a TEMP2 message will then consist in identifying the correct TEMP2 device from ID (create automatically the device if inexistent) and set all the TEMP2 variables, finally the temperature will be set from one (or severa) of these variables. There will be a decode function that set the variables + a encode function that build the message from variables (to send commands, for example to switch light ON or OFF). A function will get the ID from the message too. The device altid format could be RFXtrx_<kind of message>_<ID>, for example RFXtrx_TEMP2_47603 where 47603 is the ID included in the message. For sending command, the service will define a "high-level" action. The action will consist in setting variables on the child device and then call the encode and send functions.

Is it clear and what do you think about that ?
Title: Re: New USB RFXCOM
Post by: Quinten on February 29, 2012, 10:14:10 am
My USB RFxcom is shipping tonight, so expect some input from me soon ;)
Title: Re: New USB RFXCOM
Post by: lolodomo on February 29, 2012, 10:46:14 am
My USB RFxcom is shipping tonight, so expect some input from me soon ;)

As a user or as a developer for the plugin ?
Title: Re: New USB RFXCOM
Post by: Quinten on February 29, 2012, 11:05:49 am
Both  :)
Title: Re: New USB RFXCOM
Post by: lolodomo on February 29, 2012, 06:57:21 pm
Both  :)

Finally, that makes a lot of people for one plugin :)

Quniten, what kind of devices do you manage with the RFXtrx ?
Do you have already an experience with Vera plugin development (that is not my case) ?

redeyedrob, any news on your side ?

Now I hesitate to start, that would be waste of time if everybody spend time to do the same thing.
Title: Re: New USB RFXCOM
Post by: Quinten on March 01, 2012, 04:41:56 am
I will be using the RFXcom mainly to see the events my Visonic alarm generates, and hopefully the messages from my Bye Bye Standby switches.  Cherry on top would be some control of Bye Bye Standby modules, but that's not essential since I am replacing those with Zwave at the moment.

I've developed (well, copied and modified an existing plugin) a plugin to update my MySQL database with events from the VeraLite.  No where near ready for release, and I am still picking up on plugin development as I go along.  I am a software developer by trade though (C), so once I get the hang of Lua and UPNP, I should have no problem churning something useful out.
Title: Re: New USB RFXCOM
Post by: redeyedrob on March 01, 2012, 05:14:12 am
I have had a little more time, and have been wasting it pursuing my bottom up approach...

Having satisfied myself I couldn't tlak to the RFXtrx via straight ssh commands, I moved onto Lua.

Good news is I've satisfied myself I can't talk to it in Lua either ;)  Serial port comms in reference Lua are handled as files, no problem setting up the RFXtrx as a file and opening it for read and write, however once the reset and status commands were sent and I tried to read the response it just hangs.  I suspect serial settings are the issue again.

Plenty of third party serial comms libraries, some of them fairly popular but I didn't want to start messing with things that aren't on the box by default.

This leaves me up at the level I should have started at - Luup ;)

I started looking through some other plugins, not really got my head around the structure yet - I could say your approach makes sense lolodomo but frankly that wouldn't be much of an endorsement at this stage.  I'm away tonight, however next time I get a chance I'm going to try and write myself a hard coded on / off button for some switches I can see from my PC.  Once I've actually made the thing signal something from the Vera I'll be considerably less frustrated.  Certainly don't hold back on doing anything on my account, if I do anything I'll post it here.

I'm running a Vera 2 - will check firmware later, however the Micasa guys reinstalled it remotely themselves because my ZWave dongle wasn't working.  I'm on UI4.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 01, 2012, 12:19:55 pm
Thinking about it, my feeling is that we could (should) have shared files between the RFXLAN and RFXtrx plugins, at least for the files required to describe the specific devices.
But the merge could be done in a second time... First, let's try to communicate with the RFXtrx.
Title: Re: New USB RFXCOM
Post by: Quinten on March 01, 2012, 06:12:42 pm
I've just plugged my RFXtrx in a (powered) USB hub, but although I have the device created, I am not seeing any of those messages that you both see?

root@MiOS:~# dmesg
root@MiOS:~# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
root@MiOS:~# ls -la /dev/ttyS*
crw-rw-rw-    1 root     root        4,  64 Mar  1 23:11 /dev/ttyS0
crw-rw-rw-    1 root     root        4,  65 Jan  1  1970 /dev/ttyS1
root@MiOS:~# ls -la /dev/usb*
crw-r--r--    1 root     root      189,   0 Jan  1  1970 /dev/usb1
crw-r--r--    1 root     root      189, 128 Jan  1  1970 /dev/usb2
root@MiOS:~#


What gives?  I'm running on a VeraLite with UI5 btw.
Title: Re: New USB RFXCOM
Post by: Quinten on March 01, 2012, 06:30:54 pm
Doh!  Forgot to plug my USB hub back into the VeraLite when I disconnected it to pair it with a new module...


root@MiOS:/tmp/log/cmh# dmesg
usb 1-1: new high speed USB device using rt3883-ehci and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high speed USB device using rt3883-ehci and address 3
hub 1-1.1:1.0: USB hub found
hub 1-1.1:1.0: 4 ports detected
usb 1-1.4: new full speed USB device using rt3883-ehci and address 4
ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
usb 1-1.4: Detected FT232RL
usb 1-1.4: Number of endpoints 2
usb 1-1.4: Endpoint 1 MaxPacketSize 64
usb 1-1.4: Endpoint 2 MaxPacketSize 64
usb 1-1.4: Setting MaxPacketSize 64
usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0
root@MiOS:/tmp/log/cmh# ls -ltr /dev/tty*
crw-rw-rw-    1 root     root        5,   0 Jan  1  1970 /dev/tty
crw-rw-rw-    1 root     root        4,  65 Jan  1  1970 /dev/ttyS1
crw-rw-rw-    1 root     root      188,   0 Mar  1 23:27 /dev/ttyUSB0
crw-rw-rw-    1 root     root        4,  64 Mar  1 23:29 /dev/ttyS0
root@MiOS:/tmp/log/cmh# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 002: ID 1a40:0101
Bus 001 Device 003: ID 1a40:0101
Bus 001 Device 004: ID 0403:6001
root@MiOS:/tmp/log/cmh#

Title: Re: New USB RFXCOM
Post by: lolodomo on March 01, 2012, 07:05:38 pm
I have prepared the minimum lua code to start first tests, meaning initialization of the communication with the RFXtrx + trace of received messages from the RFXtrx.
Remains the XML files to do.
I should be able to make the first tests tomorrow evening.
Title: Re: New USB RFXCOM
Post by: Quinten on March 02, 2012, 07:52:12 am
I have prepared the minimum lua code to start first tests, meaning initialization of the communication with the RFXtrx + trace of received messages from the RFXtrx.
Remains the XML files to do.
I should be able to make the first tests tomorrow evening.

You're already one step ahead of me...  Please keep us posted!
Title: Re: New USB RFXCOM
Post by: redeyedrob on March 02, 2012, 10:18:24 am
Good work.

If you are happy with the results then it would be good to post the files, I'll hopefully have some time over the weekend - if you're happy with your files I'll work with them, if not I'll start from scratch.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 02, 2012, 12:44:32 pm
The question I am asking myself is: shall I create directly children device using usual temperature and humidity devices, meaning without the ability to add variables to store additional information (last update for example) ?
Or shall I first create a new child device specific to the plugin used for temperature/humidity that will store some data and then create the usual temperature and/or humidity devices as children of this new device ? We would have a tree with 3 levels instead of 2.

I will probably start with the first approach (because easiest), it is how it is done in the current RFXCOM plugin.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 02, 2012, 06:05:23 pm
It's working 8) Sending and receiving commands.
Until now I only log messages and partially decode temp/hum messages.
Next step is finishing at least the decoding of temperature and humidity messages received and clean my code.
Then I will publish my files (certainly during the weekend).
Title: Re: New USB RFXCOM
Post by: lolodomo on March 03, 2012, 08:37:57 am
Finally, I took full of code from the original RFXCOM plugin to manage device children.
But it looks like there is a problem when creating several children with the same id. After syncing, some child are lost and mixed up.
Is it a know bug with UI5 (1.5.254) ?
Do we have to always use different ID (altid) ? In this case, I think the original RFXCOM can not work properly because temprature and humidity devices will have the same id for the same sensor.
Title: Re: New USB RFXCOM
Post by: ninux on March 03, 2012, 08:42:23 am
Hello Lolodomo,

I'm debuging RFXCOM Plugin and I have the same issue with altid who have the same for Temp and Humidity.
I think we need to rewrite the creation of device look at Mochad X10 plugin who have a good implementation.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 03, 2012, 06:35:18 pm
Here are my files. Of course, it is not finished and enhancements are possible, but it is now working with temperature and humidity sensors.

After uploading the 4 files (the lua file must not be compressed), you have to create a new device using the file D_RFXtrx.xml and setup the serial port for this new device. The serial port must be set to 38400 bauds (not yet verified by the plugin).
To enable the child creation (for creation of temperature and humidity devices), you have to set the variable AutoCreate to 1 in the device advanced settings.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: Quinten on March 06, 2012, 02:58:52 pm
I haven't forgetten about this...  I downloaded the files, looked at them in an editor, but then I got distracted again by other stuff, so I haven't actually given them a try.  Have you progressed with them at all?
Title: Re: New USB RFXCOM
Post by: lolodomo on March 07, 2012, 06:57:18 am
I haven't forgetten about this...  I downloaded the files, looked at them in an editor, but then I got distracted again by other stuff, so I haven't actually given them a try.  Have you progressed with them at all?

The only changes I made are relative to prefix. There were mismatches, sometimes I used "XX_" sometimes "XX/". But the plugin is working well even with these "errors".
Nevertheless I know my function findChild has to be corrected because it could fail in certain particular cases (depending on the ID of sensors).
I had no time to progress since the beginning of the week.

Here is my current TODO list:
1) correct the function findChild (full matching from position 4 to the end of the string)
2) check at startup the characteristics of the serial connection (bauds, parity, ...)
3) manage the result of "Get Status" command (and store in variables the protocols decoded by the RFXtrx))
4) manage barometer data (new device to display pressure)
5) manage the setup of the RFXtrx through the plugin (manage "Set Mode" command)
Title: Re: New USB RFXCOM
Post by: Quinten on March 07, 2012, 08:45:34 am
I actually spend a couple of hours this morning going through the plugin and comparing it to the RFXCOM plugin (so I could get a feel as to how much was changed) and it's looking pretty neat already.  I do not have any temperature sensors, so I can not actually put anything to test yet, but I will try to add some functions for dealing with ByeBye Standby/HomeEasy lighting messages in the same style as yours.  I think for now it is best you maintain the plugin and merge the code in?
Title: Re: New USB RFXCOM
Post by: lolodomo on March 07, 2012, 10:26:22 am
I do not have any temperature sensors, so I can not actually put anything to test yet, but I will try to add some functions for dealing with ByeBye Standby/HomeEasy lighting messages in the same style as yours.  I think for now it is best you maintain the plugin and merge the code in?

Ok
Title: Re: New USB RFXCOM
Post by: strangely on March 07, 2012, 10:42:22 am
Any Idea if either the original plugin or this one supports Oregon Scientific Wind Sensors?
Title: Re: New USB RFXCOM
Post by: ninux on March 07, 2012, 04:31:17 pm
If RFXtrx support your Oregon Wind Sensors we can add the support of this sensors like Rain gauge, we juste need your LuaUPnP.log.
I only know RFXCOM Lan supports the Oregon Wind Senrors.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 07, 2012, 04:40:44 pm
Here are the wind sensors that are (should be) managed by the RFXtrx:
WIND1 is WTGR800
WIND2 is WGR800
WIND3 is STR918, WGR918
WIND4 is TFA

But wind data are not yet managed by the Vera plugin.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 07, 2012, 04:43:42 pm
Please note that the RFXtrx firmware dated the 7th of March correct my problem 8) My 3 THGR122NX are now detected.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 07, 2012, 06:43:34 pm
New version to correct the function findChild.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: lolodomo on March 07, 2012, 06:48:32 pm
Can someone explain to me why this code leads to value nil for variable baud and path ?
Variable IOdevice is correctly retrieved => device 21

Code: [Select]
local IOdevice = luup.variable_get("urn:micasaverde-com:serviceId:HaDevice1", "IODevice", lul_device)
log("IOdevice: " .. IOdevice)
local baud = luup.variable_get("urn:micasaverde-org:serviceId:SerialPort1", "baud", IOdevice)
log("baud: " .. (baud or "nil"))
local path = luup.variable_get("urn:micasaverde-org:serviceId:SerialPort1", "path", IOdevice)
log("path: " .. (path or "nil"))

Is it because device 21 (of type urn:micasaverde-org:device:SerialPort:1) is tagged as invisible ?
Title: Re: New USB RFXCOM
Post by: strangely on March 07, 2012, 08:44:24 pm
Here are the wind sensors that are (should be) managed by the RFXtrx:
WIND1 is WTGR800
WIND2 is WGR800
WIND3 is STR918, WGR918
WIND4 is TFA

But wind data are not yet managed by the Vera plugin.
I'm holding off buying into one of these and a weather station, as I'd really like the wind sensor to be able to trigger pulling in an awning that's controlled by Zwave, if the wind gets too high!
 
At the moment I have a bit of a hack job with a HRDS1 and a pendulum switch mounted on the awning, and would like to be a bit more scientific about it if the wind gets too high for it to be out! :)
Title: Re: New USB RFXCOM
Post by: Quinten on March 08, 2012, 10:40:05 am
New version to correct the function findChild.

Hi lolodomo (is that your name?)

I've amended the lua slightly to add support (preliminary) for Lighting1 (0x10): X10 lighting, ARC, ELRO AB400D, etc which works perfectly for my ByeBye Standbye (part of ARC / address code wheels) modules.

Hope you are able to merge the code back in...

Q.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 10, 2012, 07:11:46 am
New version to correct the function findChild.

Hi lolodomo (is that your name?)

I've amended the lua slightly to add support (preliminary) for Lighting1 (0x10): X10 lighting, ARC, ELRO AB400D, etc which works perfectly for my ByeBye Standbye (part of ARC / address code wheels) modules.

Hope you are able to merge the code back in...

Q.

Very good.

To be clear, your code currently only updates the light status from the messages coming from the RFXtrx, but your code does not yet command power ON and power OFF from the Vera ?

The only thing I don't understand is how you manage the command values from the message 0x10. Is there not someting missing in function decodeLighting1 to decode cmd value and buid a value with the constants you defined ? For example, ON command is value 1 in the RFXtrx specification, not 4. I might miss something...
Title: Re: New USB RFXCOM
Post by: lolodomo on March 10, 2012, 07:20:43 am
And it could be interesting to change this line in your function decodeLighting1

Code: [Select]
local altid = "L" .. subType .. "/" .. id
by

Code: [Select]
local altid = "L1." .. subType .. "/" .. id
and use later L2.x L3.x L4.x L5.x and L6.x for the other lighting messages.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 10, 2012, 07:55:26 am
And for commands "All ON" and "All OFF", do you know if several messages are sent, one for each unit of the house ? Or only one message and in this case what is the value of unitcode ? Maybe it is necessary to change how to find the Vera light devices in this case.
Title: Re: New USB RFXCOM
Post by: GeeZay on March 10, 2012, 09:49:15 am
Hi there,

I'd like to join the RFXCOM USB community. It setup a new RFXCOM device with the files provides within this threads. However, I do not get it to work so far.

Here's the error message I get:

01      03/10/12 15:35:35.019   IOPort::Connect connect -1 127.0.0.1:3481 <0x4408>
01      03/10/12 15:35:39.015   LuaInterface::CallFunction_Startup-1 device 41 function startup failed [string "..."]:10: module 'L_RFXtrx' not found:
        no field package.preload['L_RFXtrx']
        no file './L_RFXtrx.lua'
        no file '/usr/share/lua/L_RFXtrx.lua'
        no file '/usr/share/lua/L_RFXtrx/init.lua'
        no file '/usr/lib/lua/L_RFXtrx.lua'
        no file '/usr/lib/lua/L_RFXtrx/init.lua'
        no file '/etc/cmh-ludl/L_RFXtrx.lua'
        no file '/etc/cmh-lu/L_RFXtrx.lua'
        no file './L_RFXtrx.so'
        no file '/usr/lib/lua/L_RFXtrx.so'
        no file '/usr/lib/lua/loadall.so' <0x402>
01      03/10/12 15:35:39.016   LuImplementation::StartLua running startup code for 41 I_RFXtrx.xml failed <0x402>
01      03/10/12 15:35:43.646   LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:16: attempt to index upvalue 'pluginLib' (a nil value) <0x4408>
01      03/10/12 15:35:43.662   LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:16: attempt to index upvalue 'pluginLib' (a nil value) <0x4408>
01      03/10/12 15:35:43.664   LuaInterface::CallFunction-2 lu_incoming failed [string "..."]:16: attempt to index upvalue 'pluginLib' (a nil value) <0x4408>


I already uploaded the L_RFXtrx.lua file via the developer tab. What's missing here? Where do I get the missings files?

Also I do not see any child devices though I have set AutoConfigure tot 1.

Any idea?

Thanks, GeeZay
Title: Re: New USB RFXCOM
Post by: lolodomo on March 10, 2012, 10:24:34 am
Code: [Select]
module 'L_RFXtrx' not foundIf you use the developper tab to upload the files, the L_RFXtrx.lua is uploaded and compressed. The file must not be compressed (with UI5 1.5.254). So just use WINSCP to upload the lua file. Then it should work.
What version of UI are you using ?
Title: Re: New USB RFXCOM
Post by: lolodomo on March 10, 2012, 10:32:16 am
By the way, as incoming seems to be called even when startup has failed, it would be better to check that the lua lib is not nil before calling a function from the lib. I will change that, that will avoid the 3 error lines in your traces.
Title: Re: New USB RFXCOM
Post by: GeeZay on March 10, 2012, 10:52:45 am
Code: [Select]
module 'L_RFXtrx' not foundIf you use the developper tab to upload the files, the L_RFXtrx.lua is uploaded and compressed. The file must not be compressed (with UI5 1.5.254). So just use WINSCP to upload the lua file. Then it should work.
What version of UI are you using ?

Great. Thanks for the hint. One step ahead. Now I'm getting tons of the following error message:

01      03/10/12 16:46:17.703   ^[[31;1mLuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_RFXtrx.lua:159:


What's going wrong.

BTW: I'm still on UI4.

Thanks GeeZay
Title: Re: New USB RFXCOM
Post by: lolodomo on March 10, 2012, 12:21:35 pm
I will check tomorrow what code is at line 159.

Did you setup the serial port ?
Did you choose 38400 bauds ?
Title: Re: New USB RFXCOM
Post by: Quinten on March 10, 2012, 05:12:33 pm
Quote
Very good.

To be clear, your code currently only updates the light status from the messages coming from the RFXtrx, but your code does not yet command power ON and power OFF from the Vera ?

That is correct.  It will be the next step though ;)

Quote
The only thing I don't understand is how you manage the command values from the message 0x10. Is there not someting missing in function decodeLighting1 to decode cmd value and buid a value with the constants you defined ? For example, ON command is value 1 in the RFXtrx specification, not 4. I might miss something...

I can only speak for the commands I receive on the RFXtrx for my BBSB modules, which have a command of either 0 (off) or 1 (on).  I really added the minimum so it would work for me.  Once I get the hang of it, I'll add more to it, but those will be done without the ability for me to test.
Title: Re: New USB RFXCOM
Post by: Quinten on March 10, 2012, 05:16:26 pm
And it could be interesting to change this line in your function decodeLighting1

Code: [Select]
local altid = "L" .. subType .. "/" .. id
by

Code: [Select]
local altid = "L1." .. subType .. "/" .. id
and use later L2.x L3.x L4.x L5.x and L6.x for the other lighting messages.

The devices are created as LS/L1/F04 (for instance)...  isn't that already correct?
Title: Re: New USB RFXCOM
Post by: Quinten on March 10, 2012, 05:18:43 pm
And for commands "All ON" and "All OFF", do you know if several messages are sent, one for each unit of the house ? Or only one message and in this case what is the value of unitcode ? Maybe it is necessary to change how to find the Vera light devices in this case.

No sorry, BBSB modules do not have ALL ON/ALL OFF, so I have no idea how it will be received by the RFXtrx.  We may have to find some other willing RFXtrx owners that are able to help us.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 11, 2012, 05:03:00 am
Quote from: Quinten

I can only speak for the commands I receive on the RFXtrx for my BBSB modules, which have a command of either 0 (off) or 1 (on).  I really added the minimum so it would work for me.  Once I get the hang of it, I'll add more to it, but those will be done without the ability for me to test.

The code from the RFXCOM plugin does not expect 0 or 1  but a constant with a different value.
I will prppose an update later and you will be able to check if it is ok or not.
Title: Re: New USB RFXCOM
Post by: Quinten on March 11, 2012, 05:13:41 am
Quote from: Quinten

I can only speak for the commands I receive on the RFXtrx for my BBSB modules, which have a command of either 0 (off) or 1 (on).  I really added the minimum so it would work for me.  Once I get the hang of it, I'll add more to it, but those will be done without the ability for me to test.

The code from the RFXCOM plugin does not expect 0 or 1  but a constant with a different value.
I will prppose an update later and you will be able to check if it is ok or not.

Sure, happy to test everything
Title: Re: New USB RFXCOM
Post by: lolodomo on March 11, 2012, 05:15:35 am
devices are created as LS/L1/F04 Possible confusor instance)...  isn't that already correct?
Possible confusion later with other kinds of lighting using subgype 1. Maybe not in this case as the real id starts with a letter which could be the unique case for all lightings.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 11, 2012, 05:20:05 am
Regarding all ON all OFF i will ask RFXCOM how it is managed by the RFXtrx.
Title: Re: New USB RFXCOM
Post by: Quinten on March 11, 2012, 05:21:56 am
devices are created as LS/L1/F04 Possible confusor instance)...  isn't that already correct?
Possible confusion later with other kinds of lighting using subgype 1. Maybe not in this case as the real id starts with a letter which could be the unique case for all lightings.

If you want to shuffle the id around to make it better falling in line with the temp sensors, then please do.
Title: Re: New USB RFXCOM
Post by: Quinten on March 11, 2012, 05:25:20 am
Regarding all ON all OFF i will ask RFXCOM how it is managed by the RFXtrx.

There is a table in the SDK saying which subtype supports which cmnds.  Subtype 1 (ARC) supports 0 (off), 1 (on), 5 (all off), 6 (all on).  Each subtype supports one or more of those commands (dim and bright for instance).
Title: Re: New USB RFXCOM
Post by: lolodomo on March 11, 2012, 06:00:12 am
Yes but i need to know if a unique message is sent and with what unit code.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 11, 2012, 06:09:26 am
To go to the next step,meaning sending a command to the RFXtrx from the binary light device,it is not clear for me how the plugin will be notified that an action has been triggered on this independent device.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 11, 2012, 01:08:50 pm
I will check tomorrow what code is at line 159.

At line 159, there is a call to the function luup.is_ready that might be unknown in UI4.
I will suppress it.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 11, 2012, 01:48:25 pm
New version attached.

GeeZay, tell me if it is working better (compatibility with UI4).
Quinten, tell me if it is still working with your lights.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: shapa on March 12, 2012, 10:16:45 am
Hi

I'd like to ask about plugin compatibility with LWRF protocol (which is supported by RFXCOM) (LightWaveRF / UK)

In fact, the LWRF hardware is good enough (and cheap), there are quite a lot of peoples purchased it, but the management appliance and the software are rubbish.

The management protocol is already reverse-engeneered and there are some plugins made for Indigo5 and so on, but it could be so much better to integrate everything to the MicasaVerde Vera interface (to use dimmers / switches / relays / power sockets natively).

Probably, everything is ready to do that (bearing in mind this plugin), but I'd like to ask about... Is it possible to use LWRF protocol with plugin right now? Or there should be some improvements made?

I could even send (for free for sure) some LWRF devices (dimmer + socket for example) to play with in case someone who skilled in Lua plugin development will add the support...

So many UK users will be happy about.

By the way, hardware part of LWRF is very good (and looks very cool, especially in stainless steel)

The protocol itself is very basic and easy to work with...
Title: Re: New USB RFXCOM
Post by: shapa on March 12, 2012, 10:31:01 am
"RFXtrx firmware dated the 7th of March" - by the way, looks like this firmware is not availible on the website... The latest one is 28 Feb 2012...

Is is private beta?
Title: Re: New USB RFXCOM
Post by: Quinten on March 12, 2012, 10:58:47 am
New version attached.

GeeZay, tell me if it is working better (compatibility with UI4).
Quinten, tell me if it is still working with your lights.

I'll give it a go this week.
Title: Re: New USB RFXCOM
Post by: Quinten on March 12, 2012, 10:59:41 am
"RFXtrx firmware dated the 7th of March" - by the way, looks like this firmware is not availible on the website... The latest one is 28 Feb 2012...

Is is private beta?

You're looking at the wrong firmware: http://rfxcom.com/documents/RFXrec433_firmware.zip
Title: Re: New USB RFXCOM
Post by: Quinten on March 12, 2012, 11:01:44 am
Hi

I'd like to ask about plugin compatibility with LWRF protocol (which is supported by RFXCOM) (LightWaveRF / UK)

In fact, the LWRF hardware is good enough (and cheap), there are quite a lot of peoples purchased it, but the management appliance and the software are rubbish.

The management protocol is already reverse-engeneered and there are some plugins made for Indigo5 and so on, but it could be so much better to integrate everything to the MicasaVerde Vera interface (to use dimmers / switches / relays / power sockets natively).

Probably, everything is ready to do that (bearing in mind this plugin), but I'd like to ask about... Is it possible to use LWRF protocol with plugin right now? Or there should be some improvements made?

I could even send (for free for sure) some LWRF devices (dimmer + socket for example) to play with in case someone who skilled in Lua plugin development will add the support...

So many UK users will be happy about.

By the way, hardware part of LWRF is very good (and looks very cool, especially in stainless steel)

The protocol itself is very basic and easy to work with...


The RFXtrx supports LightwaveRF, which are similar to my ByeBye Standby modules.  Although I have no such modules, it should not be to hard to add support for them, or at least the basics for supporting them
Title: Re: New USB RFXCOM
Post by: shapa on March 12, 2012, 11:24:16 am
Yes, I know it is supported - I even able to pair / switch off / on LWRF devices from the RFXmngr.exe...

The only question is to add the support to the module...

I'm ready to provide any info / support, but I'm not a developer :)
Title: Re: New USB RFXCOM
Post by: Quinten on March 12, 2012, 12:11:45 pm
Yes, I know it is supported - I even able to pair / switch off / on LWRF devices from the RFXmngr.exe...

The only question is to add the support to the module...

I'm ready to provide any info / support, but I'm not a developer :)

What you can do is install the plugin, wait a few minutes and then press a button on a remote, or some other event on your LWRF devices, so the message will be captured in the LuaUPNP.log file and paste the output?  The plugin will not do anything else for you, but at least we'll see what the messages look like...
Title: Re: New USB RFXCOM
Post by: lolodomo on March 12, 2012, 01:24:58 pm
I think we have to make it work properly and fully first for LIGHTING1 category (X10, BBSB, ... etc). Then it will be relatively easy to make it work for LightwaveRF.

I will check the RFXtrx specification regarding LightwaveRF today and I could at least put the support of LightwaveRF at the same level as what we have currently for X10 / BBSB, meaning having light devices displayed in Vera dashboard and status updated in live.

And I will try to understand how to handle actions from children. It would be cool if I could  implement ON and OFF buttons.

So a new version maybe later in the day...
Title: Re: New USB RFXCOM
Post by: shapa on March 12, 2012, 01:27:19 pm
LWRF devices are (mostly) 1-way, therefore no any output could be made...

Initially, any LWRF device should be paired with controller device (just by enabling pairing mode on a device and sending any command from a controller)

I've tried to use .exe application, which is working fine.

For example, I choose ID "AE:00:00", unit code "1" and sending "off" command:

Lighting5 command:09 14 00 0B AE 00 00 01 00 00
------------------------------------------------
0402010B00
Packettype        = Receiver/Transmitter Message
subtype           = Transmitter Response
Sequence nbr      = 11
response          = ACK, data correct transmitted

"on" command:

Lighting5 command:09 14 00 0C AE 00 00 01 01 00
------------------------------------------------
0402010C00
Packettype        = Receiver/Transmitter Message
subtype           = Transmitter Response
Sequence nbr      = 12
response          = ACK, data correct transmitted

Title: Re: New USB RFXCOM
Post by: shapa on March 12, 2012, 01:32:24 pm
Sounds really good :)

Is it possible to make "Pair" button as well?

Overall, there are such commands availble:

on / off (dimmers, sockets), open / close / stop (inline relays (open / close is similar to on / off)), set dim level (dimmers), set mood (dimmers)

It could be extremely cool in case it will work with Vera, as the situation with native controller (WiFi Link) and software is really awful...

I think we have to make it work properly and fully first for LIGHTING1 category (X10, BBSB, ... etc). Then it will be relatively easy to make it work for LightwaveRF.

I will check the RFXtrx specification regarding LightwaveRF today and I could at least put the support of LightwaveRF at the same level as what we have currently for X10 / BBSB, meaning having light devices displayed in Vera dashboard and status updated in live.

And I will try to understand how to handle actions from children. It would be cool if I could  implement ON and OFF buttons.

So a new version maybe later in the day...
Title: Re: New USB RFXCOM
Post by: lolodomo on March 12, 2012, 01:35:52 pm
Tag handleChildren must be used to handle children actions.

So now I should be able to implement the ON and OFF actions for the binay lights.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 12, 2012, 06:07:47 pm
Please find attached a new version of the plugin. Big step from the previous version.

This version should handle Power ON and Power OFF commands, including commands from the Vera binary light devices for lighting category 1, that is X10, ARC (HomeEasy, KlikAanKlikUit, ByeByeStandBy, Intertechno, ELRO,
AB600, Düwi, DomiaLite, COCO), ELRO AB400D, Waveman, Chacon EMW200 and IMPULS.
For lighting category 2, meaning AC (HomeEasy UK, KlikAanKlikUit, Chacon, NEXA, DI.O, Intertechno), HomeEasy EU and ANSLUT, and for LightWareRF and Siemens (lighting category 5), you should have the Vera light devices automatically created and status updated but not yet the ability to power ON or power OFF from the Vera. For these ones, I don't really understand what ID I have to put in the command message.

Quinten, GeeZay and shapa, please give me a feedback, I have no way to test that.

I don(t know if after sending a Power ON or Power OFF message, these modules send back a full lighting message. Currently I update the status of the Vera device just after sending the command. This is something to enhance, at least waiting for the ACK from the RFXCOM transmitter.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: Quinten on March 12, 2012, 07:06:16 pm
Nice one lolodomo!  Quickly tested it and here's my findings.

- Plugin wouldnt start on first upload, but that may have been due to me (being a unix geek/snob) removing some of your ^M and \t symbols from the uploaded files.  I know I should not care about these things, but I'm awkward like that ;)
- AutoCreate variable was not added to the device so I manually had to add it.  I'm sure on the previous version the variable was there, but just set to 0.
- With AutoCreate set to 1, a binary device is created on first invoke, but no buttons are displayed, until I manually hit the refresh button on the web page.  I suspect this is more due to Safari (which just had an update) than to any specific coding, but I thought I mention it anyway
- Sending commands work!  This is brilliant, and means I can nearly retire some of my dodgy BBSB network ;)
Title: Re: New USB RFXCOM
Post by: Quinten on March 12, 2012, 07:07:26 pm
Oh, and you should really make the plugin your own lolodomo, with a nice new URN ;)  Don't be shy!
Title: Re: New USB RFXCOM
Post by: lolodomo on March 12, 2012, 07:43:54 pm
Nice one lolodomo!  Quickly tested it and here's my findings.

- Plugin wouldnt start on first upload, but that may have been due to me (being a unix geek/snob) removing some of your ^M and \t symbols from the uploaded files.  I know I should not care about these things, but I'm awkward like that ;)
- AutoCreate variable was not added to the device so I manually had to add it.  I'm sure on the previous version the variable was there, but just set to 0.

Very strange because I have not changed the file where is declared the variable.
Maybe you could start again from scratch to check that all is ok.
I will do myself.

Quote
- With AutoCreate set to 1, a binary device is created on first invoke, but no buttons are displayed, until I manually hit the refresh button on the web page.  I suspect this is more due to Safari (which just had an update) than to any specific coding, but I thought I mention it anyway

Probably.
And when new devices are created, not by this plugin but more in general, I noticed that a reload or even a lua engine restart is sometimes required to have something clean.

Quote
- Sending commands work!  This is brilliant, and means I can nearly retire some of my dodgy BBSB network ;)

Very good news. 8)

Your first invoke to create the device is done using a BBSB remote control ?
Title: Re: New USB RFXCOM
Post by: lolodomo on March 12, 2012, 08:11:04 pm
Please find attached a new version of the plugin.

This version could (or should) handle Power ON and Power OFF commands, including commands from the Vera binary light devices for
- lighting category 1, that is X10, ARC (HomeEasy, KlikAanKlikUit, ByeByeStandBy, Intertechno, ELRO,
AB600, Düwi, DomiaLite, COCO), ELRO AB400D, Waveman, Chacon EMW200 and IMPULS
- lighting category 2, that is AC (HomeEasy UK, KlikAanKlikUit, Chacon, NEXA, DI.O, Intertechno), HomeEasy EU and ANSLUT
- lighting category 5, that is LightWareRF and Siemens

Quinten has already done a positive feedback for BBSB.

GeeZay and shapa, we are waiting for your feedback.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: Quinten on March 13, 2012, 04:34:02 am
Quote
Your first invoke to create the device is done using a BBSB remote control ?

Yes indeed.  The AutoCreate should be set to 1 by default imho, although if someone has a lot of RF devices that are supported by RFXtrx, then they potentially can wait a long time until all devices have been added ;)

Is the last .zip you posted the same as the one I was testing, or slightly tweaked?
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 08:23:44 am
Hi

I'm going to test it now
BTW, I'm trying to help Bert (by testing the new FW) to add support for the whole bunch of the LWRF stuff.

Inline relays are already supported in the new FW (open / close / stop), as well as mood 4 and mood 5...

Hopefully, it could be very easy to add inline relays to the plugin as well.

Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 10:32:17 am
Ok, now I'm confused a bit.

The plugin itself is easy to install, and it seems to work.

But how to let him know about LWRF devices? How to pair? I could pair from the .exe application (and send commands than), but I don't see the option to do that from the Vera plugin...

01   03/13/12 14:29:54.369   luup_log:13: RFXtrx: Starting RFXCOM device: 13 __LEAK__ this:45056 start:45056 to 0xb2b000 <0x2bc83680>
01   03/13/12 14:29:54.369   luup_log:13: RFXtrx: Serial port is connected <0x2bc83680>
01   03/13/12 14:29:54.370   luup_log:13: RFXtrx: Tree with number child devices: <0x2bc83680>
01   03/13/12 14:29:54.370   luup_log:13: RFXtrx:        door sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.370   luup_log:13: RFXtrx:      motion sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.371   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.371   luup_log:13: RFXtrx:      light switches: 0 <0x2bc83680>
01   03/13/12 14:29:54.372   luup_log:13: RFXtrx:     window covering: 0 <0x2bc83680>
01   03/13/12 14:29:54.372   luup_log:13: RFXtrx: temperature sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.373   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.373   luup_log:13: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2bc83680>
01   03/13/12 14:29:54.475   luup_log:13: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2bc83680>
01   03/13/12 14:29:54.476   luup_log:13: RFXtrx: ready <0x2bc83680>
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 10:38:18 am
Ok, more info.

One light device added automatically, but it's not working (and I don't know which one is added...)


01   03/13/12 14:27:20.377   luup_log:13: RFXtrx: Starting RFXCOM device: 13 __LEAK__ this:45056 start:45056 to 0x8c8000 <0x2bd61680>
01   03/13/12 14:27:20.378   luup_log:13: RFXtrx: Serial port is connected <0x2bd61680>
01   03/13/12 14:27:20.378   luup_log:13: RFXtrx: Tree with number child devices: <0x2bd61680>
01   03/13/12 14:27:20.379   luup_log:13: RFXtrx:        door sensors: 0 <0x2bd61680>
01   03/13/12 14:27:20.379   luup_log:13: RFXtrx:      motion sensors: 0 <0x2bd61680>
01   03/13/12 14:27:20.379   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2bd61680>
01   03/13/12 14:27:20.379   luup_log:13: RFXtrx:      light switches: 0 <0x2bd61680>
01   03/13/12 14:27:20.380   luup_log:13: RFXtrx:     window covering: 0 <0x2bd61680>
01   03/13/12 14:27:20.380   luup_log:13: RFXtrx: temperature sensors: 0 <0x2bd61680>
01   03/13/12 14:27:20.380   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2bd61680>
01   03/13/12 14:27:20.381   luup_log:13: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2bd61680>
01   03/13/12 14:27:20.483   luup_log:13: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2bd61680>
01   03/13/12 14:27:20.485   luup_log:13: RFXtrx: ready <0x2bd61680>
01   03/13/12 14:27:20.505   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 01 00 01 02 53 1A 00 4F 6F 00 00 00 00  <0x2e361680>
01   03/13/12 14:27:54.175   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 00 F0 00 1A 00 00 00 00 00 00 69  <0x2e361680>
01   03/13/12 14:28:50.375   luup_log:13: RFXtrx: Starting RFXCOM device: 13 __LEAK__ this:45056 start:45056 to 0xda6000 <0x2c01d680>
01   03/13/12 14:28:50.376   luup_log:13: RFXtrx: Serial port is connected <0x2c01d680>
01   03/13/12 14:28:50.376   luup_log:13: RFXtrx: Tree with number child devices: <0x2c01d680>
01   03/13/12 14:28:50.376   luup_log:13: RFXtrx:        door sensors: 0 <0x2c01d680>
01   03/13/12 14:28:50.377   luup_log:13: RFXtrx:      motion sensors: 0 <0x2c01d680>
01   03/13/12 14:28:50.377   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2c01d680>
01   03/13/12 14:28:50.377   luup_log:13: RFXtrx:      light switches: 0 <0x2c01d680>
01   03/13/12 14:28:50.377   luup_log:13: RFXtrx:     window covering: 0 <0x2c01d680>
01   03/13/12 14:28:50.378   luup_log:13: RFXtrx: temperature sensors: 0 <0x2c01d680>
01   03/13/12 14:28:50.378   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2c01d680>
01   03/13/12 14:28:50.379   luup_log:13: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2c01d680>
01   03/13/12 14:28:50.481   luup_log:13: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2c01d680>
01   03/13/12 14:28:50.482   luup_log:13: RFXtrx: ready <0x2c01d680>
01   03/13/12 14:28:50.495   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 01 00 01 02 53 1A 00 4F 6F 00 00 00 00  <0x2e61d680>
01   03/13/12 14:28:54.185   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 00 F0 00 1A 00 00 00 00 00 00 69  <0x2e61d680>
01   03/13/12 14:29:29.370   luup_log:13: RFXtrx: Starting RFXCOM device: 13 __LEAK__ this:49152 start:49152 to 0xc80000 <0x2bcbb680>
01   03/13/12 14:29:29.370   luup_log:13: RFXtrx: Serial port is connected <0x2bcbb680>
01   03/13/12 14:29:29.371   luup_log:13: RFXtrx: Tree with number child devices: <0x2bcbb680>
01   03/13/12 14:29:29.371   luup_log:13: RFXtrx:        door sensors: 0 <0x2bcbb680>
01   03/13/12 14:29:29.371   luup_log:13: RFXtrx:      motion sensors: 0 <0x2bcbb680>
01   03/13/12 14:29:29.372   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2bcbb680>
01   03/13/12 14:29:29.372   luup_log:13: RFXtrx:      light switches: 0 <0x2bcbb680>
01   03/13/12 14:29:29.372   luup_log:13: RFXtrx:     window covering: 0 <0x2bcbb680>
01   03/13/12 14:29:29.373   luup_log:13: RFXtrx: temperature sensors: 0 <0x2bcbb680>
01   03/13/12 14:29:29.373   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2bcbb680>
01   03/13/12 14:29:29.374   luup_log:13: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2bcbb680>
01   03/13/12 14:29:29.476   luup_log:13: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2bcbb680>
01   03/13/12 14:29:29.477   luup_log:13: RFXtrx: ready <0x2bcbb680>
01   03/13/12 14:29:29.495   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 01 00 01 02 53 1A 00 4F 6F 00 00 00 00  <0x2e2bb680>
01   03/13/12 14:29:43.511   luup_log:13: RFXtrx: Decoding not yet implemented for message 00  <0x2e2bb680>
01   03/13/12 14:29:54.369   luup_log:13: RFXtrx: Starting RFXCOM device: 13 __LEAK__ this:45056 start:45056 to 0xb2b000 <0x2bc83680>
01   03/13/12 14:29:54.369   luup_log:13: RFXtrx: Serial port is connected <0x2bc83680>
01   03/13/12 14:29:54.370   luup_log:13: RFXtrx: Tree with number child devices: <0x2bc83680>
01   03/13/12 14:29:54.370   luup_log:13: RFXtrx:        door sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.370   luup_log:13: RFXtrx:      motion sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.371   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.371   luup_log:13: RFXtrx:      light switches: 0 <0x2bc83680>
01   03/13/12 14:29:54.372   luup_log:13: RFXtrx:     window covering: 0 <0x2bc83680>
01   03/13/12 14:29:54.372   luup_log:13: RFXtrx: temperature sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.373   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2bc83680>
01   03/13/12 14:29:54.373   luup_log:13: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2bc83680>
01   03/13/12 14:29:54.475   luup_log:13: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2bc83680>
01   03/13/12 14:29:54.476   luup_log:13: RFXtrx: ready <0x2bc83680>
01   03/13/12 14:29:54.495   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 01 00 01 02 53 1A 00 4F 6F 00 00 00 00  <0x2e283680>
01   03/13/12 14:30:54.203   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 00 F0 00 1A 00 00 00 00 00 00 69  <0x2e283680>
01   03/13/12 14:31:54.205   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 01 F0 00 1A 00 00 00 00 00 00 69  <0x2e283680>
01   03/13/12 14:32:54.295   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 02 F0 00 1A 00 00 00 00 00 00 69  <0x2e283680>
01   03/13/12 14:33:54.225   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 03 F0 00 1A 00 00 00 00 00 00 69  <0x2e283680>
01   03/13/12 14:34:03.124   luup_log:13: RFXtrx: Received command 4 for 16 with ID L5.0/01 <0x2e283680>
01   03/13/12 14:34:03.125   luup_log:13: RFXtrx: device not found and autocreate enabled... <0x2e283680>
01   03/13/12 14:34:03.125   luup_log:13: RFXtrx: Tree buildup, now add L5.0/01 with sensortype 16 <0x2e283680>
01   03/13/12 14:34:03.126   luup_log:13: RFXtrx: CREATING CHILD DEVICE LIGHT SWITCH WITH ID L5.0/01 <0x2e283680>
01   03/13/12 14:34:03.126   luup_log:13: RFXtrx: Tree buildup with number child devices: <0x2e283680>
01   03/13/12 14:34:03.127   luup_log:13: RFXtrx:        door sensors: 0 <0x2e283680>
01   03/13/12 14:34:03.127   luup_log:13: RFXtrx:      motion sensors: 0 <0x2e283680>
01   03/13/12 14:34:03.127   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2e283680>
01   03/13/12 14:34:03.128   luup_log:13: RFXtrx:      light switches: 1 <0x2e283680>
01   03/13/12 14:34:03.128   luup_log:13: RFXtrx:    window coverings: 0 <0x2e283680>
01   03/13/12 14:34:03.128   luup_log:13: RFXtrx: temperature sensors: 0 <0x2e283680>
01   03/13/12 14:34:03.129   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2e283680>
01   03/13/12 14:34:03.129   luup_log:13: RFXtrx: Start sync <0x2e283680>
01   03/13/12 14:34:03.669   luup_log:13: RFXtrx: End sync <0x2e283680>
01   03/13/12 14:34:15.374   luup_log:13: RFXtrx: Starting RFXCOM device: 13 __LEAK__ this:40960 start:40960 to 0xf3d000 <0x2bb5f680>
01   03/13/12 14:34:15.375   luup_log:13: RFXtrx: Serial port is connected <0x2bb5f680>
01   03/13/12 14:34:15.375   luup_log:13: RFXtrx: Found child device, lets save! id LS/L5.0/01 device urn:schemas-upnp-org:device:BinaryLight:1 <0x2bb5f680>
01   03/13/12 14:34:15.375   luup_log:13: RFXtrx: Tree with number child devices: <0x2bb5f680>
01   03/13/12 14:34:15.376   luup_log:13: RFXtrx:        door sensors: 0 <0x2bb5f680>
01   03/13/12 14:34:15.376   luup_log:13: RFXtrx:      motion sensors: 0 <0x2bb5f680>
01   03/13/12 14:34:15.376   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2bb5f680>
01   03/13/12 14:34:15.377   luup_log:13: RFXtrx:      light switches: 1 <0x2bb5f680>
01   03/13/12 14:34:15.377   luup_log:13: RFXtrx:     window covering: 0 <0x2bb5f680>
01   03/13/12 14:34:15.377   luup_log:13: RFXtrx: temperature sensors: 0 <0x2bb5f680>
01   03/13/12 14:34:15.378   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2bb5f680>
01   03/13/12 14:34:15.379   luup_log:13: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2bb5f680>
01   03/13/12 14:34:15.481   luup_log:13: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2bb5f680>
01   03/13/12 14:34:15.482   luup_log:13: RFXtrx: ready <0x2bb5f680>
01   03/13/12 14:34:15.495   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 01 00 01 02 53 1A 00 4F 6F 00 00 00 00  <0x2e15f680>
01   03/13/12 14:34:54.234   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 00 F0 00 1A 00 00 00 00 00 00 69  <0x2e15f680>
01   03/13/12 14:35:54.242   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 01 F0 00 1A 00 00 00 00 00 00 69  <0x2e15f680>
01   03/13/12 14:36:05.289   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 1 <0x2d95f680>
01   03/13/12 14:36:05.290   luup_log:13: RFXtrx: Sending command: 09 14 00 02 AB CD EF 01 01 00  <0x2d95f680>
01   03/13/12 14:36:05.291   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 1 <0x2d95f680>
01   03/13/12 14:36:05.812   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:07.198   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 1 <0x2dd5f680>
01   03/13/12 14:36:07.199   luup_log:13: RFXtrx: Sending command: 09 14 00 03 AB CD EF 01 01 00  <0x2dd5f680>
01   03/13/12 14:36:07.199   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 1 <0x2dd5f680>
01   03/13/12 14:36:07.702   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:09.910   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 0 <0x2dd5f680>
01   03/13/12 14:36:09.911   luup_log:13: RFXtrx: Sending command: 09 14 00 04 AB CD EF 01 00 00  <0x2dd5f680>
01   03/13/12 14:36:09.912   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 0 <0x2dd5f680>
01   03/13/12 14:36:10.432   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:10.815   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 1 <0x2dd5f680>
01   03/13/12 14:36:10.816   luup_log:13: RFXtrx: Sending command: 09 14 00 05 AB CD EF 01 01 00  <0x2dd5f680>
01   03/13/12 14:36:10.817   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 1 <0x2dd5f680>
01   03/13/12 14:36:11.322   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:11.833   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 0 <0x2d95f680>
01   03/13/12 14:36:11.834   luup_log:13: RFXtrx: Sending command: 09 14 00 06 AB CD EF 01 00 00  <0x2d95f680>
01   03/13/12 14:36:11.835   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 0 <0x2d95f680>
01   03/13/12 14:36:12.342   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:12.824   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 1 <0x2dd5f680>
01   03/13/12 14:36:12.825   luup_log:13: RFXtrx: Sending command: 09 14 00 07 AB CD EF 01 01 00  <0x2dd5f680>
01   03/13/12 14:36:12.826   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 1 <0x2dd5f680>
01   03/13/12 14:36:13.332   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:13.723   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 1 <0x2e586680>
01   03/13/12 14:36:13.724   luup_log:13: RFXtrx: Sending command: 09 14 00 08 AB CD EF 01 01 00  <0x2e586680>
01   03/13/12 14:36:13.725   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 1 <0x2e586680>
01   03/13/12 14:36:14.227   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:15.006   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 0 <0x2e386680>
01   03/13/12 14:36:15.007   luup_log:13: RFXtrx: Sending command: 09 14 00 09 AB CD EF 01 00 00  <0x2e386680>
01   03/13/12 14:36:15.008   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 0 <0x2e386680>
01   03/13/12 14:36:15.522   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:15.750   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 1 <0x2d95f680>
01   03/13/12 14:36:15.751   luup_log:13: RFXtrx: Sending command: 09 14 00 0A AB CD EF 01 01 00  <0x2d95f680>
01   03/13/12 14:36:15.752   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 1 <0x2d95f680>
01   03/13/12 14:36:16.252   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:16.561   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 1 <0x2e586680>
01   03/13/12 14:36:16.562   luup_log:13: RFXtrx: Sending command: 09 14 00 0B AB CD EF 01 01 00  <0x2e586680>
01   03/13/12 14:36:16.563   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 1 <0x2e586680>
01   03/13/12 14:36:17.072   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:18.358   luup_log:13: RFXtrx: switchPower LS/L5.0/01 target 1 <0x2e386680>
01   03/13/12 14:36:18.359   luup_log:13: RFXtrx: Sending command: 09 14 00 0C AB CD EF 01 01 00  <0x2e386680>
01   03/13/12 14:36:18.360   luup_log:13: RFXtrx: SET STATUS from LS/L5.0/01 with value 1 <0x2e386680>
01   03/13/12 14:36:18.862   luup_log:13: RFXtrx: transmitter response 0 ACK <0x2e15f680>
01   03/13/12 14:36:54.245   luup_log:13: RFXtrx: Decoding not yet implemented for message 0D 59 01 02 F0 00 1A 00 00 00 00 00 00 69  <0x2e15f680>
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 10:48:20 am
Please note, that I'm using the newest firmware with Inline support (it is released officially today)

SDK is already updated as well
Title: Re: New USB RFXCOM
Post by: Quinten on March 13, 2012, 11:17:47 am
Ok, now I'm confused a bit.

The plugin itself is easy to install, and it seems to work.

But how to let him know about LWRF devices? How to pair? I could pair from the .exe application (and send commands than), but I don't see the option to do that from the Vera plugin...

We do not know how the pairing works.  All we have is the SDK and in the SDK there is no message defined to pair.

It's encouraging to see that a device was created though, that means that the messages that the RFXtrx received are correctly identified for LWRF.  Does the status of the device change at all when you press the button on a LWRF remote?
Title: Re: New USB RFXCOM
Post by: Quinten on March 13, 2012, 11:20:15 am
Ah no, you probably do not see status changes yet?

Code: [Select]
Decoding not yet implemented for message 0D 59 01 00 F0 00 1A 00 00 00 00 00 00 69
Decoding not yet implemented for message 0D 59 01 01 F0 00 1A 00 00 00 00 00 00 69

Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 11:40:19 am
The pairing procedure is very simple - just to switch on pairing mode on a device and send any command to it - that's is.
It means that LWRF device could not be added automatically... Until their settings (ID's) are stored somewhere in the RFX USB device.

The second issue is that LWRF devices are one-way and not broadcasting anything, therefore I'm really curios about which info is received as "Decoding not yet implemented "

Probably it is not LWRF but my neighbour energy monitor - I'm seeing it in the log window of the RFXmngr.exe

"------------------------------------------------
0D590103F0000000000000000049
Packettype    = CURRENT
subtype       = ELEC1 - OWL CM113, Electrisave, cent-a-meter
Sequence nbr  = 3
ID            = 61440
Count         = 0
Channel 1     = 0 ampere
Channel 2     = 0 ampere
Channel 3     = 0 ampere
Signal level  = 4
Battery       = OK"




We do not know how the pairing works.  All we have is the SDK and in the SDK there is no message defined to pair.

It's encouraging to see that a device was created though, that means that the messages that the RFXtrx received are correctly identified for LWRF.  Does the status of the device change at all when you press the button on a LWRF remote?
Title: Re: New USB RFXCOM
Post by: Quinten on March 13, 2012, 11:51:05 am
But obviously we still do not know what the pairing actually means with respect to the transmitter.  Does it need a fixed id of some sort with each message send to the LWRF device?

And you're right, the 0x59 message is from a current sensor, so it would be your neighbors electricity monitor...
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 12:21:14 pm
For the transmitter - no any pairing is required...
It's just sending (broadcasting) RF commands to the ID specified.
Pairing is required only for a receiving device to accept commands (security reason) and to remember the assigned ID...

In another words I can choose any ID on the RFXcom, enable pairing mode on the device, send any command to this ID / device,  device itself will store the info (up to 6 pairings is allowed)

Next time I'll send command to the same ID - device will react accordingly (on / off / stop / etc).

Therefore, looks like only manual devices creation is possible for Vera (this is not an issue anyway and this is the way the official application works), and "pairing" process is just to send any command to the specified ID.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 01:27:17 pm
A quick answer.

First, invoke ON or OFF with your remote control to create automatically the light device in the Vera. Then check that the status changes you order with your remote control are correctly handled by the Vera plugin, I mean the status of the light is updated accordingly. Is it ok ?

Then, you have to pair the Vera with your devices. Enter in pairing mode as usual and then push the button ON from the Vera light device. That should be enough to pair Vera with your unit.
Note that the current plugin uses a fixed ID for all LightwareRF commands, that means you can command only 16 different modules using unit code from 01 to 16. I will try to enhance that later but it will require that the user enters an ID.

When pairing is done, push ON and OFF buttons from the Vera light device and check the impact on the light. Is it ok ?

Normally, it should work, I am confident ;-)
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 01:30:22 pm
Quote
Your first invoke to create the device is done using a BBSB remote control ?

Yes indeed.  The AutoCreate should be set to 1 by default imho, although if someone has a lot of RF devices that are supported by RFXtrx, then they potentially can wait a long time until all devices have been added ;)

You're right, I will change the default value in the next version.

Quote
Is the last .zip you posted the same as the one I was testing, or slightly tweaked?

The last version puts lighting2 category and lighting5 category (LightwareRF) at the same level as lighting1. Nothing new regarding BBSB behaviour.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 01:37:22 pm
Hi

I'm going to test it now
BTW, I'm trying to help Bert (by testing the new FW) to add support for the whole bunch of the LWRF stuff.

Inline relays are already supported in the new FW (open / close / stop), as well as mood 4 and mood 5...

Hopefully, it could be very easy to add inline relays to the plugin as well.

Easy only if an existing Vera device is already available for inline relays, a device that will define services open, close and stop. Maybe we can used the curtain device that is used for the other RFXCOM plugin...

Regarding mood function, I need explanations. What is the usage and how does it work ?
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 03:01:56 pm
In fact, relay and curtain device are really close by the functionality - Vera supports inline relays like fibaro one

"Regarding mood function, I need explanations. What is the usage and how does it work ?"

Quite easy... "Mood" for the LWRF device - just to store current settings, and for the same room the same mood level (1 to 3 officially, 1 to 5 works in real) means to restore settings (dim level, on / off status, etc)

For example "Mood1" for my living room - setting dimmer to the 30%, switching on power sockets for the TV and satellite box, turning off everything else.


Regarding 16 devices - for sure it is not enough, the best thing is 16 devices per 16 rooms (it is supported by the hardware). The room ID is used to store the mood settings for a whole room as well.

To be honest, "mood" could be easily replaced by the Vera "scene" and not very important (it is much more important to support on / off for power sockets, on / off / dim level for light dimmers, open / stop / close for inline relays)
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 03:21:43 pm
In fact, relay and curtain device are really close by the functionality - Vera supports inline relays like fibaro one

With which device ? D_WindowCovering1.xml ?

it is much more important to support on / off for power sockets, on / off / dim level for light dimmers, open / stop / close for inline relays
[/quote]

Yes, light dimmers should be doable, we have the device D_DimmableLight1.xml.
My question is how to know, when I receive the initial command, if I must create a binary light or a dimmable light.
We could say that if the first message is a "set level" command, I create a dimmable light; if it is a "power ON" or "power OFF" command , I create a binary light.
Or more sophisticated, I could create a binary light device when I receive a power ON command, and then change to a dimmable light device when later I receive a "set level" command.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 03:22:29 pm
And finally, with my indications, do you confirm that Power ON and Power OFF is working well ?
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 03:54:53 pm
In fact, there are no binary lights exists for LWRF at all (and probably never be exists) - the problem is that there is no live neutral in most UK houses and the only way to create binary light is to use some battery (which is not really good)...

Therefore, it is quite safe to assume that every light is a dimmer :)))

I do not think that second way is good enough, as the procedure itself is already complicated - LWRF device should be paired with remote initially just to be able to pair with Vera

I'm trying to switch on / off my light and it is not working - but probably the reason "why" - i'm using version .26 firmware (it is expanded to support inline relays).

Probably, dimming will be supported today as well (Bert is working on) with a new firmware.

When I'm trying to swith Off / On dimmer (from the remote and the native application), the only message I've seen (once) in logs:

luup_log:13: RFXtrx: Decoding not yet implemented for message 00

The situation with power socket is a bit better - it is detected as a light switch and created, but not working after :)

01   03/13/12 19:52:45.939   luup_log:13: RFXtrx: Lighting2 command not yet implemented: 64 <0x2e6af680>
01   03/13/12 19:52:45.940   luup_log:13: RFXtrx: Received command 0 for 16 with ID L2.0/195 <0x2e6af680>
01   03/13/12 19:52:45.940   luup_log:13: RFXtrx: device not found and autocreate enabled... <0x2e6af680>
01   03/13/12 19:52:45.940   luup_log:13: RFXtrx: Tree buildup, now add L2.0/195 with sensortype 16 <0x2e6af680>
01   03/13/12 19:52:45.941   luup_log:13: RFXtrx: CREATING CHILD DEVICE LIGHT SWITCH WITH ID L2.0/195 <0x2e6af680>
01   03/13/12 19:52:45.941   luup_log:13: RFXtrx: Tree buildup with number child devices: <0x2e6af680>
01   03/13/12 19:52:45.942   luup_log:13: RFXtrx:        door sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.942   luup_log:13: RFXtrx:      motion sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.942   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.943   luup_log:13: RFXtrx:      light switches: 1 <0x2e6af680>
01   03/13/12 19:52:45.943   luup_log:13: RFXtrx:    window coverings: 0 <0x2e6af680>
01   03/13/12 19:52:45.943   luup_log:13: RFXtrx: temperature sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.944   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.944   luup_log:13: RFXtrx: Start sync <0x2e6af680>





Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 04:00:45 pm
BTW, I'm able to switch of and off power sockets from the .exe application (the commands are identical for dimmers and power sockets in fact), therefore probably something is wrong with the commands sent by the plugin.

Anyway, it is really big progress made only in one day - I'm very impressed.

Regarding relays - I'm not really sure which Vera device is the best idea to use, but I'm ready to play with / to make some tests (I've got 5 LWRF relays in my house)
Title: Re: New USB RFXCOM
Post by: Quinten on March 13, 2012, 04:20:25 pm
In fact, there are no binary lights exists for LWRF at all (and probably never be exists) - the problem is that there is no live neutral in most UK houses and the only way to create binary light is to use some battery (which is not really good)...

Therefore, it is quite safe to assume that every light is a dimmer :)))

Can I just say that a binary switch only provides on/off...  the same as any appliance module, or any of those sockets LWRF have.  The stuff about needing a neutral is not relevant.

http://www.lightwaverf.co.uk/LightwaveRF-Home-Automation-Power-Socket-Switched-1-gang-13amp.html = binary switch in Mios terminology
http://www.lightwaverf.co.uk/LightwaveRF-Connect-Home-Automation-Remote-Control-On-Off-Socket-Kit-3-Pack.html = same as above
http://www.lightwaverf.co.uk/LightwaveRF-Wireless-Control-1-Gang-2-Way-250W-Light-Switch-Dimmer-Choice-of-finishes.html = dimmable light in Mios (well duh ;))
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 04:41:23 pm
In fact, there are no binary lights exists for LWRF at all (and probably never be exists) - the problem is that there is no live neutral in most UK houses and the only way to create binary light is to use some battery (which is not really good)...

Therefore, it is quite safe to assume that every light is a dimmer :)))

I do not think that second way is good enough, as the procedure itself is already complicated - LWRF device should be paired with remote initially just to be able to pair with Vera

I'm trying to switch on / off my light and it is not working - but probably the reason "why" - i'm using version .26 firmware (it is expanded to support inline relays).

Probably, dimming will be supported today as well (Bert is working on) with a new firmware.

When I'm trying to swith Off / On dimmer (from the remote and the native application), the only message I've seen (once) in logs:

luup_log:13: RFXtrx: Decoding not yet implemented for message 00

Strange indeed. Probably a bug in the RFXtrx.

Quote
The situation with power socket is a bit better - it is detected as a light switch and created, but not working after :)

01   03/13/12 19:52:45.939   luup_log:13: RFXtrx: Lighting2 command not yet implemented: 64 <0x2e6af680>
01   03/13/12 19:52:45.940   luup_log:13: RFXtrx: Received command 0 for 16 with ID L2.0/195 <0x2e6af680>
01   03/13/12 19:52:45.940   luup_log:13: RFXtrx: device not found and autocreate enabled... <0x2e6af680>
01   03/13/12 19:52:45.940   luup_log:13: RFXtrx: Tree buildup, now add L2.0/195 with sensortype 16 <0x2e6af680>
01   03/13/12 19:52:45.941   luup_log:13: RFXtrx: CREATING CHILD DEVICE LIGHT SWITCH WITH ID L2.0/195 <0x2e6af680>
01   03/13/12 19:52:45.941   luup_log:13: RFXtrx: Tree buildup with number child devices: <0x2e6af680>
01   03/13/12 19:52:45.942   luup_log:13: RFXtrx:        door sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.942   luup_log:13: RFXtrx:      motion sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.942   luup_log:13: RFXtrx:      keyfob sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.943   luup_log:13: RFXtrx:      light switches: 1 <0x2e6af680>
01   03/13/12 19:52:45.943   luup_log:13: RFXtrx:    window coverings: 0 <0x2e6af680>
01   03/13/12 19:52:45.943   luup_log:13: RFXtrx: temperature sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.944   luup_log:13: RFXtrx:    humidity sensors: 0 <0x2e6af680>
01   03/13/12 19:52:45.944   luup_log:13: RFXtrx: Start sync <0x2e6af680>

Very strange. You received a lighting2 category message. To be clear, this message is not a LightwaveRF message !
In your previous traces, you received a LightwaveRF message.
It explains why you cannot pair and so cannot command the sockets.
Maybe the newRFXtrx firmware is not totally stable with LightwaveRF.
I will add a log of the full message for lighting messages in the next version to be sure of what has been received.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 04:46:18 pm
I just created a windows covering device to see how it looks like.
What's exactly the difference between Open and Up buttons ? Same question for Close and Down buttons ?
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 05:49:39 pm
Sure, you are right - this is binary _switch_, but not light :)

As I am new to the Vera world - the question is "are there any other binary devices exists (like power sockets)?"
It is much more better to put binary on / off devices in power socket or (even better) power switch category than lights :)

Once again - there are no any binary light switches made by LWRF / JSJS, and the official answer is - no live neutral in the UK as standard for light switches, therefore only dimmers are produced.

Can I just say that a binary switch only provides on/off...  the same as any appliance module, or any of those sockets LWRF have.  The stuff about needing a neutral is not relevant.
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 05:55:57 pm
It is really hard to answer for me...
I know that open and close commands for inline relay are connecting different wires (load) to the "live", and "stop" command is disconnecting "live" from a relay load.

It is very similar to the Zwave Fibaro inline relay (which is supported by Vera) and mentioned here (on forum) as Fibaro switch

http://materialy.fibaro.com/instrukcje/relay%20switch%20FGS221%20v1_4%20eng.pdf

I just created a windows covering device to see how it looks like.
What's exactly the difference between Open and Up buttons ? Same question for Close and Down buttons ?
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 05:58:56 pm
I'm awaiting for a new firmware from Bert to test dimming functionality, and will try to ask him to test receiver functionality as well...

Everything is OK when I'm playing with RFXmngr.exe - I could intercept all LWRF codes sent (switches, sockets, etc).
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 06:17:14 pm
New version that should manage Open/Close/Stop for LightwaveRF.

1) Like for a socket, you have first to use a remote control to produce a command that will be received by the Vera plugin. A windows covering device will then be created automatically when a Open/Close/Stop command is received. On this device, only Up, Stop and Down buttons are relevant (Open and Close buttons produce a "No implementation" error message I don't yet understand !)

2) pair your unit with the Vera using for example Up button

3) Use Up, Down and Stop buttons to check if the orders are sent to your device.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 06:23:46 pm
I'm awaiting for a new firmware from Bert to test dimming functionality, and will try to ask him to test receiver functionality as well...

Everything is OK when I'm playing with RFXmngr.exe - I could intercept all LWRF codes sent (switches, sockets, etc).

Please use the new version of the plugin and show me the log. Now I trace all lighting messages received.
For socket and inline relay.
Title: Re: New USB RFXCOM
Post by: Quinten on March 13, 2012, 06:32:18 pm
Sure, you are right - this is binary _switch_, but not light :)

As I am new to the Vera world - the question is "are there any other binary devices exists (like power sockets)?"
It is much more better to put binary on / off devices in power socket or (even better) power switch category than lights :)

Once again - there are no any binary light switches made by LWRF / JSJS, and the official answer is - no live neutral in the UK as standard for light switches, therefore only dimmers are produced.

We are talking about different things.  What I am trying to explain is that in Mios/Vera a device (whether that be an appliance module, a relay, a socket) which only has two settings; on and off, is considered a binary switch.  It does not say *what* it switches, just that it has the ability to switch something on or off.

This is why I said that the LWRF sockets and appliance modules are considered binary switches in Mios/Vera.  These LWRF devices only support on or off, and nothing in between (although for convenience I am ignoring the 'mood' setting as this muddles the water somewhat).
Title: Re: New USB RFXCOM
Post by: Quinten on March 13, 2012, 06:34:12 pm
BTW shapa, where in the UK are you?  I'm in Bucks myself
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 06:36:45 pm
Sure, you are right - this is binary _switch_, but not light :)

As I am new to the Vera world - the question is "are there any other binary devices exists (like power sockets)?"
It is much more better to put binary on / off devices in power socket or (even better) power switch category than lights :)

Once again - there are no any binary light switches made by LWRF / JSJS, and the official answer is - no live neutral in the UK as standard for light switches, therefore only dimmers are produced.

With Vera, there is one kind of device used for ON/OFF. The icon for this device is a light but this device can be used for everything that requires only ON and OFF commands. By the way, I have no way to distinguish a light and a socket in the message.

For dimmers, ok I should use another kind of device. But we can start with the binary light at least to check that you are able to turn ON or OFF your dimmable lights.

To be clear, first I want to be sure that messages are received and correctly decoded by the plugin, and that you can pair and send commands to your LightwaveRF modules with the plugin. Later, I could enhance and define new specific devices if necessary. I could try to add the possibility to address more than 16 modules ... etc
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 06:43:17 pm
Quinten, you were right for the AutoCreate variable. It is not created when the device is created. But the variable is automatically created later as soon as a first message is recognized by the plugin and a child has to be created.

I have changed the default value to true in the last version.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 06:45:29 pm
Hi lolodomo (is that your name?)

I forgot answering to your question.
Of course it is not my name, just a "funny" pseudo ;D
Title: Re: New USB RFXCOM
Post by: Quinten on March 13, 2012, 06:50:05 pm
Quinten, you were right for the AutoCreate variable. It is not created when the device is created. But the variable is automatically created later as soon as a first message is recognized by the plugin and a child has to be created.

I have changed the default value to true in the last version.

I'll give that a test later in the week, when you've got the LWRF stuff a bit more stable ;)

Hi lolodomo (is that your name?)

I forgot answering to your question.
Of course it is not my name, just a "funny" pseudo ;D

I'll just call you lol then ;)
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 07:14:50 pm
Well, it is more interesting now.

Immediately 3 more devices detected, but still there is no any reaction (even in pairing mode) on any command for any device...


01   03/13/12 22:58:51.375   luup_log:20: RFXtrx: Starting RFXCOM device: 20 __LEAK__ this:32768 start:32768 to 0x7b4000 <0x2bdbf680>
01   03/13/12 22:58:51.375   luup_log:20: RFXtrx: Serial port is connected <0x2bdbf680>
01   03/13/12 22:58:51.376   luup_log:20: RFXtrx: Found child device, lets save! id LS/L2.0/02 device urn:schemas-upnp-org:device:BinaryLight:1 <0x2bdbf680>
01   03/13/12 22:58:51.376   luup_log:20: RFXtrx: Found child device, lets save! id LS/L5.0/03 device urn:schemas-upnp-org:device:BinaryLight:1 <0x2bdbf680>
01   03/13/12 22:58:51.377   luup_log:20: RFXtrx: Found child device, lets save! id LS/L1.1/A01 device urn:schemas-upnp-org:device:BinaryLight:1 <0x2bdbf680>
01   03/13/12 22:58:51.377   luup_log:20: RFXtrx: Tree with number child devices: <0x2bdbf680>
01   03/13/12 22:58:51.378   luup_log:20: RFXtrx:        door sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.378   luup_log:20: RFXtrx:      motion sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.378   luup_log:20: RFXtrx:      keyfob sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.379   luup_log:20: RFXtrx:      light switches: 3 <0x2bdbf680>
01   03/13/12 22:58:51.379   luup_log:20: RFXtrx:     window covering: 0 <0x2bdbf680>
01   03/13/12 22:58:51.379   luup_log:20: RFXtrx: temperature sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.380   luup_log:20: RFXtrx:    humidity sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.381   luup_log:20: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2bdbf680>
01   03/13/12 22:58:51.482   luup_log:20: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2bdbf680>
01   03/13/12 22:58:51.484   luup_log:20: RFXtrx: ready <0x2bdbf680>
01   03/13/12 22:58:51.484   luup_log:20: RFXtrx: Received command 0 for 32 with ID C5.0/04 <0x2bdbf680>
01   03/13/12 22:58:51.485   luup_log:20: RFXtrx: device not found and autocreate enabled... <0x2bdbf680>
01   03/13/12 22:58:51.485   luup_log:20: RFXtrx: Tree buildup, now add C5.0/04 with sensortype 32 <0x2bdbf680>
01   03/13/12 22:58:51.486   luup_log:20: RFXtrx: Tree buildup with number child devices: <0x2bdbf680>
01   03/13/12 22:58:51.486   luup_log:20: RFXtrx:        door sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.487   luup_log:20: RFXtrx:      motion sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.487   luup_log:20: RFXtrx:      keyfob sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.488   luup_log:20: RFXtrx:      light switches: 3 <0x2bdbf680>
01   03/13/12 22:58:51.488   luup_log:20: RFXtrx:    window coverings: 1 <0x2bdbf680>
01   03/13/12 22:58:51.488   luup_log:20: RFXtrx: temperature sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.489   luup_log:20: RFXtrx:    humidity sensors: 0 <0x2bdbf680>
01   03/13/12 22:58:51.489   luup_log:20: RFXtrx: Start sync <0x2bdbf680>

Trying to detect one more power switch (by sending on and off commands) - no any reaction in logs normally, but once


"luup_log:20: RFXtrx: Decoding not yet implemented for message 62 00 00 62 00 00 62 00 00 62 84 C6 31 00 E4 31 00 40 22 00 40 22 0C 40 22 0C 40 22 04 40 22 0C 40 2E 0C 00 22 0C 80 11 00 00 22 0C 00 22 0C 86 11 00 A0 11 00 00 22 00 00 2F 0C 40 2E 0C 40 22 0C 40 22 0C 40 2F 0C 40 22 0C A6 11 00 80 11 00 A0 11 00 C4 11 00 00 22 00 00 22 0C 00 22 0C 00 22 0C 00  <0x2e69b680>
01   03/13/12 23:13:41.550   luup_log:20: RFXtrx: Decoding not yet implemented for message 22 00 00 22 0C 00 22 00 40 2E 0C 40 22 00 40 22 0C 40 22 00 40 22 04 E6 11 00 C0 11 00 E0 11 00 00 22 0C "



Please use the new version of the plugin and show me the log. Now I trace all lighting messages received.
For socket and inline relay.
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 07:16:31 pm
I'm located in Swindon :)


BTW shapa, where in the UK are you?  I'm in Bucks myself
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 07:18:39 pm
Ok, thank you for the explanation, that's fine - the icon and category are not really so important :)

The functionality is... Let's all on / off devices will be shown as lighting switch.


With Vera, there is one kind of device used for ON/OFF. The icon for this device is a light but this device can be used for everything that requires only ON and OFF commands. By the way, I have no way to distinguish a light and a socket in the message.

For dimmers, ok I should use another kind of device. But we can start with the binary light at least to check that you are able to turn ON or OFF your dimmable lights.

To be clear, first I want to be sure that messages are received and correctly decoded by the plugin, and that you can pair and send commands to your LightwaveRF modules with the plugin. Later, I could enhance and define new specific devices if necessary. I could try to add the possibility to address more than 16 modules ... etc
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 07:24:10 pm
Playing with remote controls (pushing on and off quite frequently, lights are reacting properly)...

Looks like RF commands are concatenated and not detected therefore (and once again - lighting2 category, but everything is disabled on the RFX device except AD (LWRF))


"01   03/13/12 23:21:38.410   luup_log:20: RFXtrx: LIGHTING2 message received A4 11 00 00 11 00 00 2E 0C 80 11 00 00 22 00 80 11 00 00 22 0C 40 22 0C A6 11 00 40 22 0C 40 22 0C 40 22 0C 40 22 00 40 22 0C A4 11 00 00 22 0C 00 22 00 C4 11 00 00 22 00 C0 11 00 C0 11 00 00 22 0C E0 11 00 40 22 0C 40 2E 0C 40 22 04 40 22 00 40 22 0C 40 22 0C C0 11 00 40 22 0C 80 22 04 80 2A 0C 80 22 04 80 22 00 80 22 04 80 2E 0C 84 11 00 80 22 00 C0 22 0C C0 22 0C C0 21 0C C0 11 08 C0 11 00 C0 11 04 80 42 C3 C0 11 00 80 11 00 80 11 00 80 11 00 80 71 0C C0 42 C3 80 11 0C 80 71 0C 80 2D 0C  <0x2e69b680>
01   03/13/12 23:21:38.411   luup_log:20: RFXtrx: Lighting2 command not yet implemented: 128 <0x2e69b680>"
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 07:50:16 pm
Well, it is more interesting now.

Immediately 3 more devices detected, but still there is no any reaction (even in pairing mode) on any command for any device...

When you push ON button on the binary light device or Up button on the window covering device, traces should be logged that show what message is sent by the RFXtrx. I would like to see these lines in the log to be sure that a message is sent.

I should see lines like that for a light/socket:

Code: [Select]
01      03/14/12 0:24:55.219    luup_log:47: RFXtrx: switchPower LS/L5.0/03 target 1 <0x2c87f680>
01      03/14/12 0:24:55.222    luup_log:47: RFXtrx: Sending command: 09 14 00 02 AB CD EF 03 01 00  <0x2c87f680>
01      03/14/12 0:24:55.223    luup_log:47: RFXtrx: SET STATUS from LS/L5.0/03 with value 1 <0x2c87f680>
01      03/14/12 0:24:55.732    luup_log:47: RFXtrx: transmitter response 0 ACK <0x2daac680>

for an inline relay:

Code: [Select]
01      03/14/12 0:25:50.874    luup_log:47: RFXtrx: windowCoveringUp WC/C5.0/04 <0x2c87f680>
01      03/14/12 0:25:50.875    luup_log:47: RFXtrx: Sending command: 09 14 00 03 AB CD EF 04 0F 00  <0x2c87f680>
01      03/14/12 0:25:51.382    luup_log:47: RFXtrx: transmitter response 0 ACK <0x2daac680>

Quote
Code: [Select]
01 03/13/12 22:58:51.376 luup_log:20: RFXtrx: Found child device, lets save! id LS/L2.0/02 device urn:schemas-upnp-org:device:BinaryLight:1 <0x2bdbf680>
01 03/13/12 22:58:51.376 luup_log:20: RFXtrx: Found child device, lets save! id LS/L5.0/03 device urn:schemas-upnp-org:device:BinaryLight:1 <0x2bdbf680>
01 03/13/12 22:58:51.377 luup_log:20: RFXtrx: Found child device, lets save! id LS/L1.1/A01 device urn:schemas-upnp-org:device:BinaryLight:1 <0x2bdbf680>

I am still not understanding why you have L1 and L2 devices. Do you use only LightwaveRF ?
Maybe you should erase all the children devices and reload the lua engine.

Quote
Code: [Select]
01 03/13/12 22:58:51.484 luup_log:20: RFXtrx: Received command 0 for 32 with ID C5.0/04 <0x2bdbf680>
01 03/13/12 22:58:51.485 luup_log:20: RFXtrx: device not found and autocreate enabled... <0x2bdbf680>

The line just before with the full message received would have helped. It lookd like you received a LightwaveRF message for your unit 04 (inline relay). But it is not normal that command value is 0 in the trace. Might be a bug in my code. But with no impact as I currently do nothing with this value.

Quote
Trying to detect one more power switch (by sending on and off commands) - no any reaction in logs normally, but once


"luup_log:20: RFXtrx: Decoding not yet implemented for message 62 00 00 62 00 00 62 00 00 62 84 C6 31 00 E4 31 00 40 22 00 40 22 0C 40 22 0C 40 22 04 40 22 0C 40 2E 0C 00 22 0C 80 11 00 00 22 0C 00 22 0C 86 11 00 A0 11 00 00 22 00 00 2F 0C 40 2E 0C 40 22 0C 40 22 0C 40 2F 0C 40 22 0C A6 11 00 80 11 00 A0 11 00 C4 11 00 00 22 00 00 22 0C 00 22 0C 00 22 0C 00  <0x2e69b680>
01   03/13/12 23:13:41.550   luup_log:20: RFXtrx: Decoding not yet implemented for message 22 00 00 22 0C 00 22 00 40 2E 0C 40 22 00 40 22 0C 40 22 00 40 22 04 E6 11 00 C0 11 00 E0 11 00 00 22 0C "

They are unexpected messages. Very strange, I have nothing like that.
Did you set the serial port to 38400 bauds and leave unchanged all the other properties ?
Do you see these messages with the test application from RFXCOM ?
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 07:57:17 pm
Playing with remote controls (pushing on and off quite frequently, lights are reacting properly)...

Looks like RF commands are concatenated and not detected therefore (and once again - lighting2 category, but everything is disabled on the RFX device except AD (LWRF))


"01   03/13/12 23:21:38.410   luup_log:20: RFXtrx: LIGHTING2 message received A4 11 00 00 11 00 00 2E 0C 80 11 00 00 22 00 80 11 00 00 22 0C 40 22 0C A6 11 00 40 22 0C 40 22 0C 40 22 0C 40 22 00 40 22 0C A4 11 00 00 22 0C 00 22 00 C4 11 00 00 22 00 C0 11 00 C0 11 00 00 22 0C E0 11 00 40 22 0C 40 2E 0C 40 22 04 40 22 00 40 22 0C 40 22 0C C0 11 00 40 22 0C 80 22 04 80 2A 0C 80 22 04 80 22 00 80 22 04 80 2E 0C 84 11 00 80 22 00 C0 22 0C C0 22 0C C0 21 0C C0 11 08 C0 11 00 C0 11 04 80 42 C3 C0 11 00 80 11 00 80 11 00 80 11 00 80 71 0C C0 42 C3 80 11 0C 80 71 0C 80 2D 0C  <0x2e69b680>
01   03/13/12 23:21:38.411   luup_log:20: RFXtrx: Lighting2 command not yet implemented: 128 <0x2e69b680>"

It looks like there is a total mismatch to detect correctly the beginning of the messages. For example, this one is largely too big and the second number "11" identified the message as a LIGHTING2 message but it is not. I understand now why you have L1 and L2 devices.

One again, are you sure about your serial port speed ?

I will add a control of the message length, it will avoid bad interpretation of messages.
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 08:12:31 pm
Ok, everything is so much better now.

I reloaded my vera :)

Inline relay (window :)) ) is perfectly working now. Open, stop and close - everything is fine. Aren't there any other device classes which are acceptable to use? I'm asking just because there are "open / close / set level" buttons which are not implemented (for sure). Up, down and stop are perfectly working.

And power socket is working as well :))) On / off.

Hooray! :)

The only "issue" is to identify each device - they were created automatically, but not paired, so I just tried (one by one) all buttons...

Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 08:20:13 pm
One more good thing - new devices are detected virtually instantly (less than 1 second and


01   03/14/12 0:18:46.561   luup_log:20: RFXtrx: Received command 8 for 16 with ID L5.0/10 <0x2df2d680>
01   03/14/12 0:18:46.562   luup_log:20: RFXtrx: device not found and autocreate enabled... <0x2df2d680>
01   03/14/12 0:18:46.563   luup_log:20: RFXtrx: Tree buildup, now add L5.0/10 with sensortype 16 <0x2df2d680>
01   03/14/12 0:18:46.563   luup_log:20: RFXtrx: CREATING CHILD DEVICE LIGHT SWITCH WITH ID L5.0/10 <0x2df2d680>

)
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 08:24:22 pm
New version. Message length is now checked before decoding. That will allow not decoding messages that have a wrong size.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 08:39:21 pm
Even more good news...

1) Light switch (dimmer) working as well - there is no dimming supported yet (for sure, as firmware is not exists yet :)) ), but on and off are working just fine.

2) What is really cool - Vera is able to detect when remote command is send from remote control (or master switch) and changing the status accordingly! GUI showing the real status of the device... WOW :)
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 08:41:49 pm
Ok, everything is so much better now.

I reloaded my vera :)

Inline relay (window :)) ) is perfectly working now. Open, stop and close - everything is fine.

At least a good news 8)  ;D

Quote
Aren't there any other device classes which are acceptable to use? I'm asking just because there are "open / close / set level" buttons which are not implemented (for sure). Up, down and stop are perfectly working.

I don't know. It would be possible to define a new device if necessary with less features (and so less buttons).
As I said previously, the "not implemented" behind Open and Close buttons is something I don't understand. It should probably correspond to SwitchPower1 services that are implemented by my plugin. I will probably find an explanation later.

The first thing I would like to understand: why is there so many buttons on this device ?

Quote
And power socket is working as well :))) On / off.

Hooray! :)

 8)

Quote
The only "issue" is to identify each device - they were created automatically, but not paired, so I just tried (one by one) all buttons...

The two numbers at the end of the device name is the unit code of your module, something between 01 and 16. That is the best way to identify the device. Then, of course, you are encouraged to rename it manually and for example to move it in the correct room.

When you say "not paired", I am not sure to understand. You necessarly paired the Vera with each unit. If not, the commands from the Vera would not arrive to the unit ?
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 08:47:40 pm
Even more good news...

1) Light switch (dimmer) working as well - there is no dimming supported yet (for sure, as firmware is not exists yet :)) ), but on and off is working just fine.

 8)

Quote
2) What is really cool - Vera is able to detect when remote command is send from remote control (or master switch) and changing the status accordingly! GUI showing the real status of the device... WOW :)

This is because it is well managed by the plugin ;)
Note that this is currently done only for "lights" (ON/OFF).

So, to summarize, everything I have implemented is working for you. 8) Enhancements regarding UI will follow in the future.

Only point I would like to clarify now is if pairing is required or not to send commands from the Vera to the LightwaveRF modules.
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 08:50:21 pm
"If not, the commands from the Vera would not arrive to the unit ?"

Yes, exactly what I'm talking about. They are not going to be delivered... Until i switch the pairing mode on and send any command.

Even more fun: the device "id" is not permanent and could be different for any from 6 paired devices...

I.e. the same switch could be "id:1" for paired remote control and "id:15" for master switch and "id:4" for Vera :)

That's why probably the good idea is to implement manual device addition (which could be very helpful to avoid to use any remotes)

For now I'm forced to use LWRF plugin for Indigo to send RF commands (to intercept them by RFXcom and automatically create device in Vera..)
The mess happens when there are many devices detected simultaneously :)

It is possible to make some great mess by mistake - to use "wrong" device to pair - for example to "overlap" ID's...
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 08:53:19 pm
"everything I have implemented is working for you. "

Yes, you are genius. quite a lot of LWRF users will dance something like mambo-jambo :D

May I ask for one more (hopefully small :)) ) thing? Is it possible to enable more than 16 devices? It is not a problem to change the room ID manually... I've got much more than 16 LWRF devices now :)
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 09:16:49 pm
I just realize that I forgot to put some code in comments. It explained why some L1 and L2 devices were created. It was for my own testings. Sorry.

So here is now the clean version.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 09:23:35 pm
"everything I have implemented is working for you. "

Yes, you are genius. quite a lot of LWRF users will dance something like mambo-jambo :D

May I ask for one more (hopefully small :)) ) thing? Is it possible to enable more than 16 devices? It is not a problem to change the room ID manually... I've got much more than 16 LWRF devices now :)

Your idea would be to use a different ID depending on the room in which is the device ? That looks like a very good idea and very easy to implement. Will do it tommorow night.
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 09:24:42 pm
I installed the "clean" one...

And status synchronisation stopped to work :)

01   03/14/12 1:23:30.820   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 00 F0 C0 0B 01 01 60 00 00  <0x2e665680>
01   03/14/12 1:23:34.570   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 01 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:34.850   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 02 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:37.801   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 03 F0 C0 0B 01 01 60 00 00  <0x2e665680>
01   03/14/12 1:23:40.870   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 04 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:52.710   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 05 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:52.990   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 06 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:55.260   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 07 F0 C0 0B 01 01 60 00 00  <0x2e665680>
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 09:26:03 pm
Exactly! :)

Very easy and clean way to differentiate the devices.

Your idea would be to use a different ID depending on the room in which is the device ? That looks like a very good idea and very easy to implement. Will do it tommorow night.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 09:27:56 pm
That's why probably the good idea is to implement manual device addition (which could be very helpful to avoid to use any remotes)

Probably not easy to implement because there are parameters to set for each device to be created (unit code, category and sub category, ... etc)

Quote
For now I'm forced to use LWRF plugin for Indigo to send RF commands (to intercept them by RFXcom and automatically create device in Vera..)
The mess happens when there are many devices detected simultaneously :)

It is possible to make some great mess by mistake - to use "wrong" device to pair - for example to "overlap" ID's...

Sorry, I don't understand your last question.
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 09:31:52 pm
" luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 0A F0 C0 0B 01 00 60 00 00 " - off command sent from remote

"luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 0E F0 C0 0B 01 01 60 00 00" - on command sent from remote....

It used to work (detected status) with previous plugin version :)
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 09:32:30 pm
I installed the "clean" one...

And status synchronisation stopped to work :)

01   03/14/12 1:23:30.820   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 00 F0 C0 0B 01 01 60 00 00  <0x2e665680>
01   03/14/12 1:23:34.570   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 01 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:34.850   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 02 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:37.801   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 03 F0 C0 0B 01 01 60 00 00  <0x2e665680>
01   03/14/12 1:23:40.870   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 04 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:52.710   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 05 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:52.990   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 06 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:55.260   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 07 F0 C0 0B 01 01 60 00 00  <0x2e665680>

These messages are not compliant with the specification ! Please inform Bert.
I suppress the length checking for LIGHTING5 messages in few mintes...
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 09:35:12 pm
Version without the length check for LIGHTING5 messages.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 09:35:36 pm
"I don't understand your last question'

Sure, it is a bit complicated...

Ok, quite easy to explain.
I overlapped ID's by enabling pairing mode on the power socket but pressed wrong button in the GUI (from a main light device :) )


They paired successfully... When I tried to press "off" or "on" on a remote control (or master switch), Vera shows status changes for a power socket (but not a main light)

What happens is very simple - the same ID used for different devices... Unfortunately, there is nothing like unique / permanent MAC address exists for LWRF devices
Title: Re: New USB RFXCOM
Post by: lolodomo on March 13, 2012, 09:38:06 pm
Really time to sleep for me now ;)
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 09:41:23 pm
Ok, I already informed Bert :)

The new version (without length checks) working fine once again...

01   03/14/12 1:40:59.988   luup_log:20: RFXtrx: LIGHTING5 message received 0B 14 00 02 F0 C0 0B 01 01 50 00 00  <0x2e8bf680>
01   03/14/12 1:40:59.989   luup_log:20: RFXtrx: Received command 4 for 16 with ID L5.0/01 <0x2e8bf680>
01   03/14/12 1:40:59.990   luup_log:20: RFXtrx: SET STATUS from L5.0/01 with value 1 <0x2e8bf680>
01   03/14/12 1:41:04.200   luup_log:20: RFXtrx: LIGHTING5 message received 0B 14 00 03 F0 C0 0B 01 00 60 00 00  <0x2e8bf680>
01   03/14/12 1:41:04.201   luup_log:20: RFXtrx: Received command 8 for 16 with ID L5.0/01 <0x2e8bf680>
01   03/14/12 1:41:04.202   luup_log:20: RFXtrx: SET STATUS from L5.0/01 with value 0 <0x2e8bf680>


I installed the "clean" one...

And status synchronisation stopped to work :)

01   03/14/12 1:23:30.820   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 00 F0 C0 0B 01 01 60 00 00  <0x2e665680>
01   03/14/12 1:23:34.570   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 01 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:34.850   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 02 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:37.801   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 03 F0 C0 0B 01 01 60 00 00  <0x2e665680>
01   03/14/12 1:23:40.870   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 04 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:52.710   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 05 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:52.990   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 06 F0 C0 0B 01 00 60 00 00  <0x2e665680>
01   03/14/12 1:23:55.260   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 14 00 07 F0 C0 0B 01 01 60 00 00  <0x2e665680>

These messages are not compliant with the specification ! Please inform Bert.
I suppress the length checking for LIGHTING5 messages in few mintes...
Title: Re: New USB RFXCOM
Post by: shapa on March 13, 2012, 09:43:04 pm
Really time to sleep for me now ;)

yeah, it is a really good idea :)

2am GMT time...
Title: Re: New USB RFXCOM
Post by: lolodomo on March 14, 2012, 05:35:17 am
I realize that for LightwaveRF my current plugin will only create a maximum of 16 devices, one for rach unit code from 1 to 16. All modules with the same unit code will be considered by the plugin as the same module ! As you can have more than 16 modules and so modules with the same unit code, I am forced to consider the pairing (remote id + unit code of the module) as a unique identifier. That is the only solution I have to update the status of the right device when I receive a message from RFXtrx.

One advantage would be that you will not have to paar the Vera with the modules because I will then use the ID of the remote to send commands with the Vera/RFXtrx.

One disadvantage is that the modules will be multiplied if you have several controllers for the same module. Only the device corresponding to the pair will have its status updated when receiving a command.

The solution would be to give the ability to the user to define which pairs correspond to the same module. I don't know how to do that simply.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 14, 2012, 05:41:08 am
Later I will add the manual creation of device as it is absolutely required for certain devices like for example for the Harrison  curtain.
Title: Re: New USB RFXCOM
Post by: shapa on March 14, 2012, 12:29:24 pm
"I will then use the ID of the remote to send commands with the Vera/RFXtrx."

I'm not really sure it is going to work...  First of all - there is no any remote which is capable to connect / pair to more than 16 devices, at second - there are no any remotes "by default"... Inline relays are not supported by standart remotes (special control made for that)...

May be it is possible to match the data partly?
Title: Re: New USB RFXCOM
Post by: lolodomo on March 14, 2012, 03:13:51 pm
"I will then use the ID of the remote to send commands with the Vera/RFXtrx."

I'm not really sure it is going to work...  First of all - there is no any remote which is capable to connect / pair to more than 16 devices, at second - there are no any remotes "by default"... Inline relays are not supported by standart remotes (special control made for that)...

May be it is possible to match the data partly?

The idea is simply to simulate with the RFXtrx any controller (remote or special control). For sure, it will work with no limit.

By the way, I have to change something relatively deeply. My current idea would be to store the "sender" id in a variable of the device. So in the first time, I will create a new device for each "sender" id, that means for each pairing. Then, it would be possible, to change the variable manually to put (on the same device) a list of "sender" id. Unnecessary devices will be deleted by the user. Doing that, all "senders" for the same module will update the status of a unique device.
And of course, a manual creation will be necessary, at least for people who don't have "sender".
I think it is a good solution but it will require at init a manual setup by the user to finally redefine all pairings.
Title: Re: New USB RFXCOM
Post by: shapa on March 14, 2012, 07:23:07 pm
I think it is not an issue (to redefine everything), looks like your idea is quite comprehensive :)


BTW, Bert is so kind to release the new FW (.27) - with fixes for incorrect length for LWRF messages...

Title: Re: New USB RFXCOM
Post by: shapa on March 19, 2012, 11:00:35 am
Lolodomo,

please take note that the new FW (.29) release and dimming is supported now, but packet length is different (longer)

Thank you!
Title: Re: New USB RFXCOM
Post by: lolodomo on March 19, 2012, 08:30:27 pm
Lolodomo,

please take note that the new FW (.29) release and dimming is supported now, but packet length is different (longer)

Thank you!

I will update the plugin and manage dimming for LightwaveRF.
I just finished the full rewritting of the plugin to have better code in my own point of view.
So now I will start again with adding new features.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 20, 2012, 05:23:02 am
Shapa, do you know if you can "dim" a window covering with LighwaveRF, meaning ordering a defined position ?
Title: Re: New USB RFXCOM
Post by: shapa on March 20, 2012, 05:46:37 am
The fixed "position" is only possible for dimmers - it is possible to set precise number.

Inline relay is only supports open / close / stop

It is really good to know that you are finished rewriting :)
Title: Re: New USB RFXCOM
Post by: bthovda on March 20, 2012, 03:40:41 pm
Hello experts!

Finally got my RFXCOM USB Transceiver.

I've looked all over this forum for a quick tutorial on how to connect RFXCOM USB - Transceiver  to my vera 3.
(A-Z type tutorial/For dummies)

My plan is to connect two Oregon Scientific Temperature sensors (THC238) to my Vera, through my RFXCOM usb interface.

Im relative new to "Vera world", but im used to programming in all kinds of languages.

Do anyone know where I could find such tutorial?

Thank you!
Title: Re: New USB RFXCOM
Post by: lolodomo on March 20, 2012, 04:14:20 pm
You will basic instructions inside this topic.

To make it quickly:
1) upload each file from the ZIP file into the Vera using Apps => Develop Apps => Luup files; then reload the lua engine
Depending on firmware versions, it could be required to upload the L_RFXtrx.lua using WinSCP because it will not work if the Lua file is uploaded compressed. I have not yet tried with the recent UI5 firmware
2) Create a new device using Apps => Develop Apps => Create Device, use D_RFXtrx.xml file as Upnp Device Filename; then reload the lua engine
3) Setup the serial port using Apps => Develop Apps => Serial Port configuration; set speed to 38400 bauds; then reload the lua engine

After that it should work, your temperature and humidity sensors should appear.

I will release very soon a new version.
Title: Re: New USB RFXtrx from RFXCOM
Post by: lolodomo on March 21, 2012, 06:56:59 pm
Please find attached a new draft version.
This version is mainly a code rewritten.
This version is compatible with RFXtrx firmware v29.
Battery level is now set on temperature and humidity sensors.

Edit: a new version is available below in this topic
Title: Re: Plguin for the USB RFXtrx from RFXCOM
Post by: shapa on March 22, 2012, 03:25:10 am
Unfortunately, I could not test it right now as I'm hospitalised with appendix abroad (happens on a plane - I'm kinda lucky)  :)

Will test it on the next Wednesday

Hopefully someone else will test it earlier.

BTW, I'm receiving private messages from LWRF users - they are asking about "how to" use  Vera3 + LWRF

When everything will be stabilised, I'll create some manual with examples.

Thank you very much for your work!
Title: Re: Plguin for the USB RFXtrx from RFXCOM
Post by: Quinten on March 22, 2012, 05:10:47 am
Please find attached a new draft version.
This version is mainly a code rewritten.
This version is compatible with RFXtrx firmware v29.
Battery level is now set on temperature and humidity sensors.

Excellent lolodomo!  I'll give it a go later today.

Unfortunately, I could not test it right now as I'm hospitalised with appendix abroad (happens on a plane - I'm kinda lucky)  :)

Eek!  Get well soon, shapa!
Title: Re: Plguin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 22, 2012, 08:26:44 am
Unfortunately, I could not test it right now as I'm hospitalised with appendix abroad (happens on a plane - I'm kinda lucky)  :)

Eek!  Get well soon, shapa!

+1
Title: Re: Plguin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 22, 2012, 08:35:48 am
BTW, I'm receiving private messages from LWRF users - they are asking about "how to" use  Vera3 + LWRF

When everything will be stabilised, I'll create some manual with examples.

Thank you very much for your work!

Be carreful, this is still a very alpha version for what is relative to LightwaveRF.
I will try to improove this part during the next week.

My TODO list:
1) manage barometric and wind sensors
2) manage correctly LIGHTING2 and LIGHTING5 messages in order to keep somewhere traces of the pairings
3) manage light dimming for X10 and LigfhtwaveRF
4) manage the result of "Get Status" command (and store in variables the protocols decoded by the RFXtrx)
5) manage the setup of the RFXtrx through the plugin (manage "Set Mode" command)
6) check at startup the characteristics of the serial connection (bauds, parity, ...)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 22, 2012, 11:59:46 am
"1) manage barometric and wind sensors"

Cool, I ordered PRO set from the OregonScientific two days ago (wind, baro, temp, hydro, UV...) and will be able to test everything as well.
BTW, it is nice idea to support UV sensor as well - could you please? I'll provide all info in case something is required.

http://uk.oregonscientific.com/cat-Weather-sub-Professional-prod-Professional-Weather-Station-UV-plus-extra-sensor.html

"3) manage light dimming for X10 and LigfhtwaveRF"

My question is not posted but already answered :)))
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: strangely on March 22, 2012, 01:19:00 pm
I also have a WMR88A kit which includes a wind sensor.

http://www.oregonscientificstore.com/sensors.asp?mfg=oregonsc0&base=315746

Probably wont have my RFXtrx for a week or so, but can gather logs for support also if need be.
Title: Re: New USB RFXCOM
Post by: bthovda on March 23, 2012, 06:14:40 pm
You will basic instructions inside this topic.

To make it quickly:
1) upload each file from the ZIP file into the Vera using Apps => Develop Apps => Luup files; then reload the lua engine
Depending on firmware versions, it could be required to upload the L_RFXtrx.lua using WinSCP because it will not work if the Lua file is uploaded compressed. I have not yet tried with the recent UI5 firmware
2) Create a new device using Apps => Develop Apps => Create Device, use D_RFXtrx.xml file as Upnp Device Filename; then reload the lua engine
3) Setup the serial port using Apps => Develop Apps => Serial Port configuration; set speed to 38400 bauds; then reload the lua engine

After that it should work, your temperature and humidity sensors should appear.

I will release very soon a new version.

Thank you! I got it to work.
Only thing thats wrong is when the temperature goes below 0 degree C, it doesnt shows a minus sign ( - ) in front of the number.
Simple trick for this?
do you know if its possible to include ('C) after the temperature to indicate that its Celcius.

Thank you again!!

- BT
Title: Re: New USB RFXCOM
Post by: lolodomo on March 23, 2012, 09:49:20 pm
Only thing thats wrong is when the temperature goes below 0 degree C, it doesnt shows a minus sign ( - ) in front of the number.
Simple trick for this?

I am sure that at the beginning I tested the deconding of a negative temperature sent by the RFXtrx. But I have never checked later that the value set on the Vera temperature device was ok. I will check that this week-end.

Quote
do you know if its possible to include ('C) after the temperature to indicate that its Celcius.

Yes it would be possible but it will require to not use the defaut temperature device and to define one specific.



A new version will probably be pushed at the end of the week-end; it should include a lot of new things.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 25, 2012, 03:10:46 am
Just my 5 cents - I think it is better to avoid custom temperature virtual devices and check everything with MicasaVerde - in case there is a bug in the soft are, it should be fixed. World is big, there are many places with negative temperature (in Celsius)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 25, 2012, 05:21:54 am
Just my 5 cents - I think it is better to avoid custom temperature virtual devices and check everything with MicasaVerde - in case there is a bug in the soft are, it should be fixed. World is big, there are many places with negative temperature (in Celsius)

What I have to add is a conversion, depending on the unit chosen by the user in the Vera settings. Currently, temperature are displayed by the plugin in °C.

I have to finish the debugging of my new devices (json files) but you should have very soon (maybe this evening) barometer, rain and wind sensors supported by the plugin.
Title: Re: New USB RFXCOM
Post by: lolodomo on March 25, 2012, 05:19:19 pm
Thank you! I got it to work.
Only thing thats wrong is when the temperature goes below 0 degree C, it doesnt shows a minus sign ( - ) in front of the number.

Ok, there was a stupid bug in my code !
That is now corrected and verified - I put my sensor in my freezer.
The fix will be included in the next version.

Finally, next version will not be released today, but probably beginning of the coming week.
Title: Re: New USB RFXCOM
Post by: bthovda on March 26, 2012, 03:30:59 pm
Thank you! I got it to work.
Only thing thats wrong is when the temperature goes below 0 degree C, it doesnt shows a minus sign ( - ) in front of the number.

Ok, there was a stupid bug in my code !
That is now corrected and verified - I put my sensor in my freezer.
The fix will be included in the next version.

Finally, next version will not be released today, but probably beginning of the coming week.


Perfect! Thank you!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 27, 2012, 05:50:34 pm
Here is a new alpha version.

This new version handle barometer, rain and wind sensors. 3 new Vera devices have been created but these devices are not yet fully finished (the generic icon is used and they cannot be used as trigger in a scene). I don't really know how they will be displayed in a UI4 dashboard (I cannot test). If someone wants to design icons for this plugin, please contribute.

For LightwaveRF, this is still really experimental but I have now added dimmable lights. All this is still not managed as it should be (pairings not stored, limited to the control of 16 modules, ...).

Please give me your feedback.

Finishing LightwaveRF (and all lighting2 category) is my next priority. After that, I think a first "official" release could be released.

Edit: a new version is available below in this topic
Title: Re: New USB RFXCOM
Post by: lolodomo on March 27, 2012, 05:57:45 pm
do you know if its possible to include ('C) after the temperature to indicate that its Celcius.

This can be done easily by updating the D_TemperatureSensor1.json in order to add a new label at the position you wish. Check the wiki to understand how work the JSON files.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 29, 2012, 05:21:37 am
Finally, I'm back home :)

Going to test the new plugin.

lolodomo - by the way, is it possible to add UV sensor as well? Is there anything to help with? Some debugs may be...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 29, 2012, 08:24:02 am
Finally, I'm back home :)

Going to test the new plugin.

Good news.

Quote
lolodomo - by the way, is it possible to add UV sensor as well? Is there anything to help with? Some debugs may be...

It is possible, yes. But it is not my current priority.
First I would like to release a stable version before adding new things. You are one of the first concerned, I have to finish LightwaveRF support.


In the next alpha version that will be pushed probably tomorrow, I will add:
- event triggering for the barometer, rain and wind sensors
- setup page to select the units for temperature and speed
- setup page to adjust what protocols the RFXtrx is decoding
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 30, 2012, 04:40:05 pm
Ok :)

Just to confirm.

New plugin added temp (2 sensors) + humidity (2 sensors)

For some reason, rain and wind sensor devices are not added...

------------------------------------------------
1056021DEA000016000000000059000069
Packettype    = WIND
subtype       = WIND2 - WGR800
Sequence nbr  = 29
ID            = 59904
Direction     = 22 degrees
Average speed = 0 mtr/sec
Wind gust     = 0 mtr/sec
Signal level  = 6
Battery       = OK
------------------------------------------------
0B55021E99005C9900001469
Packettype    = RAIN
subtype       = RAIN2 - PCR800
Sequence nbr  = 30
ID            = 39168
Rain rate     = 237.05 mm/h
Total rain    = 20 mm
Signal level  = 6
Battery       = OK
------------------------------------------------
0957021F3F0000990059
Packettype    = UV
Subtype       = UV2 - UVN800
Sequence nbr  = 31
ID            = 16128
Level         = 0
Description = Low
Signal level  = 5
Battery       = OK

------------------------------------------------
0A520224250200E52B0159
Packettype    = TEMP_HUM
subtype       = TH2 - THGR810,THGN800
                channel 2
Sequence nbr  = 36
ID            = 9474
Temperature   = 22.9 °C
Humidity      = 43
Status        = Comfortable
Signal level  = 5
Battery       = OK



01   03/30/12 20:35:36.378   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 1B EA 00 00 16 00 00 00 00 00 69 00 00 79  <0x2df93680>
01   03/30/12 20:35:38.666   luup_log:20: RFXtrx: TH2/20993 temperature 20.2 humidity 47 % <0x2df93680>
01   03/30/12 20:35:38.666   luup_log:20: RFXtrx: Received command temperature=20.2;humidity=47 for 192 with ID TH2/20993 <0x2df93680>
01   03/30/12 20:35:38.669   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/20993 with value 20.2 <0x2df93680>
01   03/30/12 20:35:38.670   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/20993 with value 47 <0x2df93680>
01   03/30/12 20:35:40.118   luup_log:20: RFXtrx: Decoding not yet implemented for message 09 57 02 1D 3F 00 00 CA 2F 49  <0x2df93680>
01   03/30/12 20:35:41.826   luup_log:20: RFXtrx: TH2/9474 temperature 22.7 humidity 44 % <0x2df93680>
01   03/30/12 20:35:41.826   luup_log:20: RFXtrx: Received command temperature=22.7;humidity=44 for 192 with ID TH2/9474 <0x2df93680>
01   03/30/12 20:35:41.830   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/9474 with value 22.7 <0x2df93680>
01   03/30/12 20:35:41.831   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/9474 with value 44 <0x2df93680>
01   03/30/12 20:35:50.377   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 1F EA 00 00 16 00 00 00 00 00 69 00 00 79  <0x2df93680>
01   03/30/12 20:36:02.006   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 55 02 20 99 00 5C 99 00 00 14 79  <0x2df93680>
01   03/30/12 20:36:04.567   luup_log:20: RFXtrx: Decoding not yet implemented for message 0D 59 01 21 F0 00 5C 00 00 00 00 00 00 69  <0x2df93680>
01   03/30/12 20:36:18.384   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 22 EA 00 00 16 00 00 00 00 00 69 00 00 79  <0x2df93680>
01   03/30/12 20:36:20.916   luup_log:20: RFXtrx: LIGHTING5 message received 0A 14 00 23 00 B8 D8 01 01 00 60  <0x2df93680>
01   03/30/12 20:36:20.916   luup_log:20: RFXtrx: Received command 4 for 16 with ID L5.0/01 <0x2df93680>
01   03/30/12 20:36:20.917   luup_log:20: RFXtrx: SET STATUS from L5.0/01 with value 1 <0x2df93680>
01   03/30/12 20:36:30.596   luup_log:20: RFXtrx: LIGHTING5 message received 0A 14 00 24 00 B8 F1 01 01 00 50  <0x2df93680>
01   03/30/12 20:36:30.597   luup_log:20: RFXtrx: Received command 4 for 16 with ID L5.0/01 <0x2df93680>
01   03/30/12 20:36:30.597   luup_log:20: RFXtrx: SET STATUS from L5.0/01 with value 1 <0x2df93680>
01   03/30/12 20:36:31.676   luup_log:20: RFXtrx: TH2/20993 temperature 20.2 humidity 47 % <0x2df93680>
01   03/30/12 20:36:31.676   luup_log:20: RFXtrx: Received command temperature=20.2;humidity=47 for 192 with ID TH2/20993 <0x2df93680>
01   03/30/12 20:36:31.679   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/20993 with value 20.2 <0x2df93680>
01   03/30/12 20:36:31.680   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/20993 with value 47 <0x2df93680>
01   03/30/12 20:36:32.006   luup_log:20: RFXtrx: LIGHTING5 message received 0A 14 00 26 00 B8 F1 01 01 00 50  <0x2df93680>
01   03/30/12 20:36:32.006   luup_log:20: RFXtrx: Received command 4 for 16 with ID L5.0/01 <0x2df93680>
01   03/30/12 20:36:32.007   luup_log:20: RFXtrx: SET STATUS from L5.0/01 with value 1 <0x2df93680>
01   03/30/12 20:36:32.386   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 27 EA 00 00 16 00 00 00 00 00 69 00 00 79  <0x2df93680>
01   03/30/12 20:36:36.666   luup_log:20: RFXtrx: LIGHTING5 message received 0A 14 00 28 00 BA 5B 01 01 00 60  <0x2df93680>
01   03/30/12 20:36:36.666   luup_log:20: RFXtrx: Received command 4 for 16 with ID L5.0/01 <0x2df93680>
01   03/30/12 20:36:36.667   luup_log:20: RFXtrx: SET STATUS from L5.0/01 with value 1 <0x2df93680>
01   03/30/12 20:36:40.836   luup_log:20: RFXtrx: TH2/9474 temperature 22.7 humidity 44 % <0x2df93680>
01   03/30/12 20:36:40.837   luup_log:20: RFXtrx: Received command temperature=22.7;humidity=44 for 192 with ID TH2/9474 <0x2df93680>
01   03/30/12 20:36:40.840   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/9474 with value 22.7 <0x2df93680>
01   03/30/12 20:36:40.841   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/9474 with value 44 <0x2df93680>
01   03/30/12 20:36:42.554   luup_log:20: RFXtrx: LIGHTING5 message received 0A 14 00 2A 00 B9 95 01 01 00 50  <0x2df93680>
01   03/30/12 20:36:42.554   luup_log:20: RFXtrx: Received command 4 for 16 with ID L5.0/01 <0x2df93680>
01   03/30/12 20:36:42.555   luup_log:20: RFXtrx: SET STATUS from L5.0/01 with value 1 <0x2df93680>
01   03/30/12 20:36:43.386   luup_log:20: RFXtrx: LIGHTING5 message received 0A 14 00 2B 00 B9 95 01 01 00 50  <0x2df93680>
01   03/30/12 20:36:43.386   luup_log:20: RFXtrx: Received command 4 for 16 with ID L5.0/01 <0x2df93680>
01   03/30/12 20:36:43.387   luup_log:20: RFXtrx: SET STATUS from L5.0/01 with value 1 <0x2df93680>
01   03/30/12 20:36:46.388   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 2C EA 00 00 16 00 00 00 00 00 69 00 00 79  <0x2df93680>
01   03/30/12 20:36:49.276   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 55 02 2D 99 00 00 B1 00 00 16 79  <0x2df93680>
01   03/30/12 20:36:53.126   luup_log:20: RFXtrx: Decoding not yet implemented for message 09 57 02 2E 3F 00 00 B1 00 49  <0x2df93680>
01   03/30/12 20:37:00.394   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 2F EA 00 01 0E 00 00 00 10 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:37:04.497   luup_log:20: RFXtrx: Decoding not yet implemented for message 0D 59 01 30 F0 00 01 00 00 00 00 00 00 69  <0x2df93680>
01   03/30/12 20:37:14.466   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 31 EA 00 00 2D 00 00 00 0F 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:37:28.396   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 32 EA 00 00 43 00 0D 00 26 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:37:36.035   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 55 02 33 99 00 00 B1 00 00 16 79  <0x2df93680>
01   03/30/12 20:37:39.846   luup_log:20: RFXtrx: TH2/9474 temperature 22.8 humidity 44 % <0x2df93680>
01   03/30/12 20:37:39.846   luup_log:20: RFXtrx: Received command temperature=22.8;humidity=44 for 192 with ID TH2/9474 <0x2df93680>
01   03/30/12 20:37:39.849   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/9474 with value 22.8 <0x2df93680>
01   03/30/12 20:37:39.851   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/9474 with value 44 <0x2df93680>
01   03/30/12 20:37:42.398   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 35 EA 00 00 00 00 0D 00 24 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:37:56.398   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 36 EA 00 00 5A 00 0D 00 51 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:38:04.507   luup_log:20: RFXtrx: Decoding not yet implemented for message 0D 59 01 37 F0 00 00 00 00 00 00 00 00 69  <0x2df93680>
01   03/30/12 20:38:06.136   luup_log:20: RFXtrx: Decoding not yet implemented for message 09 57 02 38 3F 00 00 00 00 49  <0x2df93680>
01   03/30/12 20:38:10.405   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 39 EA 00 00 E1 00 0D 00 3A 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:38:17.686   luup_log:20: RFXtrx: TH2/20993 temperature 20.4 humidity 47 % <0x2df93680>
01   03/30/12 20:38:17.686   luup_log:20: RFXtrx: Received command temperature=20.4;humidity=47 for 192 with ID TH2/20993 <0x2df93680>
01   03/30/12 20:38:17.689   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/20993 with value 20.4 <0x2df93680>
01   03/30/12 20:38:17.691   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/20993 with value 47 <0x2df93680>
01   03/30/12 20:38:23.034   luup_log:20: RFXtrx: Decoding not yet implemented for message 0B 55 02 3B 99 00 5C 99 00 00 22 79  <0x2df93680>
01   03/30/12 20:38:24.478   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 3C EA 00 00 E1 00 20 00 00 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:38:38.408   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 3D EA 00 00 E1 00 20 00 00 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:38:38.856   luup_log:20: RFXtrx: TH2/9474 temperature 22.8 humidity 44 % <0x2df93680>
01   03/30/12 20:38:38.856   luup_log:20: RFXtrx: Received command temperature=22.8;humidity=44 for 192 with ID TH2/9474 <0x2df93680>
01   03/30/12 20:38:38.859   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/9474 with value 22.8 <0x2df93680>
01   03/30/12 20:38:38.860   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/9474 with value 44 <0x2df93680>
01   03/30/12 20:38:52.408   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 3F EA 00 00 E1 00 20 00 00 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:39:04.595   luup_log:20: RFXtrx: Decoding not yet implemented for message 0D 59 01 40 F0 00 00 00 00 00 00 00 00 69  <0x2df93680>
01   03/30/12 20:39:06.414   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 41 EA 00 00 E1 00 20 00 00 00 69 00 00 79  <0x2df93680>
01   03/30/12 20:39:10.696   luup_log:20: RFXtrx: TH2/20993 temperature 20.4 humidity 47 % <0x2df93680>
01   03/30/12 20:39:10.696   luup_log:20: RFXtrx: Received command temperature=20.4;humidity=47 for 192 with ID TH2/20993 <0x2df93680>
01   03/30/12 20:39:10.699   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/20993 with value 20.4 <0x2df93680>
01   03/30/12 20:39:10.700   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/20993 with value 47 <0x2df93680>
01   03/30/12 20:39:20.416   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 43 EA 00 00 E1 00 20 00 00 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:39:34.418   luup_log:20: RFXtrx: Decoding not yet implemented for message 10 56 02 44 EA 00 00 E1 00 00 00 00 00 69 00 00 69  <0x2df93680>
01   03/30/12 20:39:37.866   luup_log:20: RFXtrx: TH2/9474 temperature 22.8 humidity 44 % <0x2df93680>
01   03/30/12 20:39:37.866   luup_log:20: RFXtrx: Received command temperature=22.8;humidity=44 for 192 with ID TH2/9474 <0x2df93680>
01   03/30/12 20:39:37.869   luup_log:20: RFXtrx: SET CURRENTTEMPERATURE from TH2/9474 with value 22.8 <0x2df93680>
01   03/30/12 20:39:37.870   luup_log:20: RFXtrx: SET CURRENTLEVEL from TH2/9474 with value 44 <0x2df93680>
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 30, 2012, 04:52:31 pm
Regarding LWRF dimming... How to use it?

I deleted old device and created (automatically by the plugin) new one - only on / off buttons were added once again...

BTW, dimming works fine from the windows .exe application (Bert's new firmware is excellent)

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 30, 2012, 07:21:41 pm
Shapa, it looks like you are not using the last version. Some log messages are not yet present in my code and with the version you are using, decoding of wind and rain messages were not done.

Edit: I just checked the ZIP file attached and this is the correct lua file, not the one that lead to your logs. You might check that you have not two files, one named "L_RFXtrx.lua" and one named "L_RFXtrx.lua.lzo". If you are using UI5 v1.5.346, it is no more necessary to use WINSCP for the lua file, you can upload it like you do for the other files.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 30, 2012, 07:32:37 pm
Regarding LWRF dimming... How to use it?

I deleted old device and created (automatically by the plugin) new one - only on / off buttons were added once again...

BTW, dimming works fine from the windows .exe application (Bert's new firmware is excellent)

This is still tricky but the solution would be to use the dim button on your remote to first create the Vera device. Doing that, the plugin will create a dimmable light device.
When it will be correctly managed, I will have to change the kind of the device if the device is first created as a binary light device and then a dim command is received.

I will receive Chacon devices next week, so I think that LIGHTING1, LIGHTING2 and LIGHTING5 messages should be correctly managed in few days.

The version that will be released this week-end should already improved things.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 03:19:16 am
Sure, you are right.

For some reason, even with the latest UI5 firmware, still I need to use SCP to upload .lua file...

"Testing connection to: download2.mios.com ... OK

You are running the latest version: 1.5.346 ."

Rain and Wind sensors created successfully :)

Perfect!


50   03/31/12 7:20:31.081   luup_log:20: RFXtrx: W2/59904: cmds WIND Direction 225 WIND Set 0 WIND Gust 0 BatteryLevel 100 <0x2d8b9680>
50   03/31/12 7:20:41.880   luup_log:20: RFXtrx: R2/39168: cmds RAIN Set 34 RAIN RainRate 0 RAIN BatteryLevel 100 <0x2d8b9680>
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 03:31:58 am
LWRF is still confusing a bit :)

In case I'm trying to use remote control (on / off / dimming buttons are the same - short press or long press), the standart on / off device created

In case I'm trying to use master switch with pre-configure dimming levels, I see

02   03/31/12 7:29:46.320   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 0C F0 B9 83 10 04 00 60  <0x2ccb9680>
02   03/31/12 7:29:47.309   luup_log:20: RFXtrx: Lighting5 command not yet implemented: 4 <0x2ccb9680>
02   03/31/12 7:29:47.310   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 0D F0 B9 83 10 04 00 60  <0x2ccb9680>
02   03/31/12 7:29:48.409   luup_log:20: RFXtrx: Lighting5 command not yet implemented: 4 <0x2ccb9680>
02   03/31/12 7:29:48.410   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 0E F0 B9 83 10 04 00 60  <0x2ccb9680>
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 05:13:38 am
Sure, you are right.

For some reason, even with the latest UI5 firmware, still I need to use SCP to upload .lua file...

"Testing connection to: download2.mios.com ... OK

You are running the latest version: 1.5.346 ."

First delete the lua file. Then use the normal upload from the dashboard.

Quote
Rain and Wind sensors created successfully :)

Perfect!


50   03/31/12 7:20:31.081   luup_log:20: RFXtrx: W2/59904: cmds WIND Direction 225 WIND Set 0 WIND Gust 0 BatteryLevel 100 <0x2d8b9680>
50   03/31/12 7:20:41.880   luup_log:20: RFXtrx: R2/39168: cmds RAIN Set 34 RAIN RainRate 0 RAIN BatteryLevel 100 <0x2d8b9680>

Can you validate that the values are correct (the same as what is displaying on your sensor or meteo station) ?
PS: next version will display speed either in km/h or mph
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 05:22:57 am
LWRF is still confusing a bit :)

In case I'm trying to use remote control (on / off / dimming buttons are the same - short press or long press), the standart on / off device created

I will add a log message in the next version to understand what messages arrived. That would mean that a "ON" command is received before a "Set level" command. First we have to be sure that a "Set level" command is produced.

Quote
In case I'm trying to use master switch with pre-configure dimming levels, I see

02   03/31/12 7:29:46.320   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 0C F0 B9 83 10 04 00 60  <0x2ccb9680>
02   03/31/12 7:29:47.309   luup_log:20: RFXtrx: Lighting5 command not yet implemented: 4 <0x2ccb9680>
02   03/31/12 7:29:47.310   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 0D F0 B9 83 10 04 00 60  <0x2ccb9680>
02   03/31/12 7:29:48.409   luup_log:20: RFXtrx: Lighting5 command not yet implemented: 4 <0x2ccb9680>
02   03/31/12 7:29:48.410   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 0E F0 B9 83 10 04 00 60  <0x2ccb9680>

These commands are mood2 commands. Mood commands are not managed by my plugin.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 02:07:42 pm
Please find attached a new version (alpha 1).

What's new in this version:
- plugin version is displayed on the main device in the dashboard
- a new tab on the main device allows setting up the RFXtrx (defining what protocols are taken into account) and choosing the display unit for the tempratures and speeds
- no need to pair with the Vera now for LightwaveRF, Chacon, ...
- for ON/OFF/DIM commands (lighting), a device is created for each pair (remote, receiving device). That means, if you manage the same device with different remotes, several Vera devices will be created in the Vera. This si something that still needs to be enhanced.
- if a "set level" command is send (by a remote) while the Vera device is a binary light, the device will be converted to a dimmable light; then, you could dim from the Vera

Be carefull: Shapa and all others, this new version does not pair Vera with devices so I advice to use the previous version to unpair before installing this new version.

Please find the ZIP file attached to the first message in this topic.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 04:13:08 pm
lolodomo, thank you for the update.

I'm still thinking about "faking" remote control ID - is it good or not... Personally, I'd prefer to have some pairing process, but I could be wrong.

Anyway, the biggest issue is that a new device created for each pair (I've got multiple remotes assigned to multiple devices)

Going to try it now :)

p.s. I've got some idea. Ideally, the simulated LWRF ID should be WiFiLink device (official LWRF controller - quite cheap, 60 pounds only) - it is very easy to pair it with all devices... Virtually everyone who purchasing LWRF stuff normally buying this controller as well.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 04:29:11 pm
Still, only binary lights were created...

When I'm using remote, it is not sending "set level" command but I'm just pressing off or on and light level increasing / decreasing smoothly

Master switch has "mood" settings (stored dimming level), when I'm trying to switch levels a see in the logs:

02   03/31/12 20:26:13.419   luup_log:20: RFXtrx: Lighting5 command not yet implemented: 5 <0x2d9b3680>
02   03/31/12 20:26:13.419   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 15 F0 B9 83 10 05 00 60  <0x2d9b3680>
50   03/31/12 20:26:15.128   luup_log:20: RFXtrx: LIGHTING5 command: 5 <0x2d9b3680>
02   03/31/12 20:26:15.128   luup_log:20: RFXtrx: Lighting5 command not yet implemented: 5 <0x2d9b3680>
02   03/31/12 20:26:15.129   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 16 F0 B9 83 10 05 00 60  <0x2d9b3680>


Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 04:58:01 pm
When I'm using remote, it is not sending "set level" command but I'm just pressing off or on and light level increasing / decreasing smoothly

So, we have to ask Bert how to receive a "set level" command.

Quote
Master switch has "mood" settings (stored dimming level), when I'm trying to switch levels a see in the logs:

02   03/31/12 20:26:13.419   luup_log:20: RFXtrx: Lighting5 command not yet implemented: 5 <0x2d9b3680>
02   03/31/12 20:26:13.419   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 15 F0 B9 83 10 05 00 60  <0x2d9b3680>
50   03/31/12 20:26:15.128   luup_log:20: RFXtrx: LIGHTING5 command: 5 <0x2d9b3680>
02   03/31/12 20:26:15.128   luup_log:20: RFXtrx: Lighting5 command not yet implemented: 5 <0x2d9b3680>
02   03/31/12 20:26:15.129   luup_log:20: RFXtrx: Decoding not yet implemented for message 0A 14 00 16 F0 B9 83 10 05 00 60  <0x2d9b3680>

Once again, mood is not managed by my plugin. What should be the expected result when I receive this message ? What kind of device to use ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 05:10:27 pm
lolodomo, thank you for the update.

I'm still thinking about "faking" remote control ID - is it good or not... Personally, I'd prefer to have some pairing process, but I could be wrong.

The two choces will be possible when my implementation will be finished.
A specific UI (new tab in the main device) is required to create devices.

Quote
Anyway, the biggest issue is that a new device created for each pair (I've got multiple remotes assigned to multiple devices)

I will offer the possibility to set different pairs in a variable of the device.
Imagine you have a first device with pair 121213/01 stored in the variable and a second device with pair 434445/05 in the variable, the idea is that you can manually put the value 121213/01,434445/05 in the variable of the first device and then delete the second device which is no more required. Then all commands received from 121213/01 or 434445/05 will impact the same device.
I can do that quickly, almost everything is already in place.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 05:24:28 pm
Mood is mostly usable for lights - set dim level...

The "mood" idea is simple.
When some mood is configured (long press on the master control button) - all paired (with this master control) devices are storing their current settings as "mood-N" (at least 5 mood levels are allowed)

Next time I press the same button - all devices are restoring their stored settings (on / off / dimming level)

In fact, moods itself are easily replaceable by Vera scenes and not really that important.

The big question is how to understand device functionality - is it dimmable or not... Finally, may be some configuration flag is the easiest way? To create device as binary light by default and than to reconfigure in case of dimming flag set to "1" for example... The same for inline relays (flag "relay" enabled in the advanced tab?)

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 05:30:22 pm
"Imagine you have a first device with pair 121213/01 stored in the variable and a second device with pair 434445/05 in the variable, the idea is that you can manually put the value 121213/01,434445/05"

Yes, it should work. A bit complicated for average user, but still not a rocket science.

One question... Isn't it possible just to filter ID's automatically? I.e. when some new pair (remote->device) detected, is it possible to understand that receiving device is already exists and add remote control ID to the variable automatically?

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 05:54:17 pm
"Imagine you have a first device with pair 121213/01 stored in the variable and a second device with pair 434445/05 in the variable, the idea is that you can manually put the value 121213/01,434445/05"

Yes, it should work. A bit complicated for average user, but still not a rocket science.

Yes, I agree.

Quote
One question... Isn't it possible just to filter ID's automatically? I.e. when some new pair (remote->device) detected, is it possible to understand that receiving device is already exists and add remote control ID to the variable automatically?

My initial idea was to consider the unit code as identifier of the device. But first this will be partially incorrect as you can have more than 16 physical devices. And second, I have now understood that the unit code is not attached to a physical LightwaveRF receiver device, but something attached to the remote/controller. One remote can use its ID + unit code 01 (button 1 for example) and another can use its ID + unit code 02 (button 2) to control the same physical device.
So I don't see how I can have something that can be automatic.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 06:13:21 pm
Mood is mostly usable for lights - set dim level...

The "mood" idea is simple.
When some mood is configured (long press on the master control button) - all paired (with this master control) devices are storing their current settings as "mood-N" (at least 5 mood levels are allowed)

Next time I press the same button - all devices are restoring their stored settings (on / off / dimming level)

In fact, moods itself are easily replaceable by Vera scenes and not really that important.

Specific devices for LightwaveRF would be necessary that will add buttons "Mood1", ... "Mood5".

Quote
The big question is how to understand device functionality - is it dimmable or not... Finally, may be some configuration flag is the easiest way? To create device as binary light by default and than to reconfigure in case of dimming flag set to "1" for example... The same for inline relays (flag "relay" enabled in the advanced tab?)

As I understood, inline relay is using only specific commands (open, close and stop) so it is easy to identify it.
For binary light and dimmable light, what I have implemented is an automatic convertion from binary light to dimmable light when a "set level" command is received.
So, this time, I think the kind of device can be managed automatically by the plugin.
The question is now: how to produce a "set level" command as you don't succeed in.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 06:21:14 pm
The only way to send (officially) "set level" command is to use WiFiLink device.

p.s. once again, you are right. when I sent "dim level" command from a WiFiLink, Vera instantly added new device (RFX dim Light L5.0/30568....) and it is working fine (on / off / dimming levels). perfecto! :)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 06:33:44 pm
The only way to send (officially) "set level" command is to use WiFiLink device.

p.s. once again, you are right. when I sent "dim level" command from a WiFiLink, Vera instantly added new device (RFX dim Light L5.0/30568....) and it is working fine (on / off / dimming levels). perfecto! :)

Happy to read that :)

For the dimmable light device, when you push the ON button, the sent command is a "set level 100%", not a ON command. Same thing for the OFF button (set level 0% instad of OFF).
I dont't know if it is important or not. But this could be changed easily if necessary.
PS: for LightwaveRF, 32 levels are possible.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 06:43:16 pm
I really don't know too much about the internals, but all native remotes are sending on / off commands but not 0% and 100% - it could be made for compatibility with different (including non-dimmable) devices...

The additional reason why - in case of dimming device, "on" command restoring the same dimming level which was set before switching off (by sending "off" command).

Probably, it is safer to do the same - send real on and off commands... Is it  possible to remember dimming level before sending "off" (for consistent status?) and restore it when "on" is send?

From the other hand, in case a device is switched off and "set level" command sent - everything is OK and it switching on with required brightness level...




Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on March 31, 2012, 07:14:32 pm
What's happening when you set the level at any level and then send a OFF command through your remote ? Is the Vera device updated ? My feeling is that it is not updated because ON/OFF commands impacts only binary lights in my code.
Please try and if it is not working I will try to find a solution.

Storing the dim level and restoring it after external OFF and then ON commands is doable.
But I cannot distinguish with the dimmable light device whether you wish to set level to 0 or set the light off. So difficult to know if I must store the old dim level or not. Same thing for ON button that is identical to a set level to 100%, so I will not be able to choose between setting the light level to 100% or restore the previously saved dim level.
So I propose that ON and OFF commands from the Vera remain set level commands to 100% and 0%. And OFF and ON commands received from outside will store the previous dim level and restore it.
Is it ok for you ?

Edit: what happens with your external devices if you set level to 0% then off light and then on light ? What is the level ?

And for inline relay, can you check that ON/OFF commands have no effect using RFXCOM test application ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on March 31, 2012, 07:29:30 pm
For sure, the status is not updated for dimming device (but updated for binary device which is created automatically for remote->dimmer pair)

Regarding to distinguish - once again, in case some dimming level is configured, when I switching off and then switching on - dimming level is still the same.

But, it looks like "0%" and "off" are virtually the same, as when I'm sending "on" from a remote (after I switched off dimmer from a Vera), the dimming level is restored correctly (exactly the same level it was before switching off)

Probably, only "on" command should be sent as "on" but not "100%" - to restore previous dimming level...

"And for inline relay, can you check that ON/OFF commands have no effect using RFXCOM test application" - AFAIR, on / off are exactly the same for inline relays (on = open, off = close) (but stop is additional command), but I could be wrong (I tested that to help Bert to add inline relay support to the firmware 3 weeks ago :) )
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 01, 2012, 04:26:00 am
For sure, the status is not updated for dimming device (but updated for binary device which is created automatically for remote->dimmer pair)

Regarding to distinguish - once again, in case some dimming level is configured, when I switching off and then switching on - dimming level is still the same.

But, it looks like "0%" and "off" are virtually the same, as when I'm sending "on" from a remote (after I switched off dimmer from a Vera), the dimming level is restored correctly (exactly the same level it was before switching off)

Probably, only "on" command should be sent as "on" but not "100%" - to restore previous dimming level...

"And for inline relay, can you check that ON/OFF commands have no effect using RFXCOM test application" - AFAIR, on / off are exactly the same for inline relays (on = open, off = close) (but stop is additional command), but I could be wrong (I tested that to help Bert to add inline relay support to the firmware 3 weeks ago :) )

That would mean if ON is first used for a window covering, I will create a binary light. So I have to consider a new conversion from binary light to window covering.
And ON/OFF commands received from remotes should have different behaviour, depending on the device type (binary light, dimmable light or window covering).

For mood, I think I know how to manage it now. I will create a new tab for LightwaveRF in the main device and add five buttons in this tab: "Mood 1", "Mood 2", "Mood 3", "Mood 4" and "Mood 5". And pairs for these commands will be stored in variables. So you will have to run the command from your external controller a first time and then it will work from the Vera.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 01, 2012, 06:33:43 am
FYI (just tried inline relay - by pressing open / close / stop buttons)

Everything is fine,  relay is working good. The only question may be to "clean" UI (custom device?) - remove unnecessary buttons...
I'll try to add Z-Wave (fibaro) inline relay which is officially supported (bought one) to look at - which device is created by Vera


01   04/01/12 11:31:00.102   luup_log:20: RFXtrx: Unexpected device id WC/C5.0/04. Up command not sent <0x2ba01680>
50   04/01/12 11:31:00.103   luup_log:20: RFXtrx: windowCovering Up WC/C5.0/04 <0x2ba01680>
01   04/01/12 11:31:00.104   luup_log:20: RFXtrx: Unexpected device id WC/C5.0/04. Up command not sent <0x2ba01680>
50   04/01/12 11:31:02.101   luup_log:20: RFXtrx: windowCovering Stop WC/C5.0/04 <0x2ba01680>
01   04/01/12 11:31:02.101   luup_log:20: RFXtrx: Unexpected device id WC/C5.0/04. Stop command not sent <0x2ba01680>
50   04/01/12 11:31:05.275   luup_log:20: RFXtrx: W2/59904: cmds WIND Direction 315 WIND Set 3 WIND Gust 0 BatteryLevel 100 <0x2d201680>
50   04/01/12 11:31:07.333   luup_log:20: RFXtrx: TH2/20993: cmds TEMP Set 14.6 HUM Set 37 BatteryLevel 100 <0x2d201680>
50   04/01/12 11:31:09.733   luup_log:20: RFXtrx: TH2/9474: cmds TEMP Set 22.1 HUM Set 34 BatteryLevel 100 <0x2d201680>
50   04/01/12 11:31:19.214   luup_log:20: RFXtrx: W2/59904: cmds WIND Direction 22 WIND Set 3 WIND Gust 2 BatteryLevel 100 <0x2d201680>
50   04/01/12 11:31:23.730   luup_log:20: RFXtrx: LIGHTING5 command: 15 <0x2d201680>
50   04/01/12 11:31:23.731   luup_log:20: RFXtrx: L5.0/F3656D/01 remote F3656D/01: cmds COVER Open  <0x2d201680>
50   04/01/12 11:31:23.732   luup_log:20: RFXtrx: device not found and autocreate enabled... <0x2d201680>
50   04/01/12 11:31:23.734   luup_log:20: RFXtrx: Tree buildup, now add L5.0/F3656D/01 <0x2d201680>
50   04/01/12 11:31:23.734   luup_log:20: RFXtrx: Creating child device id WC/L5.0/F3656D/01 of type urn:schemas-micasaverde-com:device:WindowCovering:1 <0x2d201680>
....
....

50   04/01/12 11:39:10.532   luup_log:20: RFXtrx: windowCovering Up WC/L5.0/F3656D/01 <0x2e001680>
50   04/01/12 11:39:10.533   luup_log:20: RFXtrx: Sending command: 0A 14 00 09 F3 65 6D 01 0F 00 00  <0x2e001680>
50   04/01/12 11:39:11.041   luup_log:20: RFXtrx: L5.0/F3656D/01 remote F3656D/01: cmds COVER Open  <0x2cc01680>
50   04/01/12 11:39:14.297   luup_log:20: RFXtrx: windowCovering Stop WC/L5.0/F3656D/01 <0x2e228680>
50   04/01/12 11:39:14.298   luup_log:20: RFXtrx: Sending command: 0A 14 00 0A F3 65 6D 01 0E 00 00  <0x2e228680>
50   04/01/12 11:39:14.800   luup_log:20: RFXtrx: L5.0/F3656D/01 remote F3656D/01: cmds COVER Stop  <0x2cc01680>
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 01, 2012, 09:13:49 am
01   04/01/12 11:31:00.102   luup_log:20: RFXtrx: Unexpected device id WC/C5.0/04. Up command not sent <0x2ba01680>
50   04/01/12 11:31:00.103   luup_log:20: RFXtrx: windowCovering Up WC/C5.0/04 <0x2ba01680>
01   04/01/12 11:31:00.104   luup_log:20: RFXtrx: Unexpected device id WC/C5.0/04. Up command not sent <0x2ba01680>
50   04/01/12 11:31:02.101   luup_log:20: RFXtrx: windowCovering Stop WC/C5.0/04 <0x2ba01680>
01   04/01/12 11:31:02.101   luup_log:20: RFXtrx: Unexpected device id WC/C5.0/04. Stop command not sent <0x2ba01680>

This was certainly due to old devices. I changed the id in the last version.


I have now added mood feature. Enjoy ;D I will release later today.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 01, 2012, 09:18:04 am
Everything is fine,  relay is working good. The only question may be to "clean" UI (custom device?) - remove unnecessary buttons...

You need only UP DOWX and STOP buttons ?
I can make a specific device, deleting unnecessary buttons.

Quote
I'll try to add Z-Wave (fibaro) inline relay which is officially supported (bought one) to look at - which device is created by Vera

Fibaro will use the default window covering device like I do.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 01, 2012, 06:39:31 pm
"You need only UP DOWX and STOP buttons ?"

exactly, just to avoid any confusion for other users :)

Probably, on / off / stop should be used (exactly as per official manual) and no "level bar" at all - just three buttons.

BTW, there are some new inline relays are coming (with more features)...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 04, 2012, 04:13:55 pm
Hi

Sorry if I'm not patient enough, but are there any news? :)

I'm really dreaming about to switch finally all my LWRF stuff to Vera using your plugin and RFXcom device  :)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 05, 2012, 04:12:12 am
Hi

Sorry if I'm not patient enough, but are there any news? :)

I'm really dreaming about to switch finally all my LWRF stuff to Vera using your plugin and RFXcom device  :)

Work in progress.
I want to add the device creation from the UI before attaching a new version.
And I am waiting for Chacon devices I will have to test first.
Next version could be at end of week or beginning of next week, depending on my other activities.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 05, 2012, 04:27:33 am
Sure, take you time :)

You've made great progress already...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 06, 2012, 08:28:00 pm
lolodomo,

One small correction... Just installed Fibaro inline relay (zwave) - it is not a window covering device :)

Screenshots are attached...

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 07, 2012, 03:50:31 am
Which Fiibaro model ? FGR221 ? FGS211 ? FGS221 ?
What is the usage of each of the 3 switchs ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jltaziaux on April 07, 2012, 12:46:30 pm
hello,

can you tell me where I can load the plugin RFXtrx?
a big thank you
jl
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 07, 2012, 02:45:41 pm
hello,

can you tell me where I can load the plugin RFXtrx?
a big thank you
jl

It was present in the previous page. It is now attached in the first message of the topic.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 07, 2012, 02:50:41 pm
Which Fiibaro model ? FGR221 ? FGS211 ? FGS221 ?
What is the usage of each of the 3 switchs ?

I received this morning one Fibaro for roller shutter. I will be able to check what device(s) are created by Micasaverde.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 07, 2012, 04:37:38 pm
lolodomo,

one device is parent (global) and two others - slaves (it is the version with 1.5kW x 2)

Probably, shutter should be detected as window covering device as it should support "stop" command

For my relay only on / off are supported and shown (which is right)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 09, 2012, 09:33:08 am
Hi Shapa.
As I understood, you are using one inline relay device to manage a window covering (or a roller shutter or a curtain). Can you check please with the RFXCOM tool if command "Open" is to be used to up the window covering or to down it ?
I have a big doubt because there is place for confusion...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 09, 2012, 05:48:56 pm
Plugin in version alpha 2 dated 9th of April is attached to the first message of this topic.

What's new in version alpha 2:
- you can now create manually switch device, dimmable light device and window covering device using a new tab
- Harrison curtain is now managed (device creation + Open/Stop/Close commands)
- For LightwaveRF, a new tab includes 5 mood buttons (the command must have been received first one time; then it can be send by the Vera/RFXtrx)
- conversion of device between binary light device, dimmalbe light device and window covering device  is done automatically by the plugin depending on the received messages, or can be done manually by the user using the new tab (buttons "add xxx")
- you can now associate several devices using the "Association" variable. This is interesting when you have several controllers for one receiving device. One device for each controller will be automatically created by the plugin but then you can keep only one device and put the "id" of each others in the "Assocation" variable of the remaining device. The different "id" must be separated by comma. The "id" must be the altid minus the 3 first characters (suppress the "LS/" or "DL/" or "WC/"). Then, commands coming from different controllers will impact one unique device.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on April 10, 2012, 08:18:27 pm
Hi Lolodomo,

Nice job.
I've started updating your code to include x10 security Door Sensor and Motion sensor. I've pretty much decoded all the incoming message, expanding with new decode function, new association.
One first question, it seems you're not gathering signal level in your code, is this because it is not relevant into the Vera(lite) or does it worth decoding it and pushing it to the Vera ?

Second question, once decoded, your code tries to create childs, but it crashed the LuaUpnp as it does not seems to find proper description for those devices. Which is ok as long as you have and I have not implemented. Any recommendation on how to create those descriptions ? Should we use standard xml/json from the vera or create or own ?

Chris
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 11, 2012, 01:22:03 am
Wow, nice job :)

Going to return back home today and for sure will try to test the pluging ASAP :)

Do you have some expatiation about when more than 16 devices will be supported? :)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 11, 2012, 05:15:34 am
Do you have some expatiation about when more than 16 devices will be supported? :)

I forget to mention it, but there is now no limit.
(I think it was already the case in the previous version)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 11, 2012, 05:38:32 am
Hi Lolodomo,

Nice job.
I've started updating your code to include x10 security Door Sensor and Motion sensor. I've pretty much decoded all the incoming message, expanding with new decode function, new association.
One first question, it seems you're not gathering signal level in your code, is this because it is not relevant into the Vera(lite) or does it worth decoding it and pushing it to the Vera ?

The signal level could be added on each device using a new variable, like it is for the battery level. But at my knowledge, no standard variable is defined to store that information.
And in my point of view, this is not an information that requires to be stored frequently as it will not change.

Quote
Second question, once decoded, your code tries to create childs, but it crashed the LuaUpnp as it does not seems to find proper description for those devices. Which is ok as long as you have and I have not implemented. Any recommendation on how to create those descriptions ?

Note that after each child creation, the Lua engine is reloaded, it is normal, not a crash.
If you have a crash, it is certainly because something is wrong in your code and because I forgot some checks in my code.
You probably use standard door and motion sensors. So you need:
- to add an entry in the table tableDeviceTypes for each type you will use. Motion sensor and door sensor types are already present, so I think you have nothing to add.
- define new commands in the table tableCommands; they are the commands that you will assign in your new decoding function. The second argument of the new entries will be either "DOOR" or "MOTION". The third argument will be the variable that you want to update and that is the key in the table tabVars (it can be nil if you don't need to to update variable)
- define each new variable you want to update in the table tabVars

Edit: keep in mind that the device ID must be unique. Try to keep a coherence in ID naming with what I have already done. It could be something like "S<subtype>/<id>"; "S" for "security" and "id" would be in hexadecimal

Quote
Should we use standard xml/json from the vera or create or own ?

Standard when they exist. They already exist for motion and door sensors.


Please start your updates from the last version I released (they were many changes). And send me your changes when it is working, I will do the merge.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 11, 2012, 07:02:20 am
That's perfect for me if Chris takes the X10 security part.

My updated TODO list is now:
1 - finish barometer, rain and wind devices - events management
2 - create a new device that will have 3 commands; open, close and stop. A new plugin option will then allow choosing between the standard window covering device and this new one
3 - handle messages from UV sensors and define a new UV device
4 - handle messages from CM119/160 enerygy usage sensors
5 - upload files to code.mios.com and create a description/help page
6 - release a first version to have the plugin available in the app store
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 11, 2012, 07:34:48 am
Here is a summary of what RFXtrx messages are implemented by the plugin:

* Lighting1 (X10 lighting, ARC, ELRO AB400D, Waveman, Chacon EMW200, IMPULS): partially implemented
----- On and Off commands are implemented
----- Dim and Bright commands for X10 are not yet implemented
----- All/group Off and All/group On commands for X10, ARC and  Chacon EMW200 are not yet implemented
----- Chime command for ARC is not yet implemented

* Lighting2 (AC, HomeEasy EU, ANSLUT): partially implemented
----- On, Off and Set level commands are implemented
----- group Off, group On and Set group level are not yet implemented

* Lighting3 (Koppla): not yet implemented

* Lighting4 (PT2262): not yet implemented

* Lighting5 (LightwaveRF): partially implemented
----- On, Off, mood1, mood2, mood3, mood4, mood5, close, stop, open and set level commands are implemented
----- group Off, unlock, lock and all lock commands are not yet implemented

* Curtain1 (Harrison): partially implemented
----- Open, Close and Stop commands are implemented
----- Program command is not yet implemented

* Security1 (X10, KD101, Visonic): not yet implemented

* Camera1 (X10 Ninja/Robocam): not yet implemented

* Remote control and IR (ATI, Medion, PC Remote): not yet implemented

* Thermostat1 (Digimax): not yet implemented

* Thermostat2 (HomeEasy HE105, RTS10): not yet implemented

* Thermostat3 (Mertik-Maxitrol G6R-H4T1 / G6R-H4TB): not yet implemented

* Temperature sensors (THR128/138, THC138, THC238/268, THN132, THWR288, THRN122, THN122, AW129/131, THWR800, RTHN318, La Crosse TX3, TX4, TX17): implemented

* Humidity sensors (LaCrosse TX3): implemented

* Temperature and humidity sensors (THGN122/123, THGN132, THGR122/228/238/268, THGR810, THGN800, RTGR328, THGR328, WTGR800, THGR918, THGRN228, THGN500, TFA TS34C, Cresta, WT450H): implemented

* Barometric sensors: implemented

* Temperature, humidity and barometric sensors (BTHR918, BTHR918N, BTHR968): implemented

* Rain sensors (RGR126/682/918, PCR800, TFA): implemented

* Wind sensors (WTGR800, WGR800, STR918, WGR918, TFA): implemented

* UV sensors (UVN128, UV138, UVN800, TFA): not yet implemented

* Date/time sensors (RTGR328N): not yet implemented

* Current sensors (CM113, Electrisave): not yet implemented

* Energy usage sensors (CM119/160): not yet implemented

* Weighting scale (WEIGHT1-WEIGHT2): not yet implemented

* RFXsensor: not yet implemented

* RFXMeter: not yet implemented
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: gibbo on April 11, 2012, 08:57:55 am
Hi,

this looks good so far!

I've just ordered some of the bits to start playing with this!  should be here sometime next week...

Thanks for all your time and effort! :)

Ian
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 11, 2012, 09:32:37 am
Shapa, any idea of what is exactly the "group off" command for LightwaveRF ?
What "group" means for LightwaveRF ?
Is it a button on a remote ? Is group all devices driven by a remote ?
Why a group off command and no group on command ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on April 11, 2012, 06:36:09 pm
Hi lolodomo,

still porting on your lastest code release.
Got all messages regarding security on Door and Motion sensors identified, finishing the code to get battery level.
I've removed part related to Signal Strength based on your comment.
Still need to process command sent to the devices.

Got a bug in my code regarding Door Sensor and Motion Sensor both detected as Door Sensors. Need to find out why  ??? :'(

Alos I've gone through Motion Sensor and Door Sensor, those are too simple from my point of view, compared to what exist on other boxes (based on a discussion with Bert). We might start buy this one, but we might move to something more complete later  :D
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 12, 2012, 05:32:18 am
lolodomo - overall, everything is working fine. Thank you very much!

System already is fully usable

One small suggestion - is it possible to put "convert" tab in the device itself as well?

For now, in case of manual device conversion (binary->dimmer for example), I'm going to the device properties, copying something like "F0C98B/01", than going to the master RFX device, entering manually this info... It could be extremely easier to put such tab (in case it is possible) to the device itself (just one click :) )

The same idea could be useful to "join" devices - may be it is possible to provide "link" tab to choose already exist device to combine together and automatically delete unnecessary one.

Regarding groups - I'm pretty confused, as I never seen any real usage for them... Yes, it is possible to bind multiple devices on the same button on a remote for example... And to switch them off / on simultaneously... But I'm not really sure we are talking about groups

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 12, 2012, 06:20:03 am
lolodomo - overall, everything is working fine. Thank you very much!

System already is fully usable

Did you try everything relative to LightwaveRF ? on/off commands, dim level, inline relay commands, mood, manual device creation, manual device conversion, association of devices, ... ?

Quote
One small suggestion - is it possible to put "convert" tab in the device itself as well?

For now, in case of manual device conversion (binary->dimmer for example), I'm going to the device properties, copying something like "F0C98B/01", than going to the master RFX device, entering manually this info... It could be extremely easier to put such tab (in case it is possible) to the device itself (just one click :) )

The same idea could be useful to "join" devices - may be it is possible to provide "link" tab to choose already exist device to combine together and automatically delete unnecessary one.

That would be doable, but one time again it would require to define new devices instead of using standard devices. That would work with the Micasaverde Web UI but these devices would not be recognized by other applications (like iPhone or Android applications). So this is probably something to avoid.
And what we are talking about is mainly something to be done one time at init time when setting up the system, not something used very often.
By the way, I could probably enhance the UI on the master device using JavaScript.

Quote
Regarding groups - I'm pretty confused, as I never seen any real usage for them... Yes, it is possible to bind multiple devices on the same button on a remote for example... And to switch them off / on simultaneously... But I'm not really sure we are talking about groups

No, that is probably something else. That's something to ask to Bert as he included the command "group off" in his interface.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 12, 2012, 09:32:12 am
I'm not tried:

mood settings (as mood is normally used for room in terms of LWRF, but plugin has only global mood settings)
manual device creation (it is really hard to get info about a new device as they are not announcing anything)

conversion is working ok
on / off / dim / inline working as well

going to try association today

regarding conversion - for sure, it is better to leave compatibility and it is not really important - it is usable and stable in the current way
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on April 12, 2012, 05:48:55 pm
lolodomo,

I don't know if you want to do this in private chat or if it can help other to build further support into your plugin, but I've got several question on your code, some are probably obvious to plugin developer, some other for lua expert, I'm not any, just a regular developer willing to increase the Woman Acceptance Factor by reusing x10 security items inherited from the previous house owner, before I'm autorized to buy any further zwave  ;D ;D

1/ it seems that there is a code to automatically detect any device through the RFX433 (decodeXXX functions), and another piece to create manually the device (addXX functions). Correct ?
2/ At the end both are triggering a method which is creating the child. Correct ?
3/ Is there any method to actually remove created childs ? out of removing the RFX433 device itself from the vera , I mean  :)
4/ Typically, I've got devices of the same type, with two different subtypes. One decode function or two ? I went for two so far, but I don't know if I missed any design point
5/ TableCommands structure can you explain why some fields are at nil ?
6/ it seems that i corrected my bug regarding Motion Sensor being identified as a Door Sensor. But the Motion Sensor does not seem counted once but then disapear even if listed:

Code: [Select]
50 04/13/12 0:40:36.356 luup_log:34: RFXtrx: Decode x10securityMS: altid=x10sec.MS/AAA593 CMD= <0x2e6cb680>
50 04/13/12 0:40:36.356 luup_log:34: RFXtrx: Decode x10securityMS: altid=x10sec.MS/AAA593 CMD=Motion Battery lvl=89 <0x2e6cb680>
50 04/13/12 0:40:36.356 luup_log:34: RFXtrx: x10sec.MS/AAA593: cmds Motion  <0x2e6cb680>
50 04/13/12 0:40:36.358 luup_log:34: RFXtrx: device not found and autocreate enabled... <0x2e6cb680>
50 04/13/12 0:40:36.359 luup_log:34: RFXtrx: Creating child device id MS/x10sec.MS/AAA593 of type uurn:schemas-micasaverde-com:device:MotionSensor:1 <0x2e6cb680>
50 04/13/12 0:40:36.360 luup_log:34: RFXtrx: Tree with number child devices: 10 <0x2e6cb680>
50 04/13/12 0:40:36.360 luup_log:34: RFXtrx:        door sensors: 2 <0x2e6cb680>
50 04/13/12 0:40:36.361 luup_log:34: RFXtrx:      motion sensors: 1 <0x2e6cb680>

luup_log:34: RFXtrx: Found child device id HS/TH1/47873 of type urn:schemas-micasaverde-com:device:HumiditySensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.269 luup_log:34: RFXtrx: Found child device id TS/TH1/22530 of type urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.269 luup_log:34: RFXtrx: Found child device id TS/T2/30721 of type urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.270 luup_log:34: RFXtrx: Found child device id DS/x10sec.DS/07082A of type urn:schemas-micasaverde-com:device:DoorSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.270 luup_log:34: RFXtrx: Found child device id DS/x10sec.DS/9E91EB of type urn:schemas-micasaverde-com:device:DoorSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.271 luup_log:34: RFXtrx: Found child device id TS/TH1/47873 of type urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.271 luup_log:34: RFXtrx: Found child device id TS/TH1/28676 of type urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.272 luup_log:34: RFXtrx: Found child device id MS/x10sec.MS/AAA593 of type urn:schemas-micasaverde-com:device:MotionSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.273 luup_log:34: RFXtrx: Found child device id HS/TH1/28676 of type urn:schemas-micasaverde-com:device:HumiditySensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.273 luup_log:34: RFXtrx: Found child device id HS/TH1/22530 of type urn:schemas-micasaverde-com:device:HumiditySensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.274 luup_log:34: RFXtrx: Tree with number child devices: 9 <0x2b4a5680>
50 04/13/12 0:40:55.274 luup_log:34: RFXtrx:        door sensors: 2 <0x2b4a5680>
50 04/13/12 0:40:55.274 luup_log:34: RFXtrx:      motion sensors: 0 <0x2b4a5680>
50 04/13/12 0:40:55.275 luup_log:34: RFXtrx:      light switches: 0 <0x2b4a5680>
50 04/13/12 0:40:55.275 luup_log:34: RFXtrx:  dim light switches: 0 <0x2b4a5680>
50 04/13/12 0:40:55.275 luup_log:34: RFXtrx:     window covering: 0 <0x2b4a5680>
50 04/13/12 0:40:55.276 luup_log:34: RFXtrx: temperature sensors: 4 <0x2b4a5680>
50 04/13/12 0:40:55.276 luup_log:34: RFXtrx:    humidity sensors: 3 <0x2b4a5680>
50 04/13/12 0:40:55.276 luup_log:34: RFXtrx:  barometric sensors: 0 <0x2b4a5680>
50 04/13/12 0:40:55.276 luup_log:34: RFXtrx:        wind sensors: 0 <0x2b4a5680>
50 04/13/12 0:40:55.277 luup_log:34: RFXtrx:        rain sensors: 0 <0x2b4a5680>

Chris
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 13, 2012, 05:42:54 am
I'm not any, just a regular developer willing to increase the Woman Acceptance Factor by reusing x10 security items inherited from the previous house owner, before I'm autorized to buy any further zwave  ;D ;D

That's easy, you told her: "Sorry, my dear, I tried but I did not succeed" ;D ;D

Quote
1/ it seems that there is a code to automatically detect any device through the RFX433 (decodeXXX functions), and another piece to create manually the device (addXX functions). Correct ?

Correct but addXXX functions are not required for all devices. For X10 security, I think automatic creation through decodeXXX functions is sufficient.
addXXX functions are for manual creation and require to define special UI.

Quote
2/ At the end both are triggering a method which is creating the child. Correct ?

Correct.

Quote
3/ Is there any method to actually remove created childs ? out of removing the RFX433 device itself from the vera , I mean  :)

No code is needed to remove child, you can do it through the UI, exactly the same way you do it for any device.

Quote
4/ Typically, I've got devices of the same type, with two different subtypes. One decode function or two ? I went for two so far, but I don't know if I missed any design point

You must define a decoding function for each couple (tyoe, subtype) but then you can define the same decoding function for several subtypes.
You have to define an entry in the table tableMsgTypes for each type/subtype and then assign the decoding function in the function initDecodingFunctions.

Quote
5/ TableCommands structure can you explain why some fields are at nil ?

The second field is nil in two cases:
- when the command is attached to the master device (lightwaveRF mood commands)
- when the command can concern every device (battery level)
Except in very particular cases, this field must be set.

The third field is nil in two cases:
- when the command does not require to update a variable on the child device
- when the command requires to update several variables on the child device; this is the case for the battery (battery level + battery update date); this case requires to update the generic code :-\

Quote
6/ it seems that i corrected my bug regarding Motion Sensor being identified as a Door Sensor. But the Motion Sensor does not seem counted once but then disapear even if listed:

Code: [Select]
50 04/13/12 0:40:36.356 luup_log:34: RFXtrx: Decode x10securityMS: altid=x10sec.MS/AAA593 CMD= <0x2e6cb680>
50 04/13/12 0:40:36.356 luup_log:34: RFXtrx: Decode x10securityMS: altid=x10sec.MS/AAA593 CMD=Motion Battery lvl=89 <0x2e6cb680>
50 04/13/12 0:40:36.356 luup_log:34: RFXtrx: x10sec.MS/AAA593: cmds Motion  <0x2e6cb680>
50 04/13/12 0:40:36.358 luup_log:34: RFXtrx: device not found and autocreate enabled... <0x2e6cb680>
50 04/13/12 0:40:36.359 luup_log:34: RFXtrx: Creating child device id MS/x10sec.MS/AAA593 of type uurn:schemas-micasaverde-com:device:MotionSensor:1 <0x2e6cb680>
50 04/13/12 0:40:36.360 luup_log:34: RFXtrx: Tree with number child devices: 10 <0x2e6cb680>
50 04/13/12 0:40:36.360 luup_log:34: RFXtrx:        door sensors: 2 <0x2e6cb680>
50 04/13/12 0:40:36.361 luup_log:34: RFXtrx:      motion sensors: 1 <0x2e6cb680>

luup_log:34: RFXtrx: Found child device id HS/TH1/47873 of type urn:schemas-micasaverde-com:device:HumiditySensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.269 luup_log:34: RFXtrx: Found child device id TS/TH1/22530 of type urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.269 luup_log:34: RFXtrx: Found child device id TS/T2/30721 of type urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.270 luup_log:34: RFXtrx: Found child device id DS/x10sec.DS/07082A of type urn:schemas-micasaverde-com:device:DoorSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.270 luup_log:34: RFXtrx: Found child device id DS/x10sec.DS/9E91EB of type urn:schemas-micasaverde-com:device:DoorSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.271 luup_log:34: RFXtrx: Found child device id TS/TH1/47873 of type urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.271 luup_log:34: RFXtrx: Found child device id TS/TH1/28676 of type urn:schemas-micasaverde-com:device:TemperatureSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.272 luup_log:34: RFXtrx: Found child device id MS/x10sec.MS/AAA593 of type urn:schemas-micasaverde-com:device:MotionSensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.273 luup_log:34: RFXtrx: Found child device id HS/TH1/28676 of type urn:schemas-micasaverde-com:device:HumiditySensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.273 luup_log:34: RFXtrx: Found child device id HS/TH1/22530 of type urn:schemas-micasaverde-com:device:HumiditySensor:1 <0x2b4a5680>
50 04/13/12 0:40:55.274 luup_log:34: RFXtrx: Tree with number child devices: 9 <0x2b4a5680>
50 04/13/12 0:40:55.274 luup_log:34: RFXtrx:        door sensors: 2 <0x2b4a5680>
50 04/13/12 0:40:55.274 luup_log:34: RFXtrx:      motion sensors: 0 <0x2b4a5680>
50 04/13/12 0:40:55.275 luup_log:34: RFXtrx:      light switches: 0 <0x2b4a5680>
50 04/13/12 0:40:55.275 luup_log:34: RFXtrx:  dim light switches: 0 <0x2b4a5680>
50 04/13/12 0:40:55.275 luup_log:34: RFXtrx:     window covering: 0 <0x2b4a5680>
50 04/13/12 0:40:55.276 luup_log:34: RFXtrx: temperature sensors: 4 <0x2b4a5680>
50 04/13/12 0:40:55.276 luup_log:34: RFXtrx:    humidity sensors: 3 <0x2b4a5680>
50 04/13/12 0:40:55.276 luup_log:34: RFXtrx:  barometric sensors: 0 <0x2b4a5680>
50 04/13/12 0:40:55.276 luup_log:34: RFXtrx:        wind sensors: 0 <0x2b4a5680>
50 04/13/12 0:40:55.277 luup_log:34: RFXtrx:        rain sensors: 0 <0x2b4a5680>

There is a stupid bug in the MOTION entry in the table tableDeviceTypes. Type is uurn... rather than urn...
Sorry. That should work afther this fix.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 13, 2012, 12:43:42 pm
lolodomo,

Association working properly :)
Very nice...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: gibbo on April 13, 2012, 06:11:01 pm
OK, I thought this would be almost simple, but maybe it shows just what a Newbie I am to this.

Just got a vera lite and rfx433... 

I've downloaded the zip file and tried to upload all the files... but dont seem to be able to get / keep the RFX connected / recognised to it.

Once it is, how do I then add devices via it - or maybe its becuase its not correctly connecting that it isnt seeing the devices. (to start with I'm playing with some Lightwave RF devices (just sockets etc).

Help! :oS

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 13, 2012, 07:22:54 pm
OK, I thought this would be almost simple, but maybe it shows just what a Newbie I am to this.

Just got a vera lite and rfx433... 

I've downloaded the zip file and tried to upload all the files... but dont seem to be able to get / keep the RFX connected / recognised to it.

Once it is, how do I then add devices via it - or maybe its becuase its not correctly connecting that it isnt seeing the devices. (to start with I'm playing with some Lightwave RF devices (just sockets etc).

Help! :oS

If you have a remote associated to a socket, use it to turn on or off the socket. A Vera device will then be created automatically by the plugin.
If you have only LightwaveRF receivers (sockets) and no remote, you have to create manual Vera device using the UI on the master device.
Tell us in which case you are and I will guide you. Shapa is our LightwaveRF expert, it should be able to help you to make it work ;D
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: gibbo on April 13, 2012, 07:58:07 pm
I think I've got there.. it was the setting up that needed a device type in it. urn:schemas-rfxcom-com:device:rfxtrx:1 is what I used
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 14, 2012, 03:43:55 am
I think I've got there.. it was the setting up that needed a device type in it. urn:schemas-rfxcom-com:device:rfxtrx:1 is what I used

When creating the device, just enter "D_RFXtrx.xml" in the field "Upnp Device Filename". That's enough.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 14, 2012, 05:38:12 am
Do not forget to set 38400 port speed :)


Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: bthovda on April 17, 2012, 03:04:10 pm
Do some of you know if there are smoke detectors (e.g nexa) that can communicate with this rfxcom device?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on April 17, 2012, 03:30:09 pm
The RFXtrx433 supports the NEXA KD101 and X10 SD90 smoke detectors.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: chris66 on April 17, 2012, 05:11:41 pm
Hello, Does anybody know what is the command to send order via The RFXCOM trans to an X10 DEVICE? Like for example [X10: ID: X10A02 CMD: -On] ? Thanks.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on April 18, 2012, 02:50:34 am
chris66,

I suppose you own an RFXLAN. The protocols of RFXLAN and the RFXtrx are different! If you are able to write the coding for the RFXLAN plug-in contact RFXCOM support.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: chris66 on April 18, 2012, 03:24:34 am
b_weijenberg,

Well suppose! Right I own an RFXCOM LAN transceiver, for your information, the plugin is already implemented in Vera,  (See appropriate plugin RFXCOM interface), I can receive X10, Oregon but I was just wondering how to send to an X10. I can imagine that the protocol is different, but for the end user, the command line should be normalised. I think Bert could be aware of that.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: gibbo on April 18, 2012, 02:08:48 pm
Just an update from my install...

Got it to work second time round. Might have to re install the devices though as it only appears to see / recognise the off transmission from other devices (remote or the wifi link) - actually only saw the off signal I think.

I had bought fibaro 3kw switch too. That works fine - it was only after I'd mounted it in the attic that I discovered the one light switch in my house with a neutral wire in (as I was installing the light wave dimmer).

One question from me - homeeasy produce an external Pir, do you have plans to add that into the interface at some point? @ lolodomo

Thanks for your hardwork!,
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: strangely on April 28, 2012, 11:32:58 pm
Just thought I'd drop a quick note to say i'm up and running with this now and I'm very impressed with the work that's gone into this and the setup was a breeze!

Thanks for all the hard work guys!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on April 29, 2012, 05:19:19 am
Just a quick message to mention that the RFXtrx firmware is now in version v35 and the plugin has to be updated to take into account few changes (rain sensors) and added sensors (UPM).
I will do it but probably not during the coming week.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on April 30, 2012, 10:07:39 am
Hi lolodomo,

Sure, waiting for a new releases :)
Anyway, it is stable and very efficient even in "alpha" stage
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TANE on April 30, 2012, 04:23:16 pm
Thank you for the great plugin.
All is working fine.

I have added more 30 new devices ...(few to go)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 01, 2012, 05:33:40 am
Please comment what category of devices you are using with the plugin, what is working well and what is not working, and don't hesitate to make suggestions.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TANE on May 01, 2012, 07:24:57 am
Hi,

I have added the fallowing devices
- Oregon (no problem)
- Kaku (no problem)
- Harrison (no problem)

Will test the scene control in the next days.

I hope you can add support for the Lan version so that I can add my Visonic sensors and Rfxio to the vera.



Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 01, 2012, 01:34:44 pm
For the LAN version, you have the other plugin.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TANE on May 01, 2012, 02:44:17 pm
For the LAN version, you have the other plugin.

thanks.
The Lan version is only showing the Harrison option.
I will contact de developer.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Meinaart on May 01, 2012, 04:10:05 pm
I see in the topic start that this plugin should support HomeEasy, how do I add my magnetdoorcontact (HE305EU) and my build in light switch (HE886)?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: arjenhiemstra on May 07, 2012, 05:35:15 am
I'm quite new to this all and bought my first RFXcom USB last week. To test and automate a few things I also bought a KaKu door sensor (AMST-606) to use it as a sensor to trigger scenes.
The sensor is detected by the Vera but reports as a lightbuld instead of a (armable) sensor. Is this due to the Alpha status of the plugin or is this normal behaviour?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on May 07, 2012, 05:52:39 am
I suppose this is normal behavior because the command send by the sensor is identical to a command send by a remote to control a lamp module.

About AC (KAKU, Chacon, HomeEasy, NEXA...) sensors read this: http://www.domoticaforum.eu/viewtopic.php?f=27&t=7337
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 07, 2012, 08:49:04 am
I see in the topic start that this plugin should support HomeEasy, how do I add my magnetdoorcontact (HE305EU) and my build in light switch (HE886)?

You probably associate your magnetdoorcontact (HE305EU) and your build in light switch (HE886) ? In this case, you just have to change the state of your door contact and the command sent to the light switch will be received by the RFXtrx and the plugin; a binary light device will then be automatically created.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 07, 2012, 08:51:11 am
I'm quite new to this all and bought my first RFXcom USB last week. To test and automate a few things I also bought a KaKu door sensor (AMST-606) to use it as a sensor to trigger scenes.
The sensor is detected by the Vera but reports as a lightbuld instead of a (armable) sensor. Is this due to the Alpha status of the plugin or is this normal behaviour?

It is the normal behaviour. Your sensor acts as an ON/OFF switch to control a light or something else.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Thomasss on May 07, 2012, 05:03:02 pm
Just to say thank you to all contributors, specially to lolodomo for this plugin. It works like a charm.
It detected all my Oregon sensors in a few minutes, even the main station !? 
Don't have much more RFX deviceS. But I will certainly buy a kit a of on/off module from Chacon for testing.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TANE on May 07, 2012, 05:21:51 pm
My Systeem keeps adding devices.
How can i disable auto add?

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: arjenhiemstra on May 07, 2012, 05:35:32 pm

It is the normal behaviour. Your sensor acts as an ON/OFF switch to control a light or something else.

Hmm, not what I expected. That is a pitty.
Is it somehow possible to get it report in Vera as a armable sensor that will be tripped when the state (On to Off or the other way around) changes?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on May 08, 2012, 04:09:50 am
Arjen, for 3 reasons it is preferred to use a real security sensor like the DS90.

1 a security sensor transmits about every hour an alive signal to indicate that the sensor is operational,
2 a security sensor reports the battery low state
3 a security sensor transmits a few RF packets so that the risk that other sensor signals are disturbed is minimized.

The points 1 and 2 are important because you need a reliable solution for a security system.
And connect the VERA (and the Internet router) to an UPS if you want to use the VERA as a security system.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 08, 2012, 04:43:29 am
My Systeem keeps adding devices.
How can i disable auto add?

Just set the variable AutoCreate to 0 and reload the UI.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 08, 2012, 04:51:04 am

It is the normal behaviour. Your sensor acts as an ON/OFF switch to control a light or something else.

Hmm, not what I expected. That is a pitty.
Is it somehow possible to get it report in Vera as a armable sensor that will be tripped when the state (On to Off or the other way around) changes?

There is nothing in the message that can help to identify the kind of the sending module, while the kind of message can help to identify the kind of the receiving module. That's why the plugin create a device that represent the receiver.

But I think you can simply create a device and a scene to do what you need. Your scene will update your device when the RFXtrx plugin update the state of the RFX device.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on May 08, 2012, 05:01:22 am
lolodomo,

sorry for being so late, but I had to travel for my job and have been unable to finish the code, here are the snippets you can add to your code in order to detect X10 security devices:
 
   -- SECURITY_X10SR = { 0x20, 0x2, 8, nil, nil, "x10SD" }, todo= SECURITY REMOTE
   SECURITY_X10MS = { 0x20, 0x1, 8, nil, nil, "x10MS" },
   SECURITY_X10DS = { 0x20, 0x0, 8, nil, nil, "x10DS" }
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on May 08, 2012, 05:14:29 am
Hi Lolodomo,

I've been travelling in various countries, and have not been able to finish the coding of the action on devices,
so please find below the code working to detect X10 security devices:

   
Code: [Select]
-- SECURITY_X10SR = { 0x20, 0x2, 8, nil, nil, "x10SD" }, todo= SECURITY REMOTE
SECURITY_X10MS = { 0x20, 0x1, 8, nil, nil, "x10MS" },
SECURITY_X10DS = { 0x20, 0x0, 8, nil, nil, "x10DS" }

   
Code: [Select]
CMD_ARM = { "Normal", "DOOR", "VAR_" },
CMD_NORMAL = { "Normal", "DOOR", nil },
CMD_NORMALDELAYED = { "Normal Delayed", "DOOR", nil },
CMD_DTAMPERED = { "Tampered device", "DOOR", nil },
CMD_ALARM = { "Alarm", "DOOR", nil },
CMD_ALARMDELAYED = { "AlarmDelayed", "DOOR", nil },

CMD_MTAMPERED = { "Tampered device", "MOTION", nil },
CMD_MOTION = { "Motion", "MOTION", nil },
CMD_NOMOTION = { "No Motion", "MOTION", nil },

Code: [Select]
VAR_ARMED = { "urn:upnp-org:serviceId:SecuritySensor1", "Armed", true },

Code: [Select]
DOOR = { "urn:schemas-micasaverde-com:device:DoorSensor:1", "D_DoorSensor1.xml", "RFX Door ", "DS/", false },
MOTION = { "urn:schemas-micasaverde-com:device:MotionSensor:1", "D_MotionSensor1.xml", "RFX Motion ", "MS/", false },

Code: [Select]
tableMsgTypes.SECURITY_X10DS[4] = decodeX10DoorSensor
tableMsgTypes.SECURITY_X10MS[4] = decodeX10MotionSensor

Code: [Select]
function setArmed(device, newArmedValue)

local id = luup.devices[device].id
log("setArmed " .. id .. " target " .. newArmedValue)

local category
log("Unexpected device id " .. id .. ". setArmed command not sent", 2)
-- return
-- end


end

Code: [Select]
function decodeX10DoorSensor(subType, data, seqNum)

local altid = "D/" .. string.format("%02X", tonumber(string.byte(data, 1)))
.. string.format("%02X", tonumber(string.byte(data, 2)))
.. string.format("%02X", tonumber(string.byte(data, 3)))

-- log("Decode x10security: " .. subtype_name .. " altid=" .. altid .. " CMD=" .. string.sub(data, 7, 8) )
log("Decode x10securityDS: altid=" .. altid )

local tableCmds = {}
local cmdValue = nil
local cmd = tonumber(string.byte(data, 4))

if (cmd == 00)
then
cmdValue = tableCommands.CMD_NORMAL[1]
elseif (cmd == 01)
then
cmdValue = tableCommands.CMD_NORMALDELAYED[1]
elseif (cmd == 02)
then
cmdValue = tableCommands.CMD_ALARM[1]
elseif (cmd == 03)
then
cmdValue = tableCommands.CMD_ALARMDELAYED[1]
elseif (cmd == 08)
then
cmdValue = tableCommands.CMD_DTAMPERED[1]
else
if (cmd ~= nil)
then
log("x10securityDS command not yet implemented: " .. cmd .. "hex=" .. formattohex(cmd), 2)
else
log("x10securityDS command not yet implemented " , 2)
end
end


local battery = tonumber(string.sub(string.byte(data, 5), 2, 2))

if (cmdValue ~= nil)
then
log("Decode x10securityDS: altid=" .. altid .. " CMD=" .. cmdValue .. " Battery lvl=" .. battery)
table.insert(tableCmds, { cmdValue, nil } )
end
if (battery <= 9)
then
battery = (battery + 1) * 10
table.insert(tableCmds, { tableCommands.CMD_BATTERY[1], battery } )
end

return altid, tableCmds

end

function decodeX10MotionSensor(subType, data, seqNum)

local altid = "M/" .. string.format("%02X", tonumber(string.byte(data, 1)))
.. string.format("%02X", tonumber(string.byte(data, 2)))
.. string.format("%02X", tonumber(string.byte(data, 3)))

local tableCmds = {}
local cmdValue = nil
local cmd = tonumber(string.byte(data, 4))

if (cmd == 04)
then
cmdValue = tableCommands.CMD_MOTION[1]
elseif (cmd == 05)
then
cmdValue = tableCommands.CMD_NOMOTION[1]
elseif (cmd == 08)
then
cmdValue = tableCommands.CMD_MTAMPERED[1]
else
if (cmd ~= nil)
then
log("x10securityMS command not yet implemented: " .. cmd .. "hex=" .. formattohex(cmd), 2)
else
log("x10securityMS command not yet implemented " , 2)
end
end

local battery = tonumber(string.sub(string.byte(data, 5), 2, 2))

if (cmdValue ~= nil)
then
log("Decode x10securityMS: altid=" .. altid .. " CMD=" .. cmdValue .. " Battery lvl=" .. battery)
table.insert(tableCmds, { cmdValue, nil } )
end
if (battery <= 9)
then
battery = (battery + 1) * 10
table.insert(tableCmds, { tableCommands.CMD_BATTERY[1], battery } )
end

return altid, tableCmds

end

hope it helps anyway
Chris


Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 08, 2012, 05:21:43 am
Thank you, I will add your code in the new alpha version I am preparing.


For arming action, I think something needs to be added in the implementation file to link to your function setArmed. I will add it too.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Meinaart on May 08, 2012, 05:44:37 am
I suppose this is normal behavior because the command send by the sensor is identical to a command send by a remote to control a lamp module.

About AC (KAKU, Chacon, HomeEasy, NEXA...) sensors read this: http://www.domoticaforum.eu/viewtopic.php?f=27&t=7337

Which door- and motionsensors do you recommend using with Vera/RFXCom combination?

The DS90 is a bit pricy and the MS13 doesn't seem to be available anymore (or for a very high price). I bought the RFXCom to have access to some cheaper sensors. With the prices of the DS90 and MS13 I am better of buying Z-Wave sensors (same price range).

BTW, I could not register on DomoticaForum.eu, the captcha doesn't seem to work properly.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on May 08, 2012, 06:19:11 am
Lolodomo,

you're right I forgot to add the code from within I_RFXTRX.xml  :-[:

Code: [Select]
    <action>
  <serviceId>urn:upnp-org:serviceId:SecuritySensor1</serviceId>
  <name>SetArmed</name>
  <run>if (pluginLib ~= nil) then pluginLib.setArmed(lul_device, lul_settings.newArmedValue) end</run>
    </action>
but it might there is a bug as it was not working
Chris
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on May 08, 2012, 06:42:20 am
@Meinaart, check elekhomica.nl. They have a few MS13 left for a special price. The normal price is about € 30
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Meinaart on May 08, 2012, 08:32:47 am
@Meinaart, check elekhomica.nl. They have a few MS13 left for a special price. The normal price is about € 30

Thanks, I ordered a 5-pack :D. Hopefully they work as expected.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Meinaart on May 10, 2012, 06:37:51 am

It is the normal behaviour. Your sensor acts as an ON/OFF switch to control a light or something else.

Hmm, not what I expected. That is a pitty.
Is it somehow possible to get it report in Vera as a armable sensor that will be tripped when the state (On to Off or the other way around) changes?

There is nothing in the message that can help to identify the kind of the sending module, while the kind of message can help to identify the kind of the receiving module. That's why the plugin create a device that represent the receiver.

But I think you can simply create a device and a scene to do what you need. Your scene will update your device when the RFXtrx plugin update the state of the RFX device.

Would it be possible to offer the option to change the device type manually? So that it's detected as a light switch but it can be changed to "SecuritySensor" in the Vera interface?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 11, 2012, 07:13:48 am
@Chris: your code relative to X10security will create the door and motion devices but what is missing is the management of Tripped and LastTrip variables.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 11, 2012, 12:14:48 pm
Plugin in version alpha 3 dated 11th of May is attached to the first message of this topic.

What's new in version alpha 3:
- plugin is up to date with RFXtrx firmware v41
- new devices supported: Honeywell TS15C (temperature sensor), UPM WT450H (temperature and humidity sensor), UPM RG700 (rain sensor), UPM WDS500 (wind sensor), OWL CM119/CM160 (energy usage sensor), RisingSun (switch power)
- barometer, rain and wind devices include now UI5 events and so can be used as triggers in a scene
- X10 security is partially supported (door and motion sensors are created but status is not updated; arm/disarm is not yet implemented)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Meinaart on May 11, 2012, 12:26:42 pm
Thanks for the hard work lolodomo, very much appreciated! :)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on May 12, 2012, 04:42:24 am
@Chris: your code relative to X10security will create the door and motion devices but what is missing is the management of Tripped and LastTrip variables.

Yes I will spend some time next week-end to tackle both those values and the delay management
Also security remote are not yet supported and Bert told me how to simulate them even if I've not any.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 12, 2012, 05:26:56 am
@Chris: your code relative to X10security will create the door and motion devices but what is missing is the management of Tripped and LastTrip variables.

Yes I will spend some time next week-end to tackle both those values and the delay management
Also security remote are not yet supported and Bert told me how to simulate them even if I've not any.

I have integrated your code and done some little changes, so start from the last version.

I don't know what are these "delayed" status and what you can do from them in Vera...
For the two variables, this is probably very easy to add now. Just declare the two variables, add a new command for the date, and associate the variables to each command.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: bfromdruten on May 13, 2012, 06:39:31 pm
Hi,

I have added the fallowing devices
- Oregon (no problem)
- Kaku (no problem)
- Harrison (no problem)

Will test the scene control in the next days.

I hope you can add support for the Lan version so that I can add my Visonic sensors and Rfxio to the vera.

Tane, lan version works with all devices mentioned above. Make sure you get the latest version from svn. The first version supports harrison. The latest kaku, visonic, homeeasy etc..
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TANE on May 18, 2012, 05:23:12 am
Hi,
For Harrison control is not always the Vera used for controlling.
Is there a possibility for adding the Harrison remote to the Vera so that the status changes will be noticed?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 18, 2012, 06:13:37 am
Hi,
For Harrison control is not always the Vera used for controlling.
Is there a possibility for adding the Harrison remote to the Vera so that the status changes will be noticed?

No because the RFXtrx does not decode messages from Harrison remote.
This is a limit of the RFXtrx, not a limit of the plugin.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: bthovda on May 18, 2012, 08:18:12 am
Anyone know an easy way to monitor my NEXA smoke detector KD-101LA trough USB rfxcom on my vera 3?. dosent look like its automaticly added, so i guess i would have to something manually?.

Thank you!!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 18, 2012, 09:12:35 am
Anyone know an easy way to monitor my NEXA smoke detector KD-101LA trough USB rfxcom on my vera 3?. dosent look like its automaticly added, so i guess i would have to something manually?.

Thank you!!

KD101 is part of the security1 category. Chris is working on this part. Support by the plugin for this smoke detector is not yet implemented. Sorry.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: bthovda on May 18, 2012, 04:06:51 pm
Anyone know an easy way to monitor my NEXA smoke detector KD-101LA trough USB rfxcom on my vera 3?. dosent look like its automaticly added, so i guess i would have to something manually?.

Thank you!!

KD101 is part of the security1 category. Chris is working on this part. Support by the plugin for this smoke detector is not yet implemented. Sorry.


Ok, thank you.
Looking forward to try that out!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: sliver38 on May 21, 2012, 05:50:52 pm
Hi
I've bought an Oregon UV probe UVR128: is it plan to take it into account? Thanks a lot for this super work!!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 25, 2012, 01:32:24 pm
Hi
I've bought an Oregon UV probe UVR128: is it plan to take it into account? Thanks a lot for this super work!!

UVN128 is mentioned as supported by RFXCOM, not UVR128.
Regarding support of the UV sensors by the plugin, that would be easy, there is just a new specific device to create. I could add it for the next release.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on May 26, 2012, 04:31:08 am
Hi lolodomo,

I'm waiting for a UV support as well :)

Thank you!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Pierre.bln on May 26, 2012, 07:54:30 pm
Hi,

Sorry to interrupt a thread between experts  ::)

Question as a potential user:
Is the HomeEasy (EU) protocol/plugin implemented so that I could pair my devices directly with Vera (via RFXcom USB), without needing any HomeEasy controller/remote to send an initial order?

I don't have any Homeeasy device yet, but they look like a damn good alternative to Z-wave for basic ON/OFF modules (no feedback or power consumption). I can get a Homeeasy On/Off plug for 8€ here in Germany (instead of 45€+ for a Z-wave switch), and would like to know if I could save even more by never buying original Homeeasy controllers  ;D

Don't let this question disturb you from improving the plugin, but any tip is welcome. Thanks!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Quinten on May 27, 2012, 04:19:31 am
Theoratically it is possible, but you have to then painstakingly create every device manually, using the correct parameters.  The AutoCreate functionality will only work if you send the controlling commands from a controller first.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Pierre.bln on May 27, 2012, 06:20:26 am
Thanks Quinten, that's good to know!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Pierre.bln on May 27, 2012, 10:05:22 am
Another quick one if I may:

I use the SQ Remote app. Do you know if it will list the HomeEasy or X10 devices from the Vera?
I don't know if SQ remote is "dumb enough" to control them, without wondering which actual protocol/interface lies behind the Micasaverde box.

Pierre
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: strangely on May 27, 2012, 12:09:45 pm
If the devices are implemented as standard devices like power switches etc, then SQ remote shouldn't know any different.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: sliver38 on May 27, 2012, 05:44:00 pm
Hi
I've bought an Oregon UV probe UVR128: is it plan to take it into account? Thanks a lot for this super work!!

UVN128 is mentioned as supported by RFXCOM, not UVR128.
Regarding support of the UV sensors by the plugin, that would be easy, there is just a new specific device to create. I could add it for the next release.

Yes sorry I was talking about UVN128 ! Thank you very much if you add UV sensors!!  :) I want to use mine to trigger my 'blind partially closure': the will 75% close if temperature >25°C AND 'UV signal' is high (to not close them if cloudy outside).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 28, 2012, 04:13:33 am
If the devices are implemented as standard devices like power switches etc, then SQ remote shouldn't know any different.

Standard devices are used when they exist: temperature, humidity, switch power, dimmer light, window covering, ...
Specific devices were created for barometer sensors, wind sensors and rain sensors.
Title: Re: Plugin for the USB RFXtrx from RFXCOM:RollerTrol windblind and shade motors
Post by: rollertrol on May 28, 2012, 12:15:04 pm
Hi @lolodomo, I now have an RFXtrx433 transceiver and I'm attempting to use it with Vera so that I can produce any easy, clear set of instructions on how to set it up (I have a Veralite). I have tested the RFXtrx433 with the sample apps that came with the unit and it works perfectly.

I was wondering if the RFXCOM plug-in that appears in the list of searchable plug-ins is the same code that is referred to in your directions in this forum? I wasn't able to contact you directly, but you can reach me through the contact page at rollertrol.com if necessary. I realize you are probably very busy, but there are a few issues I need to sort out and I'm hoping a few quick questions will do the trick.

Regards, Adrian

Adrian Biffen
Customer Service
RollerTrol Automation Systems
http://RollerTrol.com/

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Quinten on May 29, 2012, 07:26:51 am
The RFXCOM plugin is for the LAN version, it will not work for the RFXtrx433.  When development started, it used small parts of the RFXCOM plugin, but those days are well behind us ;)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on May 29, 2012, 08:20:32 am
Hi @Quinten, thanks for that, I guess that explains why it didn't work  ::)

I'll use the link in this forum instead and see how that goes,

Regards, Adrian

Adrian Biffen
Customer Service
RollerTrol Automation Systems
http://RollerTrol.com/

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on May 29, 2012, 09:44:47 am
Hi, I have managed to create the RFXcom device on my system, and I can see that I will have to write some code to use this for controlling our window blind motors. All the modules I installed seem to be for input sensing, so I'm wondering if there is an example of motor control somewhere? Also, if this is inappropriate content for this discussion, please let me know.

Thanks, Adrian
Title: Re: Plugin for the USB RFXtrx from RFXCOM:RollerTrol windblind and shade motors
Post by: lolodomo on May 29, 2012, 02:04:32 pm
Hi @lolodomo, I now have an RFXtrx433 transceiver and I'm attempting to use it with Vera so that I can produce any easy, clear set of instructions on how to set it up (I have a Veralite). I have tested the RFXtrx433 with the sample apps that came with the unit and it works perfectly.

I was wondering if the RFXCOM plug-in that appears in the list of searchable plug-ins is the same code that is referred to in your directions in this forum? I wasn't able to contact you directly, but you can reach me through the contact page at rollertrol.com if necessary. I realize you are probably very busy, but there are a few issues I need to sort out and I'm hoping a few quick questions will do the trick.

Regards, Adrian

Adrian Biffen
Customer Service
RollerTrol Automation Systems
http://RollerTrol.com/

The RFXCOM plug-in that appears in the list of searchable plug-ins is certainly the other plugin, the one for the RFXLAN product.

What issues do you have and with which plugin ?

If you try to make the plugin work with the RollerTrol blind, this is a new feature of the RFXtrx product introduced in the last firmware (v42) that is not yet supported by the plugin. I will add it in the next release.

I see there is a major restriction to use the RFXtrx with the RollerTrol:
Quote
All other receive protocols are disabled if RollerTrol receive is enabled
:(

In the SDK, I see a "confirm" command. What is it ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 29, 2012, 02:11:12 pm
Hi, I have managed to create the RFXcom device on my system, and I can see that I will have to write some code to use this for controlling our window blind motors. All the modules I installed seem to be for input sensing, so I'm wondering if there is an example of motor control somewhere? Also, if this is inappropriate content for this discussion, please let me know.

Thanks, Adrian

You can search where window covering is referenced in the plugin, either Harrison curtain or LightwareRF.
But it is something relatively easy to add for me who know perfectly the plugin. I can add it in the next release of the plugin.

After a quick reading of the RFXtrx SDK, the only thing not clear for me is the role of the "Confirm" command. Open, Close, Stop commands are clear, Confirm is not.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on May 29, 2012, 02:43:16 pm
Hi @lolodomo, thanks for your response. Certainly there is no need for me to re-invent the wheel here. I have been programming for 35 years, but I'm new to Lua and Vera, so it would probably take me a long time to get it all working. If you think of some contribution I could make, I am certainly open to that idea, we are very appreciative of the fact that you are doing this.

I may be completely wrong about this, but my take on what has to happen is that a user would have one of our 14 channel remotes (14 + ALL), and the RFXCOM unit (and/or Vera) would have to 'learn' each of the channel protocols.

This is what the 'confirm' button is about: you set the channel number on the remote, then press a switch on the motor to put it into 'learn' mode, then press the confirm button on the remote to transmit the address encoding of that particular channel to the motor. The motor then beeps and jogs to indicate transmission received and understood, and the pairing is complete.

You can see a more complete description of the process on our website:

http://RollerTrol.com/instructions

The motors are capable of learning codes from multiple remotes, so you can have more than 1 remote in the same room for any particular motor. You can also assign multiple motors to the same channel.

That is a very odd restriction you mention, I will find out what is behind that.

If I can be of further assistance, please contact me anytime.

Regards, Adrian

Adrian Biffen
Customer Service
RollerTrol Automation Systems
http://RollerTrol.com/

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on May 29, 2012, 04:19:55 pm
Hi @lolodomo, I was just checking up on your comment about restricted receiving:

"All other receive protocols are disabled if RollerTrol receive is enabled"

It actually turns out to be a non-issue because the only time you would be receiving is to learn the codes of the remotes, which you would only do once.

Apparently it is a temporary constraint because adding a protocol in reception mode can affect other protocols. This depends on timing and protocol overlaps; extensive testing and re-tuning of all protocols is needed to minimize the impact. Again, this does not affect the transmit capabilities of the RFXtrx433, which is what you would be using for controlling the RollerTrol window shade and blind motors.

Regards, Adrian

Adrian Biffen
Customer Service
RollerTrol Automation Systems
http://RollerTrol.com/

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 29, 2012, 05:07:05 pm
Hi @lolodomo, thanks for your response. Certainly there is no need for me to re-invent the wheel here. I have been programming for 35 years, but I'm new to Lua and Vera, so it would probably take me a long time to get it all working. If you think of some contribution I could make, I am certainly open to that idea, we are very appreciative of the fact that you are doing this.

If you are hurry, you can try and then send me the changes. This is not very difficult if you have minimal knowledge of Lua and how Vera plugins are working.
If you can wait for few days, I will add it myself.

Quote
I may be completely wrong about this, but my take on what has to happen is that a user would have one of our 14 channel remotes (14 + ALL), and the RFXCOM unit (and/or Vera) would have to 'learn' each of the channel protocols.

This is what the 'confirm' button is about: you set the channel number on the remote, then press a switch on the motor to put it into 'learn' mode, then press the confirm button on the remote to transmit the address encoding of that particular channel to the motor. The motor then beeps and jogs to indicate transmission received and understood, and the pairing is complete.

Ok, in that case, we can forget the Confirm command and define that the setup will be done normally using the remote. The RFXtrx Vera plugin will just listen the Open/Close/Stop commands and then create a window covering device for each remote id. Then, for this device, the user will be able to open/close/stop the window covering, just simulating the command of the remote. The user will still be able to use the remote with an automatic status refresh on the Vera.

Is the motor always sold with a remote ?
If the ser can buy a motor without a remote, then we would have to implement the pairing on the Vera side.

Quote
The motors are capable of learning codes from multiple remotes, so you can have more than 1 remote in the same room for any particular motor.

One device for each remote command will be created but then the user has the possibility to setup in order to keep only one device being updated from each remote. This is something I have already implemented  for Chacon and others, so this will work for RollerTrol too.

Quote
You can also assign multiple motors to the same channel.

You mean one button of a remote controlling several motors ? In this case, Vera will display only one device representing all the motors.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 29, 2012, 05:13:48 pm
Hi @lolodomo, I was just checking up on your comment about restricted receiving:

"All other receive protocols are disabled if RollerTrol receive is enabled"

It actually turns out to be a non-issue because the only time you would be receiving is to learn the codes of the remotes, which you would only do once.

Not exactly because if the user does this, the status of the Vera device (open or close) will not be updated when the user will use the remote. So it is better to have receiving, of course if receiving is very reliable.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on May 29, 2012, 05:39:08 pm
Hi @lolodomo, we are not in a particular hurry as the first shipment of RFXtrx433 units won't be here until late next week.

I would say that a user will need to have at least 1 remote in order to do this. They are not expensive.

I don't think it will be a problem with Vera with the 'grouping' of motors onto one channel, if I can call it anything I want, like 'Group A'?

You have lost me a bit on the receiving issue. I'm assuming that if one uses the remote, it will talk to the motors directly, no need for RFXtrx unit to be listening during normal operation. I'm thinking it only needs to listen 1 time during setup to capture the channel encoding. Did I get this wrong?

Regards, Adrian
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on May 29, 2012, 05:48:11 pm
Hi @lolodomo, we are not in a particular hurry as the first shipment of RFXtrx433 units won't be here until late next week.

I should be able to publish a new version during next week.

Quote
I would say that a user will need to have at least 1 remote in order to do this. They are not expensive.

I don't think it will be a problem with Vera with the 'grouping' of motors onto one channel, if I can call it anything I want, like 'Group A'?

Yes, you can give the name that you want to the device.

Quote
You have lost me a bit on the receiving issue. I'm assuming that if one uses the remote, it will talk to the motors directly, no need for RFXtrx unit to be listening during normal operation. I'm thinking it only needs to listen 1 time during setup to capture the channel encoding. Did I get this wrong?

The main idea is to have a device managed by the Vera that represents your motor. The device can then be controlled using a PC, a tablet, a phone, ... through Vera stuff. But you can still use the original remote to control your motor and in that case, it is very interesting to have the device status updated automatically on the Vera. For this, the receiving capability is required.

Regards
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on May 29, 2012, 07:40:52 pm
Hi @lolodomo, ok, I get your point about Vera knowing the device status, but in reality it will only know if a command has been issued, not that the window blind actually moved. For that there would have to be some kind of sensor feedback.

Also, the way our motors work is that they will travel to the preset end (which is configured with the remote, no need to get to the blind once installed), then stop when the internal pulse counter matches the preset value stored in non-volatile memory. So even if Vera thought it was closed and issued an open command, it would still end up where the user wanted it.

I don't see this as a major problem, and I understand that this may be resolved in the future anyway. I'm just happy that we can make these puppies work within the context of a full home automation system, instead of being an isolated system!

We have some new Arduino compatible controllers in the works that will be able to control LED lighting and other devices, using the same remote control, so it will get even more interesting soon :)

Cheers, Adrian
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Brientim on June 05, 2012, 02:38:33 pm
Hello,

After installing this plugin I experienced crashes with Automator.App. I contacted the developer to enable them to identify the cause. Below are the detailed response.

-----
I found the cause of the crash.  The devices included with the RFXtrx plugin (wind, barometer, and rain sensor) are defined in an unexpected way that is causing Automator.app to crash.  Specifically the DisplayStatus entry in the JSON is defined as an empty string.  This tag is used to provide a mechanism by which the icons can change with the value of the device (such as how dimmable lights have 4 different icons).    This is expected to be json object (e.g. a set of name/value pairs) rather than a single string.  

While I can, and will, code around this to prevent a crash in the future it may take some time before that would get released.  In the meantime I would suggest making this change to the plugin's json definition (and ideally contact the plugin owner, if that is not you) to have them make this.
--------

Whilst I will rectify this to enable Automator to function correctly, you may will to look at the this for future releases. Some example where provided and if you need the examples of what coding changes are recommended please PM and I will forward you an email.

Thanks.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 06, 2012, 07:25:53 am
Hello

I will correct that in the next version.
As I don't need DisplayStatus, what must be included in the JSON file ? Nothing ? Something like this ?
Code: [Select]
"DisplayStatus" : [],
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: automator.app on June 06, 2012, 10:37:34 am
Hello

I will correct that in the next version.
As I don't need DisplayStatus, what must be included in the JSON file ? Nothing ? Something like this ?
Code: [Select]
"DisplayStatus" : [],

This should work (an empty object):

Code: [Select]
"DisplayStatus" : {},

As mentioned I will resolve the issue on my side as well but this will make your devices more consistent with the others (as far as I am aware of) anyways.

Thanks!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on June 06, 2012, 05:38:58 pm
Lolodomo,

finally get sometimes reading upnp, and several docs.
I have corrected the .lua from your latest drop:

On tableCommands table, I've added the reference to VAR_TRIPPED
Code: [Select]
CMD_NORMAL = { "Normal", "DOOR", "VAR_TRIPPED" },
CMD_NORMALDELAYED = { "Normal Delayed", "DOOR", "VAR_TRIPPED" },
CMD_ALARM = { "Alarm", "DOOR", "VAR_TRIPPED" },
CMD_ALARMDELAYED = { "AlarmDelayed", "DOOR", "VAR_TRIPPED" },
CMD_MOTION = { "Motion", "MOTION", "VAR_TRIPPED" },
CMD_NOMOTION = { "No Motion", "MOTION", "VAR_TRIPPED" },
CMD_DTAMPERED = { "Tampered door sensor", "DOOR", "VAR_TRIPPED" },
CMD_MTAMPERED = { "Tampered motion sensor", "MOTION", "VAR_TRIPPED" },

On TabVars, I've added the three upnp security sensors variables:
Code: [Select]
VAR_ARMED = { "urn:micasaverde-com:serviceId:SecuritySensor1", "Armed", false },
VAR_TRIPPED = { "urn:micasaverde-com:serviceId:SecuritySensor1", "Tripped", false },
VAR_LAST_TRIP = {"urn:micasaverde-com:serviceId:SecuritySensor1", "LastTrip", false },

in function actOnMessage(deviceId, tableCmds, dateMsg)

I've added the following code, after battery and before the look for the key:
Code: [Select]
-- tripped value for X10 security sensors
if (cmd == tableCommands.CMD_NORMAL[1] or cmd == tableCommands.CMD_NORMALDELAYED[1] or cmd == tableCommands.CMD_NOMOTION[1])
then
value = "0"

elseif (cmd == tableCommands.CMD_ALARM[1] or cmd == tableCommands.CMD_ALARMDELAYED[1] or cmd == tableCommands.CMD_MOTION[1])
then
if (dateMsg ~= nil)
then
variable = tabVars.VAR_LAST_TRIP
-- log("SET LAST TRIP" .. variable[2] .. " from " .. v.id .. " with value " .. dateMsg .. " " .. os.date("%H:%M:%S", dateMsg))
luup.variable_set(variable[1], variable[2], dateMsg, device)
end
value = "1"
end

I see that it works within the logs, but the UI5 still does not reflect the fact that the device is tripped. I've probabl still missing something. On the other hand, when I add a trigger on the tripped variable, it does work.
Also the Armed is still not working, therefore the trigger has to be put even if the device is not triggered, until I'd correct this bug, or just understand what I'm missing.
Delayed is not yet implemented.

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 07, 2012, 10:59:42 am
Dear Lolodomo,

I am a rookie in Home Automation trying tot get my RFXtrx433 working on my newly purchased Vera 3 system running with firmware 1.5.346. I first tried to install a driver from ftdichip com/drivers/vcp htm. I picked the driver for Linux x64 and installed it in Vera 3, as stated in the Quick User Guide from  the RFXtrx433. Nothing happend and the RFXtrx433 was not recognised. Mister Enver from Tane pointed me to this forum topic and especially to your first post. I then followed your Quick start Guide.
I am able to create the RFXtrx controller device, but instantly receive the message "Plugin not correctly Installed". When I try to setup the serial port  I see the following information:
Name:  ftdi-sio          (this name comes from the www ftdichip com driver)
device number: usb-rt3883-ohci-2
port: 3481
parity: none
databits: 8
Stopbit: 1
Baudrate: 38400 (configured by me)
Device name "RFXrtx controller device"  (after I have reloaded the lua engine.

The warning of plugin not correctly installed remains and in Devices The light in the window RFXtrx controller device is red withe the information "Lua Startup Failure".

What can I do now to get my RFXtrx controller running?

Regards, Johan

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 07, 2012, 01:52:40 pm
I see that it works within the logs, but the UI5 still does not reflect the fact that the device is tripped. I've probabl still missing something. On the other hand, when I add a trigger on the tripped variable, it does work.

I am going to compare to how the Visonic plugin updates these variables because I know that the status is correctly updated on UI5 with this plugin.

Quote
Also the Armed is still not working, therefore the trigger has to be put even if the device is not triggered, until I'd correct this bug, or just understand what I'm missing.
Delayed is not yet implemented.

Ok, thank you, I will include your code in the coiming new alpha version.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 07, 2012, 02:20:26 pm
Dear Lolodomo,

I am a rookie in Home Automation trying tot get my RFXtrx433 working on my newly purchased Vera 3 system running with firmware 1.5.346. I first tried to install a driver from ftdichip com/drivers/vcp htm. I picked the driver for Linux x64 and installed it in Vera 3, as stated in the Quick User Guide from  the RFXtrx433. Nothing happend and the RFXtrx433 was not recognised.

This was absolutely not required, the driver is already installed in the Vera when you buy it. Installing a new driver could have corrupted something.

Quote
I am able to create the RFXtrx controller device, but instantly receive the message "Plugin not correctly Installed". When I try to setup the serial port  I see the following information:
Name:  ftdi-sio          (this name comes from the www ftdichip com driver)
device number: usb-rt3883-ohci-2
port: 3481
parity: none
databits: 8
Stopbit: 1
Baudrate: 38400 (configured by me)
Device name "RFXrtx controller device"  (after I have reloaded the lua engine.

The warning of plugin not correctly installed remains and in Devices The light in the window RFXtrx controller device is red withe the information "Lua Startup Failure".

What can I do now to get my RFXtrx controller running?

You get no RFXtrx error messages in the logs ?
One idea could be that you did not upload all the files included in my zip files. Go in Apps => Developer apps => Luup files and check if you find all the files.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 07, 2012, 02:56:30 pm
I see that it works within the logs, but the UI5 still does not reflect the fact that the device is tripped. I've probabl still missing something. On the other hand, when I add a trigger on the tripped variable, it does work.

Checking the Visonic plugin code, it looks like the value for the "Tripped" variable must be set to 1 or 1, not "0" or "1". I am not sure if it can make the difference.

I would prefer to keep the code of the function actOnMessage as generic as possible, but ok with your changes; First make it work well and after I will do it more properly if possible.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on June 07, 2012, 03:16:09 pm
Hi Lolodomo,

actually after a while it was working on the UI5, may be not as fast as I was expecting, but actually similar to zwave security devices  ;D
I see that it works within the logs, but the UI5 still does not reflect the fact that the device is tripped. I've probabl still missing something. On the other hand, when I add a trigger on the tripped variable, it does work.

Checking the Visonic plugin code, it looks like the value for the "Tripped" variable must be set to 1 or 1, not "0" or "1". I am not sure if it can make the difference.

I would prefer to keep the code of the function actOnMessage as generic as possible, but ok with your changes; First make it work well and after I will do it more properly if possible.
I will re-run some test with numeric values to see if there's any change.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 07, 2012, 04:54:28 pm
Now added in the next release coming soon:
- RollerTrol added (including a new setting to enable or disable receiving + a new button to create manually the device)
- Viking 02811 temperature sensor now supported
- fix for DisplayStatus definition in json files for better compatibility with Automator app
- Chris's code relative to security added ("tripped" status is now updated for X10 door sensors and X10 motion sensors)

Still missing before I release the new version: the implementation of the UV sensor.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 08, 2012, 03:52:27 am
Dear Lolodomo

Quote
You get no RFXtrx error messages in the logs ?
One idea could be that you did not upload all the files included in my zip files. Go in Apps => Developer apps => Luup files and check if you find all the files.

After a factory reset I installed al 13 files, except the L_RFXtrx.lua file but without succes.

These are the errors mentioned in the errors Log:
2012-06-07_21:22:17 [erase_part_schema] WARNING: We'll RAW ERASE disc: /dev/sda, having: 3913192 sectors
2012-06-07_21:22:17 [is_usb_plugged] WARNING: Found UNPARTITIONED USB STICK Connected
2012-06-07_21:22:33 (/dev/sda1) : Successfully checked
2012-06-07_21:22:33 CHECKDISK: Starting to check device: /dev/sda1 with: /usr/sbin/e2fsck

I hope you can help me
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 08, 2012, 06:31:31 am
Dear Lolodomo

Quote
You get no RFXtrx error messages in the logs ?
One idea could be that you did not upload all the files included in my zip files. Go in Apps => Developer apps => Luup files and check if you find all the files.

After a factory reset I installed al 13 files, except the L_RFXtrx.lua file but without succes.

This file must be installed like others, this is the main file of the plugin.

{quote]These are the errors mentioned in the errors Log:
2012-06-07_21:22:17 [erase_part_schema] WARNING: We'll RAW ERASE disc: /dev/sda, having: 3913192 sectors
2012-06-07_21:22:17 [is_usb_plugged] WARNING: Found UNPARTITIONED USB STICK Connected
2012-06-07_21:22:33 (/dev/sda1) : Successfully checked
2012-06-07_21:22:33 CHECKDISK: Starting to check device: /dev/sda1 with: /usr/sbin/e2fsck

I hope you can help me

No log relative to RFXtrx plugin ?
It looks like you have other problems with an USB stick not partitionned. Do you have several USB devices connected ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on June 08, 2012, 01:47:15 pm
Now added in the next release coming soon:
- RollerTrol added (including a new setting to enable or disable receiving + a new button to create manually the device)
- Viking 02811 temperature sensor now supported
- fix for DisplayStatus definition in json files for better compatibility with Automator app
- Chris's code relative to security added ("tripped" status is now updated for X10 door sensors and X10 motion sensors)

Still missing before I release the new version: the implementation of the UV sensor.

just discovered a sh264 remote control (x10), trying to implement code for it by the next release. when are you planning to publish your new code ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 08, 2012, 03:41:07 pm
when are you planning to publish your new code ?

I was planning to do it today ... or tomorrow.
Coding for UV sensor is now done, I have now just few tests to do...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 08, 2012, 04:10:38 pm
I just released the version alpha 4.

What's new in version alpha 4:
- plugin is up to date with RFXtrx firmware v42
- RollerTrol supported (including a new setting to enable or disable receiving + a new button to create manually the Vera device)
- UV sensors supported
- Viking 02811 temperature sensor supported
- Chris's code relative to X10 security added ("tripped" status is now updated for X10 door sensors and X10 motion sensors)
- fix for DisplayStatus definition in json files for better compatibility with Automator app

Please find the ZIP file attached in the first message of this topic.

And don't forget to give feedback 8)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: automator.app on June 08, 2012, 04:49:01 pm

- fix for DisplayStatus definition in json files for better compatibility with Automator app

Thanks!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 08, 2012, 04:54:56 pm
Next step now is to upload files to code.mios.com, create a description/help page and finally make the plugin available in the app store
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: asbkar on June 09, 2012, 05:16:18 am
Just a thank you from me too. Both alpha3 and 4 is working great with my vera lite and a couple of oregon temp-devices. Will get the THWR800 pool thermometer on monday. Controlling my vera with homebuddy on android, and temps are showing up fine.

Karl Erik
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 10, 2012, 05:32:56 am
Sources are now available here: http://code.mios.com/svn_public/mios_rfxtrx
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on June 10, 2012, 02:54:17 pm
Just tested the Comfort Remote Control from Marmitek (reference SH624)
the bottom buttons are all recognized as light switches by your code, so that's fine.
The button about bright is yet not recognized:
up:
02   06/10/12 20:52:22.838   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 3 <0x2ef01680>
02   06/10/12 20:52:22.838   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 3D 41 00 03 60  <0x2ef01680>
down:
02   06/10/12 20:53:00.598   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 2 <0x2ef01680>
02   06/10/12 20:53:00.598   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 41 41 00 02 50  <0x2ef0168

The "All lamps" button is issuing a special code:
02   06/10/12 20:37:18.718   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 6 <0x2ef01680>
02   06/10/12 20:37:18.718   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 00 41 00 06 50

For the "Arm/disarm Away", it is not recognized as for now, but it should be with my new code, by tomorrow:
02      06/10/12 20:40:26.848   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 0C 84 8B 64 09 59  <0x2ef01680>
same for the "Arm/disarm Home" :
02   06/10/12 20:42:11.058   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 12 84 8B 64 0B 59  <0x2ef01680>

as well as for the "panic" button:
02   06/10/12 20:45:00.638   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 20 84 8B 64 06 69  <0x2ef01680>
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 10, 2012, 04:14:57 pm
Dear Lolodomo

Quote
This file must be installed like others, this is the main file of the plugin.

From your first message I understood  that it was not required to upload L_RFXtrx.lua with the last UI5 firmware. I now included the file and it is working. Thank you for your assistance.

I would be a very happy person if you or someone else write a plugin for the LaCrosse weather station WS-3600. Unfortunately I am not a programmer otherwise I would have write the plugin.

Did you implement the Koppla from Ikea already?

Regards
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 10, 2012, 04:19:30 pm
Hello Chris.

Just tested the Comfort Remote Control from Marmitek (reference SH624)
the bottom buttons are all recognized as light switches by your code, so that's fine.
The button about bright is yet not recognized:
up:
02   06/10/12 20:52:22.838   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 3 <0x2ef01680>
02   06/10/12 20:52:22.838   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 3D 41 00 03 60  <0x2ef01680>
down:
02   06/10/12 20:53:00.598   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 2 <0x2ef01680>
02   06/10/12 20:53:00.598   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 41 41 00 02 50  <0x2ef0168

Yes, that's true, dim and bright commands are not handled. What could be the expected result on Vera device when receiving these commands ?
What is the result on the light ? Dim command reduces the brightness and bright command increases the brightness ? These commands are for dimmable lights ?

Quote
The "All lamps" button is issuing a special code:
02   06/10/12 20:37:18.718   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 6 <0x2ef01680>
02   06/10/12 20:37:18.718   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 00 41 00 06 50

With X10, how is working the "all on" and "all off" commands ? Does it impact every X10 devices or only devices you setup in a way or another ?

Quote
For the "Arm/disarm Away", it is not recognized as for now, but it should be with my new code, by tomorrow:
02      06/10/12 20:40:26.848   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 0C 84 8B 64 09 59  <0x2ef01680>
same for the "Arm/disarm Home" :
02   06/10/12 20:42:11.058   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 12 84 8B 64 0B 59  <0x2ef01680>

as well as for the "panic" button:
02   06/10/12 20:45:00.638   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 20 84 8B 64 06 69  <0x2ef01680>

 8)
That would be cool to have a full X10 support in the v1.0.

I was thinking about security and maybe we should conform to the standard defined for the alarm panels ? When you arm or disarm, is it for a specific X10 device or is it a global command for all X10 security devices ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 10, 2012, 04:31:42 pm
From your first message I understood  that it was not required to upload L_RFXtrx.lua with the last UI5 firmware. I now included the file and it is working. Thank you for your assistance.

I should have been clearer in my explanations. With the last firmware, the lua file can be uploaded like others.

Quote
I would be a very happy person if you or someone else write a plugin for the LaCrosse weather station WS-3600. Unfortunately I am not a programmer otherwise I would have write the plugin.

Few La Crosse sensors are supported by the RFXtrx and by the plugin: http://www.rfxcom.com/oregon.htm
TX3, TX3P, TX4, TX7, TX17

Quote
Did you implement the Koppla from Ikea already?

No but I can do it if you can test it.
I just need understanding how does it work. It looks like there is a system code + a channel (from 1 to 10) ? Each device uses a dedicated channel ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on June 10, 2012, 05:41:29 pm
Hello Chris.

Just tested the Comfort Remote Control from Marmitek (reference SH624)
the bottom buttons are all recognized as light switches by your code, so that's fine.
The button about bright is yet not recognized:
up:
02   06/10/12 20:52:22.838   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 3 <0x2ef01680>
02   06/10/12 20:52:22.838   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 3D 41 00 03 60  <0x2ef01680>
down:
02   06/10/12 20:53:00.598   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 2 <0x2ef01680>
02   06/10/12 20:53:00.598   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 41 41 00 02 50  <0x2ef0168

Yes, that's true, dim and bright commands are not handled. What could be the expected result on Vera device when receiving these commands ?
What is the result on the light ? Dim command reduces the brightness and bright command increases the brightness ? These commands are for dimmable lights ?
This is what I understand, but there's a unique bright/dim button for all lights, as I don't have such devices I'm wondering how it is supposed to work, and the documentation from Marmitek does not help much
Quote

Quote
The "All lamps" button is issuing a special code:
02   06/10/12 20:37:18.718   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 6 <0x2ef01680>
02   06/10/12 20:37:18.718   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 00 41 00 06 50

With X10, how is working the "all on" and "all off" commands ? Does it impact every X10 devices or only devices you setup in a way or another ?
I do think it is supposed to send a message to some central systems, where we have identify what the "all" means. So kind of a switchable stuff, I will have to put X10 dimmable lights to really see how does it works. If someone have a full Marmitek installation, it would be kind to help us there. So far on my side, I will just use the SH264 as a generic remote
Quote

Quote
For the "Arm/disarm Away", it is not recognized as for now, but it should be with my new code, by tomorrow:
02      06/10/12 20:40:26.848   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 0C 84 8B 64 09 59  <0x2ef01680>
same for the "Arm/disarm Home" :
02   06/10/12 20:42:11.058   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 12 84 8B 64 0B 59  <0x2ef01680>

as well as for the "panic" button:
02   06/10/12 20:45:00.638   luup_log:34: RFXtrx: Decoding not yet implemented for message 08 20 02 20 84 8B 64 06 69  <0x2ef01680>

 8)
That would be cool to have a full X10 support in the v1.0.

I was thinking about security and maybe we should conform to the standard defined for the alarm panels ? When you arm or disarm, is it for a specific X10 device or is it a global command for all X10 security devices ?
I understand it is a sort of switch for a Security station, which arm/disarm two variables : "Home" et "Away". "Panic" is supposed to make every alerts being triggered, including souding alarm (PowerHorn, Ph7208).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 11, 2012, 08:08:47 am
Chris, we could try to get more information about X10 security from Bert ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on June 11, 2012, 08:27:02 am
Chris, we could try to get more information about X10 security from Bert ?

I have discussed the element with Bert, two months ago on a generic topic, but some of the points are not matching with the reality of the SH264.
So yes, I will get back to Bert, and see how we could move forward.
I've created the extensions of the RFXTRX.lua for the RemoteControl security managing arm/disarm of home & away as well as panic button, into a new sub-device called RemoteSecurity. It seems that the related variables ("Home", "Away", "Panic") are not UPnP described, so it means we have to generate these under our own namespace, or use x10 namespace but I don't know what is the policy at Micasaverde for this topic.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 11, 2012, 09:07:57 am
You may check how the plugins for alarm panels are managing arm home, arm away and other commands. I think you should conform to the standard that was defined, if it is relevant for X10. That would allow an automatic compatibility with mobile applications for example.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 12, 2012, 07:16:10 am


Quote
Did you implement the Koppla from Ikea already?

No but I can do it if you can test it.
I just need understanding how does it work. It looks like there is a system code + a channel (from 1 to 10) ? Each device uses a dedicated channel ?

I am willing to test your plugin if you tell me what to do.
You can find the instructions of Koppla on http://www.ikeafans.com/forums/workspaces/39791-owners-manual-koppla-bedienungsanleitung.html
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 12, 2012, 08:07:56 am
I take a look to the user manual.
As I suspected, there is one channel per receiver.
System code is probably the id of the remote.
I see that you can select several channels with the remote (in a group or not).
So I will create one device for each couple (remote, channel) and all commands from the remote will automatically uopdate the Vera devices. Fron the Vera, you will be able to send command only from one device (light) - one by one.
I will assume that bright and dim commands increases and decreases from 10%.
If you set level to 50% for a light, then do OFF and then ON, what is level ? 50% or 100 % ?
Edit: manual says level is memorized.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 12, 2012, 09:20:18 am
I take a look to the user manual.
As I suspected, there is one channel per receiver.
System code is probably the id of the remote.
I see that you can select several channels with the remote (in a group or not).
So I will create one device for each couple (remote, channel) and all commands from the remote will automatically uopdate the Vera devices. Fron the Vera, you will be able to send command only from one device (light) - one by one.
I will assume that bright and dim commands increases and decreases from 10%.
If you set level to 50% for a light, then do OFF and then ON, what is level ? 50% or 100 % ?
Edit: manual says level is memorized.

As far as I can see the dimmer works with the range of 0% to 100% in 30 steps. Every third step a dash is added on the LCD screen of the receiver when increasing or a dash disappears when decreasing. At full load the On symbol  (a light bulb) appears on the LCD screen.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 12, 2012, 01:59:30 pm
I take a look to the user manual.
As I suspected, there is one channel per receiver.
System code is probably the id of the remote.
I see that you can select several channels with the remote (in a group or not).
So I will create one device for each couple (remote, channel) and all commands from the remote will automatically uopdate the Vera devices. Fron the Vera, you will be able to send command only from one device (light) - one by one.
I will assume that bright and dim commands increases and decreases from 10%.
If you set level to 50% for a light, then do OFF and then ON, what is level ? 50% or 100 % ?
Edit: manual says level is memorized.

As far as I can see the dimmer works with the range of 0% to 100% in 30 steps. Every third step a dash is added on the LCD screen of the receiver when increasing or a dash disappears when decreasing. At full load the On symbol  (a light bulb) appears on the LCD screen.

The RFXtrx interface defines only 9 levels. I assume that:
OFF = 0%
Level 1 = 10%
Level 2 = 20%
...
Level 9 = 90%
ON = 100%

I will provide an initial partial support, for testing. Mulitple channels in one command will not be managed in this version because it requires a more in depth update of my code.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: MartijnK on June 12, 2012, 02:42:38 pm
Is it possible to (permantly) remove/hide a device?

I am picking up my neighbours temperature sensor, i want to get rid of it in my Vera UI.
I tried the trash icon, but it comes back automaticly.

thanks
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Quinten on June 13, 2012, 04:05:59 am
Is it possible to (permantly) remove/hide a device?

I am picking up my neighbours temperature sensor, i want to get rid of it in my Vera UI.
I tried the trash icon, but it comes back automaticly.

thanks

Once you've got all your devices added, set the AutoCreate variable to 0.  Then delete the roque device and it it won't be created again...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: MartijnK on June 13, 2012, 07:08:47 am

Is it possible to (permantly) remove/hide a device?

I am picking up my neighbours temperature sensor, i want to get rid of it in my Vera UI.
I tried the trash icon, but it comes back automaticly.

thanks

Once you've got all your devices added, set the AutoCreate variable to 0.  Then delete the roque device and it it won't be created again...

Will give that a try.

Thanks for the suggestion!

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: gibbo on June 13, 2012, 07:10:59 am
Is it possible to (permantly) remove/hide a device?

I am picking up my neighbours temperature sensor, i want to get rid of it in my Vera UI.
I tried the trash icon, but it comes back automaticly.

thanks

Or find a use for your neighbours temperature sensor in your system!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: strangely on June 13, 2012, 07:30:03 pm
Mine is also picking up quite a few other devices locally, I've left them so far out of curiosity value, mainly to compare to the readings that my sensors are giving! However good to know that you can turn discovery off!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: blooby78 on June 15, 2012, 09:45:45 am
Hello lolodomo,

Nice job.

I have order a KR21 X10 telecommande http://www.maisondunumerique.com/telecommande-porte-cle-kr21-de-marmitek.html (http://www.maisondunumerique.com/telecommande-porte-cle-kr21-de-marmitek.html), and i would like to know if it is compatible with your plugin ?

Thanks.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 06:02:29 am
Hello lolodomo,

Nice job.

I have order a KR21 X10 telecommande http://www.maisondunumerique.com/telecommande-porte-cle-kr21-de-marmitek.html (http://www.maisondunumerique.com/telecommande-porte-cle-kr21-de-marmitek.html), and i would like to know if it is compatible with your plugin ?

Thanks.

Not yet but read the previous page, Chris (cboulang) is working on X10 security support.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 06:07:26 am
Chris, we could try to get more information about X10 security from Bert ?

I have discussed the element with Bert, two months ago on a generic topic, but some of the points are not matching with the reality of the SH264.
So yes, I will get back to Bert, and see how we could move forward.
I've created the extensions of the RFXTRX.lua for the RemoteControl security managing arm/disarm of home & away as well as panic button, into a new sub-device called RemoteSecurity. It seems that the related variables ("Home", "Away", "Panic") are not UPnP described, so it means we have to generate these under our own namespace, or use x10 namespace but I don't know what is the policy at Micasaverde for this topic.

Chris, I take a look to the protocol specification again and it looks like the X10 security commands are global commands, not commands addressing a specific device.
For lights, it looks like the remote can control two lights (ON/OFF): light 1 and light 2. I could easily add the support for this. But you might have already integrated it ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 06:16:03 am
Chris, for security, I still think we should use the standard that was defined: http://forum.micasaverde.com/index.php/topic,3713.0.html
Check S_AlarmPartition2.xml
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 07:24:25 am
Adrian (rollertrol), no feedback from the last version ? Does RollerTrol works or not ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 08:35:16 am
Johan,

I added initial support for Ikea Koppla. Try with the attached file (do a usual install starting from the version alpha 4 and replace the lua file with the attached file) and give me a feedback.

Here is the status:
- ON/OFF commands from your remote should create and update the Vera switch/light devices
- you should be able to run ON/OFF commands from the Vera switch/light devices
- multi-channels (or group) commands from remote are not yet managed, only the lowest channel will be taken into account
- I have implemented the 9 intermediate levels commands for dimmable lights but I am not sure that the corresponding commands can be produced from your remote, so maybe you should not be able to play with dimmable lights. If you can produce these commands with the remote or with the RFXCOM application, please tell me if LEVEL_1 is 10% or 90% bright.
- bright and dim commands are not yet managed
- manual creation of devices is not yet provided

Don't forget to enable Koppla receiving.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 09:25:07 am
For people using X10 security remotes, I just added support for light1 and light2 ON/OFF commands.
Please try with the attached file (do a usual install starting from the version alpha 4 and replace the lua file with the attached file) and give me a feedback.

The commands ON/OFF from your remote for light 1 and light 2 should create and then update a Vera switch/light device. Then you should be able to use the ON/OFF commands from the Vera device in place of your remote.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 09:37:00 am
Johan,

I added initial support for Ikea Koppla. Try with the attached file and give me a feedback.

Here is the status:
- ON/OFF commands from your remote should create and update the Vera switch/light devices
- you should be able to run ON/OFF commands from the Vera switch/light devices
- multi-channels (or group) commands from remote are not yet managed, only the lowest channel will be taken into account
- I have implemented the 9 intermediate levels commands for dimmable lights but I am not sure that the corresponding commands can be produced from your remote, so maybe you should not be able to play with dimmable lights. If you can produce these commands with the remote or with the RFXCOM application, please tell me if LEVEL_1 is 10% or 90% bright.
- bright and dim commands are not yet managed
- manual creation of devices is not yet provided

Don't forget to enable Koppla receiving.

OK, as a start I use two switches. 2 is a ON/OF switch and 1 a dimmer. With the Koppla remote I have set the channels 2 for the switch and 1 for the dimmer.
How do I configure the devices with the RFXtrx controller?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 09:44:13 am
How do I configure the devices with the RFXtrx controller?

First, be sure to enable Koppla receiving by the RFXtrx from the "Settings" panel of the Vera device "RFXtrx controller device" and save.
Then, just use your usual remote to play with switch 1 and 2 and see if devices are created in the dashboard and then updated in regards to your remote commands.
After that, you can leave your remote and check if you can control your two switches from the new Vera devices.

If nothing happens, please send me logs (grep RFXtrx in the log file to get only lines correspondng to my plugin).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 10:00:48 am
How do I configure the devices with the RFXtrx controller?

First, be sure to enable Koppla receiving by the RFXtrx from the "Settings" panel of the Vera device "RFXtrx controller device" and save.
Then, just use your usual remote to play with switch 1 and 2 and see if devices are created in the dashboard and then updated in regards to your remote commands.
After that, you can leave your remote and check if you can control your two switches from the new Vera devices.

If nothing happens, please send me logs (grep RFXtrx in the log file to get only lines correspondng to my plugin).

As you already know I am A Rookie. In the Advanced screen of the RFXtrx controller I can see IkeaReceiving withe the value 1.
In the settings screen of the RFXtrx controller Ikea-Koppla is enabled. I the reloaded the Lua.
Within a range off less the a metre from the RFXtrx controller I used the Ikea controller to switch  receiver 2 to ON and Off. Nothing happened. No device was created.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 10:08:54 am
and no logs were created.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 10:10:37 am
How do I configure the devices with the RFXtrx controller?

First, be sure to enable Koppla receiving by the RFXtrx from the "Settings" panel of the Vera device "RFXtrx controller device" and save.
Then, just use your usual remote to play with switch 1 and 2 and see if devices are created in the dashboard and then updated in regards to your remote commands.
After that, you can leave your remote and check if you can control your two switches from the new Vera devices.

If nothing happens, please send me logs (grep RFXtrx in the log file to get only lines correspondng to my plugin).

As you already know I am A Rookie. In the Advanced screen of the RFXtrx controller I can see IkeaReceiving withe the value 1.
In the settings screen of the RFXtrx controller Ikea-Koppla is enabled. I the reloaded the Lua.

Ok, what you say let me think that the plugin is well installed and you have enable Koppla receiving. For your information you can check and change the receiving in the first panel, it is more graphical than the advanced panel.

Quote
Within a range off less the a metre from the RFXtrx controller I used the Ikea controller to switch  receiver 2 to ON and Off. Nothing happened. No device was created.

If you have correcly installed the new lua file, the version displayed in the dashboard on the main RFXtrx controller should be "alpha 5". Is it the case ?
If all this is ok, next step would be to check the log file searching for RFXtrx messages.

Something else you can try first is to check that your RFXtrx device is working well with Koppla using the RFXCOM test applications. With this application, you should see messages coming when using your remote. If nothing happens with this application, nothing will happen with the plugin.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 10:17:58 am
and no logs were created.

If the plugin is correctly installed, you should have few logs each time the lua engine is reloaded. Then logs will occur only when new messages are received.

Here is what you should have, at least at starting of the plugin (it proves that the plugin is ready):

Code: [Select]
50      06/16/12 16:15:31.467   luup_log:203: RFXtrx: loading library L_RFXtrx ... <0x2bbe9680>
50      06/16/12 16:15:31.600   luup_log:203: RFXtrx: library L_RFXtrx loaded <0x2bbe9680>
50      06/16/12 16:15:31.601   luup_log:203: RFXtrx: Starting RFXtrx device: 203 <0x2bbe9680>
50      06/16/12 16:15:31.602   luup_log:203: RFXtrx: Serial port is connected <0x2bbe9680>
50      06/16/12 16:15:31.603   luup_log:203: RFXtrx: Baud is 38400 <0x2bbe9680>
50      06/16/12 16:15:31.616   luup_log:203: RFXtrx: Tree with number child devices: 0 <0x2bbe9680>
50      06/16/12 16:15:31.617   luup_log:203: RFXtrx:        door sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.617   luup_log:203: RFXtrx:      motion sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.617   luup_log:203: RFXtrx:      light switches: 0 <0x2bbe9680>
50      06/16/12 16:15:31.618   luup_log:203: RFXtrx:  dim light switches: 0 <0x2bbe9680>
50      06/16/12 16:15:31.618   luup_log:203: RFXtrx:     window covering: 0 <0x2bbe9680>
50      06/16/12 16:15:31.619   luup_log:203: RFXtrx: temperature sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.619   luup_log:203: RFXtrx:    humidity sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.620   luup_log:203: RFXtrx:  barometric sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.620   luup_log:203: RFXtrx:        wind sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.620   luup_log:203: RFXtrx:        rain sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.621   luup_log:203: RFXtrx:          UV sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.621   luup_log:203: RFXtrx:       power sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.622   luup_log:203: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2bbe9680>
50      06/16/12 16:15:31.724   luup_log:203: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2bbe9680>
50      06/16/12 16:15:31.725   luup_log:203: RFXtrx: RFXtrx is ready <0x2bbe9680>
50      06/16/12 16:15:31.747   luup_log:203: RFXtrx: Response to a Get Status command or Set Mode command <0x2e216680>

I realize I should log what protocols receiving is enabled too.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on June 16, 2012, 11:24:02 am
Hi @lolodomo, unfortunately I did not get your query about your new RFXCOM plugin working with our RollerTrol blind and shade motors, because I don't monitor this particular thread, although I will start doing that now. Thanks to Bert at RFXCOM for letting me know about this.

Most of my communications will be on the thread below, though, in an attempt to keep topics more specific:

http://forum.micasaverde.com/index.php/topic,9555.0.html

To be perfectly honest with you, I had not realized it was ready and I have been away visiting my family in Regina. So I'm back now and I'll get busy with it shortly, and I'll post the results to the above thread.

Regards, Adrian

Adrian Biffen
Customer Service
RollerTrol Automation Systems
http://RollerTrol.com/

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 12:07:32 pm
How do I configure the devices with the RFXtrx controller?


If you have correcly installed the new lua file, the version displayed in the dashboard on the main RFXtrx controller should be "alpha 5". Is it the case ?
If all this is ok, next step would be to check the log file searching for RFXtrx messages.

Something else you can try first is to check that your RFXtrx device is working well with Koppla using the RFXCOM test applications. With this application, you should see messages coming when using your remote. If nothing happens with this application, nothing will happen with the plugin.

Yes "alpha 5" is displayed.

Where can I get the RFXcom test application?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 12:13:30 pm
and no logs were created.

If the plugin is correctly installed, you should have few logs each time the lua engine is reloaded. Then logs will occur only when new messages are received.

Here is what you should have, at least at starting of the plugin (it proves that the plugin is ready):

Code: [Select]
50      06/16/12 16:15:31.467   luup_log:203: RFXtrx: loading library L_RFXtrx ... <0x2bbe9680>
50      06/16/12 16:15:31.600   luup_log:203: RFXtrx: library L_RFXtrx loaded <0x2bbe9680>
50      06/16/12 16:15:31.601   luup_log:203: RFXtrx: Starting RFXtrx device: 203 <0x2bbe9680>
50      06/16/12 16:15:31.602   luup_log:203: RFXtrx: Serial port is connected <0x2bbe9680>
50      06/16/12 16:15:31.603   luup_log:203: RFXtrx: Baud is 38400 <0x2bbe9680>
50      06/16/12 16:15:31.616   luup_log:203: RFXtrx: Tree with number child devices: 0 <0x2bbe9680>
50      06/16/12 16:15:31.617   luup_log:203: RFXtrx:        door sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.617   luup_log:203: RFXtrx:      motion sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.617   luup_log:203: RFXtrx:      light switches: 0 <0x2bbe9680>
50      06/16/12 16:15:31.618   luup_log:203: RFXtrx:  dim light switches: 0 <0x2bbe9680>
50      06/16/12 16:15:31.618   luup_log:203: RFXtrx:     window covering: 0 <0x2bbe9680>
50      06/16/12 16:15:31.619   luup_log:203: RFXtrx: temperature sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.619   luup_log:203: RFXtrx:    humidity sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.620   luup_log:203: RFXtrx:  barometric sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.620   luup_log:203: RFXtrx:        wind sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.620   luup_log:203: RFXtrx:        rain sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.621   luup_log:203: RFXtrx:          UV sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.621   luup_log:203: RFXtrx:       power sensors: 0 <0x2bbe9680>
50      06/16/12 16:15:31.622   luup_log:203: RFXtrx: Sending command: 0D 00 00 00 00 00 00 00 00 00 00 00 00 00  <0x2bbe9680>
50      06/16/12 16:15:31.724   luup_log:203: RFXtrx: Sending command: 0D 00 00 01 02 00 00 00 00 00 00 00 00 00  <0x2bbe9680>
50      06/16/12 16:15:31.725   luup_log:203: RFXtrx: RFXtrx is ready <0x2bbe9680>
50      06/16/12 16:15:31.747   luup_log:203: RFXtrx: Response to a Get Status command or Set Mode command <0x2e216680>

I realize I should log what protocols receiving is enabled too.

Something is going wrong with logging. The only information I see is this:

Logs
x  Show polling activity
x  Show individual jobs
x  Verbose logging (May cause system instability if you're not using USB logging)
x  Lock Log Levels (not recommended)
    Archive old logs on server (recommended) learn more
x  Store logs on USB device*

WARNING: please do not remove USB stick while Vera is running.
USB status
Enabled
Mounted: read-write
Usage: 6%
Errors log:
2012-06-16_18:02:35 CHECKDISK: Starting to check device: /dev/sda1 with: /usr/sbin/e2fsck
2012-06-16_18:02:36 (/dev/sda1) : Successfully checked
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 12:25:00 pm
You are looking at the setup logs options in the dashboard.
To get the logs, here is a page explaining how to get them: http://wiki.micasaverde.com/index.php/Logs
First, you need to ssh to the Vera: http://wiki.micasaverde.com/index.php/Logon_Vera_SSH
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 12:29:04 pm
Johan, RFXCOM application can be downloaded here:  http://rfxcom.com/downloads.htm
It is the file named RFXmngr.zip.
Title: Plugin for the USB RFXtrx from RFXCOM
Post by: Brientim on June 16, 2012, 02:20:44 pm
@Johan, you may want to look at dataMine see http://forum.micasaverde.com/index.php/topic,7750.0.html
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 05:41:55 pm
You are looking at the setup logs options in the dashboard.
To get the logs, here is a page explaining how to get them: http://wiki.micasaverde.com/index.php/Logs
First, you need to ssh to the Vera: http://wiki.micasaverde.com/index.php/Logon_Vera_SSH

I managed to read the log. I selected code 50 and this is what I get:

50   06/16/12 23:27:53.343   luup_log:26: RFXtrx: W5/2562: cmds Direction 270 Gust 15 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:29:53.344   luup_log:26: RFXtrx: W5/2562: cmds Direction 247 Gust 8 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:31:53.374   luup_log:26: RFXtrx: W5/2562: cmds Direction 292 Gust 14 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:32:51.709   luup_log:26: RFXtrx: TH1/53506: cmds Temperature 15.8 Humidity 48 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:34:13.519   luup_log:26: RFXtrx: TH1/53506: cmds Temperature 15.8 Humidity 48 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:34:21.422   luup_log:26: RFXtrx: switchPower LS/L1.0/O01 target 1 <0x2d7e5680>
50   06/16/12 23:34:21.423   luup_log:26: RFXtrx: Sending command: 07 10 00 02 4F 01 01 00  <0x2d7e5680>
50   06/16/12 23:34:22.085   luup_log:26: RFXtrx: L1.0/O01: cmds On  <0x2ea12680>
50   06/16/12 23:34:30.343   luup_log:26: RFXtrx: switchPower LS/L1.0/O01 target 0 <0x2e7e5680>
50   06/16/12 23:34:30.344   luup_log:26: RFXtrx: Sending command: 07 10 00 03 4F 01 00 00  <0x2e7e5680>
50   06/16/12 23:34:31.015   luup_log:26: RFXtrx: L1.0/O01: cmds Off  <0x2ea12680>



It seems the RFXtrx doesn't receive a thing from The Koppla remote.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 05:43:48 pm
Johan, RFXCOM application can be downloaded here:  http://rfxcom.com/downloads.htm
It is the file named RFXmngr.zip.

I work with a MacBook. The RFXmngr.zip is a windows programm
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 06:16:10 pm
You are looking at the setup logs options in the dashboard.
To get the logs, here is a page explaining how to get them: http://wiki.micasaverde.com/index.php/Logs
First, you need to ssh to the Vera: http://wiki.micasaverde.com/index.php/Logon_Vera_SSH

After trying all 7 receivers, without any succes, RFXtrx suddenly created 2 devices RFX Light L1.1/A01 and L1.1/A02. These devices does not switch one off the Koppla receivers. ???
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 16, 2012, 06:17:48 pm
You are looking at the setup logs options in the dashboard.
To get the logs, here is a page explaining how to get them: http://wiki.micasaverde.com/index.php/Logs
First, you need to ssh to the Vera: http://wiki.micasaverde.com/index.php/Logon_Vera_SSH

After trying all 7 receivers, without any succes, RFXtrx suddenly created 2 devices RFX Light L1.1/A01 and L1.1/A02. These devices does not switch one off the Koppla receivers. ???

Here is the LOG:

50   06/17/12 0:06:26.148   luup_log:26: RFXtrx: RFXtrx is ready <0x2c0f1680>
50   06/17/12 0:06:51.926   luup_log:26: RFXtrx: switchPower LS/L1.1/A01 target 1 <0x2e4f1680>
50   06/17/12 0:06:51.927   luup_log:26: RFXtrx: Sending command: 07 10 01 02 41 01 01 00  <0x2e4f1680>
50   06/17/12 0:06:52.305   luup_log:26: RFXtrx: L1.1/A01: cmds On  <0x2ed1e680>
50   06/17/12 0:06:58.856   luup_log:26: RFXtrx: switchPower LS/L1.1/A01 target 0 <0x2e4f1680>
50   06/17/12 0:06:58.857   luup_log:26: RFXtrx: Sending command: 07 10 01 03 41 01 00 00  <0x2e4f1680>
50   06/17/12 0:06:59.245   luup_log:26: RFXtrx: L1.1/A01: cmds Off  <0x2ed1e680>
50   06/17/12 0:07:01.849   luup_log:26: RFXtrx: TH1/53506: cmds Temperature 15.6 Humidity 51 BatteryLevel 100 <0x2ed1e680>
50   06/17/12 0:07:15.666   luup_log:26: RFXtrx: switchPower LS/L1.1/A01 target 1 <0x2d8f1680>
50   06/17/12 0:07:15.667   luup_log:26: RFXtrx: Sending command: 07 10 01 04 41 01 01 00  <0x2d8f1680>
50   06/17/12 0:07:16.055   luup_log:26: RFXtrx: L1.1/A01: cmds On  <0x2ed1e680>
50   06/17/12 0:07:18.927   luup_log:26: RFXtrx: switchPower LS/L1.1/A01 target 0 <0x2eaf1680>
50   06/17/12 0:07:18.928   luup_log:26: RFXtrx: Sending command: 07 10 01 05 41 01 00 00  <0x2eaf1680>
50   06/17/12 0:07:19.315   luup_log:26: RFXtrx: L1.1/A01: cmds Off  <0x2ed1e680>
50   06/17/12 0:07:21.662   luup_log:26: RFXtrx: switchPower LS/L1.1/A02 target 1 <0x2e4f1680>
50   06/17/12 0:07:21.663   luup_log:26: RFXtrx: Sending command: 07 10 01 06 41 02 01 00  <0x2e4f1680>
50   06/17/12 0:07:21.905   luup_log:26: RFXtrx: L1.1/A02: cmds On  <0x2ed1e680>
50   06/17/12 0:07:25.441   luup_log:26: RFXtrx: switchPower LS/L1.1/A02 target 0 <0x2eaf1680>
50   06/17/12 0:07:25.442   luup_log:26: RFXtrx: Sending command: 07 10 01 07 41 02 00 00  <0x2eaf1680>
50   06/17/12 0:07:25.835   luup_log:26: RFXtrx: L1.1/A02: cmds Off  <0x2ed1e680>
50   06/17/12 0:09:07.139   luup_log:26: RFXtrx: switchPower LS/L1.1/A02 target 1 <0x2e4f1680>
50   06/17/12 0:09:07.140   luup_log:26: RFXtrx: Sending command: 07 10 01 08 41 02 01 00  <0x2e4f1680>
50   06/17/12 0:09:07.525   luup_log:26: RFXtrx: L1.1/A02: cmds On  <0x2ed1e680>
50   06/17/12 0:09:14.203   luup_log:26: RFXtrx: switchPower LS/L1.1/A01 target 1 <0x2e8f1680>
50   06/17/12 0:09:14.204   luup_log:26: RFXtrx: Sending command: 07 10 01 09 41 01 01 00  <0x2e8f1680>
50   06/17/12 0:09:14.595   luup_log:26: RFXtrx: L1.1/A01: cmds On  <0x2ed1e680>
50   06/17/12 0:09:26.387   luup_log:26: RFXtrx: L1.1/A01: cmds Off  <0x2ed1e680>
50   06/17/12 0:09:27.717   luup_log:26: RFXtrx: L1.1/A02: cmds Off  <0x2ed1e680>
50   06/17/12 0:09:53.893   luup_log:26: RFXtrx: W5/2562: cmds Direction 247 Gust 16 BatteryLevel 100 <0x2ed1e680>
50   06/17/12 0:10:53.733   luup_log:26: RFXtrx: W5/2562: cmds Direction 270 Gust 19 BatteryLevel 100 <0x2ed1e680>
50   06/17/12 0:11:25.828   luup_log:26: RFXtrx: switchPower LS/L1.1/A01 target 1 <0x2e8f1680>
50   06/17/12 0:11:25.829   luup_log:26: RFXtrx: Sending command: 07 10 01 0A 41 01 01 00  <0x2e8f1680>
50   06/17/12 0:11:26.215   luup_log:26: RFXtrx: L1.1/A01: cmds On  <0x2ed1e680>
50   06/17/12 0:11:31.756   luup_log:26: RFXtrx: switchPower LS/L1.1/A01 target 0 <0x2e4f1680>
50   06/17/12 0:11:31.757   luup_log:26: RFXtrx: Sending command: 07 10 01 0B 41 01 00 00  <0x2e4f1680>
50   06/17/12 0:11:32.135   luup_log:26: RFXtrx: L1.1/A01: cmds Off  <0x2ed1e680>
50   06/17/12 0:11:34.985   luup_log:26: RFXtrx: switchPower LS/L1.1/A02 target 1 <0x2e4f1680>
50   06/17/12 0:11:34.986   luup_log:26: RFXtrx: Sending command: 07 10 01 0C 41 02 01 00  <0x2e4f1680>
50   06/17/12 0:11:35.365   luup_log:26: RFXtrx: L1.1/A02: cmds On  <0x2ed1e680>
50   06/17/12 0:11:41.556   luup_log:26: RFXtrx: switchPower LS/L1.1/A02 target 0 <0x2e8f1680>
50   06/17/12 0:11:41.557   luup_log:26: RFXtrx: Sending command: 07 10 01 0D 41 02 00 00  <0x2e8f1680>
50   06/17/12 0:11:41.945   luup_log:26: RFXtrx: L1.1/A02: cmds Off  <0x2ed1e680>

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 06:21:22 pm
You are looking at the setup logs options in the dashboard.
To get the logs, here is a page explaining how to get them: http://wiki.micasaverde.com/index.php/Logs
First, you need to ssh to the Vera: http://wiki.micasaverde.com/index.php/Logon_Vera_SSH

I managed to read the log. I selected code 50 and this is what I get:

50   06/16/12 23:27:53.343   luup_log:26: RFXtrx: W5/2562: cmds Direction 270 Gust 15 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:29:53.344   luup_log:26: RFXtrx: W5/2562: cmds Direction 247 Gust 8 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:31:53.374   luup_log:26: RFXtrx: W5/2562: cmds Direction 292 Gust 14 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:32:51.709   luup_log:26: RFXtrx: TH1/53506: cmds Temperature 15.8 Humidity 48 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:34:13.519   luup_log:26: RFXtrx: TH1/53506: cmds Temperature 15.8 Humidity 48 BatteryLevel 100 <0x2ea12680>
50   06/16/12 23:34:21.422   luup_log:26: RFXtrx: switchPower LS/L1.0/O01 target 1 <0x2d7e5680>
50   06/16/12 23:34:21.423   luup_log:26: RFXtrx: Sending command: 07 10 00 02 4F 01 01 00  <0x2d7e5680>
50   06/16/12 23:34:22.085   luup_log:26: RFXtrx: L1.0/O01: cmds On  <0x2ea12680>
50   06/16/12 23:34:30.343   luup_log:26: RFXtrx: switchPower LS/L1.0/O01 target 0 <0x2e7e5680>
50   06/16/12 23:34:30.344   luup_log:26: RFXtrx: Sending command: 07 10 00 03 4F 01 00 00  <0x2e7e5680>
50   06/16/12 23:34:31.015   luup_log:26: RFXtrx: L1.0/O01: cmds Off  <0x2ea12680>



It seems the RFXtrx doesn't receive a thing from The Koppla remote.

Ok, with your traces, I see that the plugin is working.
Please filter on "RFXtrx" rather than code 50, I am not sure but I think that warnings and errors will produce lines not starting with 50.
Can you check if you have message contraining "RFXtrx: Decoding not yet implemented for message".

Please retry with the new attached file, I have added new log messages.
Check if you have this message after a reload: "RFXtrx:    - Ikea Koppla"

Check if you have these messages after sending ON or OFF command from your remote:
"RFXtrx: Koppla message received with command code: "
"RFXtrx: Lighting3 command not yet implemented: "
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 16, 2012, 06:25:47 pm
You are looking at the setup logs options in the dashboard.
To get the logs, here is a page explaining how to get them: http://wiki.micasaverde.com/index.php/Logs
First, you need to ssh to the Vera: http://wiki.micasaverde.com/index.php/Logon_Vera_SSH

After trying all 7 receivers, without any succes, RFXtrx suddenly created 2 devices RFX Light L1.1/A01 and L1.1/A02. These devices does not switch one off the Koppla receivers. ???

Your initial traces show that you use X10 lightings too (L1.0) ! Is it true ?

The last traces show that ARC commands (L1.1) were received. Do you have Chacon too ? Or it might be from your neighbours...

What we need is id with L3.0 correspond to Koppla.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on June 16, 2012, 07:12:28 pm
Hi @lolodomo, I'm not having much luck installing the new verstion. I uploaded all the unzipped files, then followed your instructions, but when I look in the device list, all I see are a pair of empty brackets []. This appear to have been created without a name for the device. When I do the 'add device' with D_RFXtrx.xml as the Upnp Device Filename, do I have to adjust any other fields (eg. Parent Device, which has nothing selected)? Also, do I need to delete files from the previous install, that could be interfering? Here's the list:

Device type      
Internal ID    
Description    
Upnp Device Filename      
Upnp Implementation Filename    
Ip Address    
MAC    
Room    --no room --   
Parent device

Tks, Adrian
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 17, 2012, 05:27:13 am
[quote author=lolodomo link=topic=9563.msg76772#msg76772 date=1339863900

Ok, with your traces, I see that the plugin is working.
Please filter on "RFXtrx" rather than code 50, I am not sure but I think that warnings and errors will produce lines not starting with 50.
Can you check if you have message contraining "RFXtrx: Decoding not yet implemented for message".

Please retry with the new attached file, I have added new log messages.
Check if you have this message after a reload: "RFXtrx:    - Ikea Koppla"

Check if you have these messages after sending ON or OFF command from your remote:
"RFXtrx: Koppla message received with command code: "
"RFXtrx: Lighting3 command not yet implemented: "

I installed the new file. After that I tried to read the logfile as you suggested, but I get no log. I waited for more than an hour.


BusyBox v1.17.3 (2012-01-09 12:40:42 PST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M

 -------------- Backfire (10.03) -------------------

 ---------------------------------------------------
  ***        MiOS LTD. ( www.mios.com )        ***
  ***                         ***
  ***               WARNING :                  ***
  *** Any changes made to the system without ***
  *** guidance from MiOS support will VOID   ***
  *** your future Support requests          ***
 ---------------------------------------------------
root@MiOS_xxxxxxxx:~# cd /var/log/cmh
root@MiOS_xxxxxxxx:/tmp/log/cmh# tail -f LuaUPnP.log | grep "^50"
50   06/17/12 10:47:52.200   luup_log:26: RFXtrx: W5/2562: cmds Direction 225 Gust 11 BatteryLevel 100 <0x2eb3a680>
^C
root@MiOS_xxxxxxxx:/tmp/log/cmh# tail -f LuaUPnP.log | grep "^RFXtrx"
^C
root@MiOS_xxxxxxxx:/tmp/log/cmh# tail -f LuaUPnP.log | grep "^RFXtrx:"
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 17, 2012, 05:37:46 am
Your grep command is wrong. This one should work:
Code: [Select]
tail -f LuaUPnP.log | grep "RFXtrx"The RFXtrx word is not at the beginning of the line.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 17, 2012, 05:44:17 am
Hi @lolodomo, I'm not having much luck installing the new verstion. I uploaded all the unzipped files, then followed your instructions, but when I look in the device list, all I see are a pair of empty brackets []. This appear to have been created without a name for the device. When I do the 'add device' with D_RFXtrx.xml as the Upnp Device Filename, do I have to adjust any other fields (eg. Parent Device, which has nothing selected)? Also, do I need to delete files from the previous install, that could be interfering? Here's the list:

Device type      
Internal ID    
Description    
Upnp Device Filename      
Upnp Implementation Filename    
Ip Address    
MAC    
Room    --no room --   
Parent device

Tks, Adrian

No need to delete files first, you have just to upload all the files to replace the all ones, and reload the lua engine.
To create the device, just entering the field "Upnp Device Filename" with D_RFXtrx.xml is enough. Don't forget to reload the lua engine and if necessary to empty the cache of your WEB browser.

1) create the device and reload
2) configure the serial port for the new created device and reload
3) check in the panel of the device that RollerTrol receiving is enabled.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 17, 2012, 07:23:46 am
Your grep command is wrong. This one should work:
Code: [Select]
tail -f LuaUPnP.log | grep "RFXtrx"The RFXtrx word is not at the beginning of the line.

I knew I was doing something wrong. In the attached fil you will find a part of the log after reloading and switching Koppla receivers with the Koppla remote. I can't see the information you requested for.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 17, 2012, 10:01:58 am
The first lines that are intesting me are the two last ones. But next lines are missing. You might have not wait for enough time. Log messages are not immediately flushed into the log file, we can have a little delay. There is an option to set to avoid this problem.

Edit: here is explained how to do to flush logs immediately: http://forum.micasaverde.com/index.php?topic=1672.0

So a new attempt is required to have full logs, especially initial logs after a reload.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 17, 2012, 12:00:55 pm
The first lines that are intesting me are the two last ones. But next lines are missing. You might have not wait for enough time. Log messages are not immediately flushed into the log file, we can have a little delay. There is an option to set to avoid this problem.

Edit: here is explained how to do to flush logs immediately: http://forum.micasaverde.com/index.php?topic=1672.0

So a new attempt is required to have full logs, especially initial logs after a reload.

Here again the logfile. After reload I sent around 17:16:11 several commands with the Koppla remote to the Koppla receivers. More than 30 minutes later still nothing was recorded.

I have checked the log again as you mentioned before but to no avail. The only thing I have found is the row:
function SRFXtrx_rfxtrx1_ReceiveIkea_run(lul_device,lul_settings
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on June 17, 2012, 12:31:31 pm
Ikea Koppla is not supported for receive.
See the RFXtrx433 User guide chapter 2.1. This indicates which protocols are supported for receive and/or transmit.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 17, 2012, 01:34:46 pm
Ikea Koppla is not supported for receive.
See the RFXtrx433 User guide chapter 2.1. This indicates which protocols are supported for receive and/or transmit.

It is true that receive is not supported, but at the top of the table is stated:  "It supports a number of RF protocols in flash memory so that it can easily be upgraded by the user. " That's what Lolodomo is trying to do. :D
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on June 18, 2012, 09:08:12 am
Hi @lolodomo, so I managed to get the RFXCOM plug-in installed, but I'm not happy with how that went. I couldn't actually say what it was that finally made it work, with reboots of Vera and re-starts of Lua. I want to develop a set of bullet proof instructions for our clients, so is it ok to remove the device and re-install it multiple times until I figure out what the exact problem was? I presume I don't have to keep uploading the files each time?

And also, the download link for the plugin zip file at the bottom of your original instruction message seems to have disappeared, do we go to the other link at the top for the files from now on? If so, which folder do we use? (I see /tag and /trunk).

Back to the install, I can now bring up the settings dialog for the RFXCOM device, but when I click 'enable RollerTrol' I get a 'device not ready' message. Does that mean I have to configure it first, or is there something wrong?

Thanks, Adrian
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 19, 2012, 02:36:10 pm
Ikea Koppla is not supported for receive.
See the RFXtrx433 User guide chapter 2.1. This indicates which protocols are supported for receive and/or transmit.

It is true that receive is not supported, but at the top of the table is stated:  "It supports a number of RF protocols in flash memory so that it can easily be upgraded by the user. " That's what Lolodomo is trying to do. :D

So maximum of time lost !
Remark for Bert: it is not really logic to have a setting and a command to enable/disable Ikea Koppla if receiving is not possible.

So the solution is to create manually the devices through the plugin. I have to consult again the Koppla manual to understand if there is a way to pair a switch with a remote.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 19, 2012, 02:41:58 pm
Hi @lolodomo, so I managed to get the RFXCOM plug-in installed, but I'm not happy with how that went. I couldn't actually say what it was that finally made it work, with reboots of Vera and re-starts of Lua. I want to develop a set of bullet proof instructions for our clients, so is it ok to remove the device and re-install it multiple times until I figure out what the exact problem was? I presume I don't have to keep uploading the files each time?

Yes and yes.

Normally, it is very simple.

Quote
And also, the download link for the plugin zip file at the bottom of your original instruction message seems to have disappeared, do we go to the other link at the top for the files from now on? If so, which folder do we use? (I see /tag and /trunk).

That's true, I deleted the attached file because the files are now available on code.mios.com.
Currently, there is no difference between the files in the trunk and the files in the only tag (alpha 4 version).
I corrected the link to point directly to the alpha 4 version.

Quote
Back to the install, I can now bring up the settings dialog for the RFXCOM device, but when I click 'enable RollerTrol' I get a 'device not ready' message. Does that mean I have to configure it first, or is there something wrong?

Don't knwo exactly where your message come from.
But yes, you have to setup first the serial port.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on June 19, 2012, 10:56:20 pm
Hi @lolodomo, I started over and now I see that I probably was moving to fast, not noticing the 'unit busy' message at the top of the screen. I also forgot to restart the Luup files between some of the steps.

It has been installed properly now, with no device errors. I'm ready to start entering the RF codes extracted from the remote and 'learned' by the RFXCOM transceiver with their downloaded software. I'll let you know how it goes.

Thanks, Adrian
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 20, 2012, 03:35:35 am
The easiest way for you woulb be to let the plugin create the device automatically. just use your remote as usual to open or close.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on June 20, 2012, 08:29:09 am
Hi @lolodomo, thanks for that note. I was about to start the somewhat complicated procedure of determining the codes transmitted from my RollerTrol remote with the RFXCOM transceiver software I downloaded. I was thinking that I then had to manually transfer all the codes for up/down/stop for all 15 channels on the remote, a tedious job (but at least it only has to be done once).

If you are saying your plugin will learn them directly, that's very cool, and a big step forward in the 'user friendly' department. I'll give it a try today and let you know how it goes.

Cheers, Adrian

Adrian Biffen
Customer Service
RollerTrol Automation Systems
http://RollerTrol.com/

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 20, 2012, 01:27:57 pm
Just don't forget to enalbe RollerTrol receiving.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: rollertrol on June 21, 2012, 03:18:03 pm
Hi @lolodomo, this is one of those rare moments when something works waaay better than expected :)

I thought I would have a long complicated process to go through, configuring my blind motor to work with your Vera Plugin, but all I did was press the up/down/stop buttons on the remote and a device control box appeared on the Vera browser screen, AND IT WAS DONE! I suddenly had control of the motor simply by clicking the buttons in my browser ... how cool is THAT??  ;D

Thanks for a masterful job of designing that plug-in, you deserve an award for that! If you contact me privately I'll be happy to send you a motor, though it hardly compensates for your time.

I'm going to go play some more now, set up some events, etc., will keep you posted.

Cheers, Adrian

Adrian Biffen
Customer Service
RollerTrol Automation Systems
http://RollerTrol.com/

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 23, 2012, 06:51:44 am
Johan, after loosing lots of time, you and me; thinking the RFXtrx was able to receive Koppla, I come back to you after consulting again the user manual. My feeling is that without receiving capability, it is required to implement the program mechanism between the Vera/RFXtrx and each of your Koppla receiver. This is possible with the RFXtrx protocol. My problem is that I don't want to define a new specific switch device with a new "Program" button.

Here is my proposal:
1) I will add the ability to create manually a new Koppla device from the plugin settings, like for other protocols
2) I will define a variable "DeviceProgrammed" on this device, with a value set by default to 0. So after a manual creation of the device, pushing ON or OFF button will only send a "Program" message and you will have to push a button on the receiver to link the Vera with the receiver. When it is done, you will set the variable "DeviceProgrammed" to 1; then pushing ON or OFF button will send the ON or OFF command to the programmed receiver.

What do you think about that ?

PS: Koppla allow having 16*10 = 160 different receivers.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 23, 2012, 09:32:54 am
Here is my proposal:
1) I will add the ability to create manually a new Koppla device from the plugin settings, like for other protocols
2) I will define a variable "DeviceProgrammed" on this device, with a value set by default to 0. So after a manual creation of the device, pushing ON or OFF button will only send a "Program" message and you will have to push a button on the receiver to link the Vera with the receiver. When it is done, you will set the variable "DeviceProgrammed" to 1; then pushing ON or OFF button will send the ON or OFF command to the programmed receiver.

What do you think about that ?

PS: Koppla allow having 16*10 = 160 different receivers.

I think that your idea might well work, so let's try.

You say Koppla allows having 160 different receivers. I understood (see page 7 of the manual) Koppla allows only 10 channels/receivers to be programmed.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 23, 2012, 10:02:31 am
You say Koppla allows having 160 different receivers. I understood (see page 7 of the manual) Koppla allows only 10 channels/receivers to be programmed.

10 channels per remote, that's true. But you can have until 16 remotes having each one a different system code (0 to 15).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 23, 2012, 12:54:07 pm
You say Koppla allows having 160 different receivers. I understood (see page 7 of the manual) Koppla allows only 10 channels/receivers to be programmed.

10 channels per remote, that's true. But you can have until 16 remotes having each one a different system code (0 to 15).

I never experienced problems due to operating disturbances, therefor I have never read the chapter Changing the system code with interference.

I hope your suggested solution will work :)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: ansandro on June 24, 2012, 09:12:01 am
Hi lolodomo, first of all thanks for this great plugin.

I tried to use KAKU doorbell (AC) but it's not responding. I contacted Bert from RFXCOM and probably the doorbell push button is a GROUP ON command. Are you planning to implement this soon? Thanks in advance!

Here is the RFXmng info of the protocol communication:
0B110005006804F601040F70
Packettype    = Lighting2
subtype       = AC
Sequence nbr  = 5
ID            = 06804F6
Unit          = 1
Command       = Group On
Signal level  = 7
 
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jibdata on June 24, 2012, 02:59:38 pm
Hi,

I'm trying to configure the plugin on my Vera Lite without success.
My setup:
Vera Lite
Firmware version: 1.5.346

RFXtrx433
Batch: 1412
Firmware version: RFXtrx433_44 18-6-2012
Get Status:
response on cmnd  = Get Status
Transceiver type  = 433.92MHz
Firmware version  = 44
Hardware version  = 1.0

I have followed the Quick Start Guide in the first post of this thread.
Uploaded the files as described (tested both with Firefox and IE) through UI5 web GUI and reloaded the lua engine.
When trying to create a device (reloaded the lua engine) it just shows up as a blank generic device without name.
Checking the log file (cat /tmp/log/cmh/LuaUPnP.log|grep RFX) with this result:
08   06/24/12 11:45:19.759   JobHandler_LuaUPnP::HandleActionRequest argument UpnpDevFilename=D_RFXtrx.xml <0x2cf35680>
01   06/24/12 11:45:52.087   Device_LuaUPnP::LoadDeviceDoc ixmlParseBufferEx /etc/cmh-ludl//D_RFXtrx.xml size 15820 ret 106 <0x2b4d1000>
01   06/24/12 11:45:52.088   JobHandler_LuaUPnP::CreateDevice_LuaUPnP failed to load 5/D_RFXtrx.xml so device 5 is offline <0x2b4d1000>
I have tried to follow the Quick Start Guide to the end by setting the devicename manually to "RFXtrx controller device" and done the Serial Port configuration but with same result.

What am I doing wrong here?

Please advice.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 25, 2012, 06:46:30 am
D_RFXtrx.xml file has zie 1075 bytes, not 15820. You probably did something wrong when uploading the different files.
Did you get the files from the attached ZIP file or from code.mios.com ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jibdata on June 25, 2012, 06:52:24 am
I downloaded them from http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha4#

That was probably not a good idea?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 25, 2012, 07:03:06 am
Hi lolodomo, first of all thanks for this great plugin.

I tried to use KAKU doorbell (AC) but it's not responding. I contacted Bert from RFXCOM and probably the doorbell push button is a GROUP ON command. Are you planning to implement this soon? Thanks in advance!

Here is the RFXmng info of the protocol communication:
0B110005006804F601040F70
Packettype    = Lighting2
subtype       = AC
Sequence nbr  = 5
ID            = 06804F6
Unit          = 1
Command       = Group On
Signal level  = 7

Are you sure that it is the only received message ?
For chime / doorbell, there is a dedicated chime message that is sent and then received by the RFXtrx. I had plan to implement this message as someone else already asked me (elsewhere). But I have no plan to implement the "group ON" command for the good reason that it is still no clear for me what should be done when receiving such a message. As I understood, the "all" would not be exaclly a "all devices" but only the devices that are programmed to belong to the "all" group and I have nothing to know which ones are and which ones are not in that special group. And if I correcly remember, on the remotes, the "Group" commands are attached to dedicated buttons.
If you have a clear vision of how AC group works and what should be done, let me know.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 25, 2012, 07:06:16 am
I downloaded them from http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha4#

That was probably not a good idea?

No, that is a good idea. I checked few minutes ago at that place and the file has the correct size. Download each file pushing the button "original format". Before uploading the file to the Vera, open the file D_RFXtrx.xml with your WEB browser and check its size with your file browser.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jibdata on June 26, 2012, 03:39:40 am
I downloaded them from http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha4#

That was probably not a good idea?

No, that is a good idea. I checked few minutes ago at that place and the file has the correct size. Download each file pushing the button "original format". Before uploading the file to the Vera, open the file D_RFXtrx.xml with your WEB browser and check its size with your file browser.

I was not able to download the files correct via code.mios.com. Could not find the button "original format". Do I need to be a registred user there to be able to get this button?
Anyway, I downloaded the zip-file from the first post in this thread and now the plugin is working fine.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: CyberJM on June 27, 2012, 09:02:06 am
Good afternoon,

I am a newbie in this home automation world, but I am really interested in all this.
I hope I am posting on the right topic. if not, please excuse me.
I just bought a vera lite and a rfxtrx433 plus some DI-O plugs to start with.

I bought yesterday a DI-O movment detector (ref 54741), and a DI-O switch (200 W to be placed behind an existing switch).

What I'd like to put on place is :
 1- receive an email if someone cross the detector during the day (I want to place it on the path to my house which is is the middle of nowehere.)
 2- switch on some outdoor lights at a given hour, for a given time then switch them off.(evenings - it is nice during summertime)
 3- switch on the same lights at night time, outside the previous time range, if someone comes to my house.
I'd like to be able to keep the mecanical switch that commands the outdoor lights operationnal if possible.

I then bought a DI-O detector,and an extra flat switch 200W

I created a new device from the frxtrx in the UI5 interface, chosing ARC switch. (the auto detect did not trigger any device creation)
I placed the detector on 'doorbell' since i just need a signal send. (no signal off or on, just 'do something').

I now have a device defined as a light, that goes from off to on an on to off randomly (or so it seems).

My knowledge stops here... anyone to help a poor (and lost) French newbie ?
I have not even succeeded to plug the switch yet...

Thank you

CyberJM
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on June 27, 2012, 09:47:36 am
Is the Chacon motion detector received in RFXmngr?

If that sensor has address code wheels it should be OK. If the sensor is an AC type (learning mode type) it is better not to use this kind of sensor. See http://www.domoticaforum.eu/viewtopic.php?f=27&t=7337
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: CyberJM on June 27, 2012, 01:14:56 pm
Hi,
Thanks for spending time on my issue.
The sensor has wheels.  I get in rfreceiver things like this:
 ACK
 ATIPLUS[0]C Remote type= Unknown remote:FE Channel= 0 Even   Command= TV
 Buffer flushed due to timeout
 ATIPLUS[7]C Remote type= Unknown remote:9 Channel= 7 Even   Command= Drag
 ATIPLUS[7]C Remote type= Unknown remote:FD Channel= 7 Even   Command= Drag
 Buffer flushed due to timeout
 ATIPLUS[7]C Remote type= Unknown remote:9 Channel= 7 Even   Command= Drag
 ATIPLUS[7]C Remote type= Unknown remote:FE Channel= 7 Even   Command= Drag
 Buffer flushed due to timeout
 ATIPLUS[7]C Remote type= Unknown remote:9 Channel= 7 Even   Command= Drag
 ATIPLUS[7]C Remote type= Unknown remote:FF Channel= 7 Even   Command= Drag
 Buffer flushed due to timeout
 ATIPLUS[7]C Remote type= Unknown remote:9 Channel= 7 Even   Command= Drag
 ATIPLUS[7]C Remote type= Unknown remote:100 Channel= 7 Even   Command= Drag
 Buffer flushed due to timeout
kinda randomly.

In the rfxmngr, I get this kind of info, that I used to create the device in my vera lite (ARC, G, 1, 7) :
0710010047010070
Packettype    = Lighting1
subtype       = ARC
housecode     = G
Sequence nbr  = 0
unitcode      = 1
Command       = Off
Signal level  = 7
------------------------------------------------
0710010147010070
Packettype    = Lighting1
subtype       = ARC
housecode     = G
Sequence nbr  = 1
unitcode      = 1
Command       = Off
Signal level  = 7
------------------------------------------------
0710010247010070
Packettype    = Lighting1
subtype       = ARC
housecode     = G
Sequence nbr  = 2
unitcode      = 1
Command       = Off
Signal level  = 7

But I might then try to give it back to the shop I bought it from and try order an X10 MS13 instead then ?
Any advice on what I could use for the switch then ? something to insert behind the mecanical switch, I mean.

Thanks again !

CyberJM
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on June 27, 2012, 05:17:10 pm
Do not use RFreceiver for the RFXtrx, use RFXmngr!!
RFreceiver is for the RFXLAN receiver or the older RFXCOM USB receiver.

Disable all unused protocols. This will increase the sensitivity of the receiver for some protocols.
Some protocols overlap a bit and if both are enabled you will get wrong data or even nothing.

Configure the receiver in RFXmngr and select the protocols used and click Save Settings. the receiver will now be initialized correctly during start-up.
And select the same protocols in the VERA plug-in.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: CyberJM on June 27, 2012, 05:37:21 pm
Ok. Thanks for the advice. I Will try this tomorow.
Thanks again.
CyberJM
Title: Plugin for the USB RFXtrx from RFXCOM
Post by: ansandro on June 27, 2012, 06:08:50 pm


Are you sure that it is the only received message ?
For chime / doorbell, there is a dedicated chime message that is sent and then received by the RFXtrx. I had plan to implement this message as someone else already asked me (elsewhere). But I have no plan to implement the "group ON" command for the good reason that it is still no clear for me what should be done when receiving such a message. As I understood, the "all" would not be exaclly a "all devices" but only the devices that are programmed to belong to the "all" group and I have nothing to know which ones are and which ones are not in that special group. And if I correcly remember, on the remotes, the "Group" commands are attached to dedicated buttons.
If you have a clear vision of how AC group works and what should be done, let me know.

Hi lolodomo, I talked to Bert from RFXCOM and understood that you two figured it out. Doorbell should work when you implement the chime. Hope you can implement it soon. Please let us know about your plans.
Thanks in advance!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 27, 2012, 06:53:47 pm


Are you sure that it is the only received message ?
For chime / doorbell, there is a dedicated chime message that is sent and then received by the RFXtrx. I had plan to implement this message as someone else already asked me (elsewhere). But I have no plan to implement the "group ON" command for the good reason that it is still no clear for me what should be done when receiving such a message. As I understood, the "all" would not be exaclly a "all devices" but only the devices that are programmed to belong to the "all" group and I have nothing to know which ones are and which ones are not in that special group. And if I correcly remember, on the remotes, the "Group" commands are attached to dedicated buttons.
If you have a clear vision of how AC group works and what should be done, let me know.

Hi lolodomo, I talked to Bert from RFXCOM and understood that you two figured it out. Doorbell should work when you implement the chime. Hope you can implement it soon. Please let us know about your plans.
Thanks in advance!

For ARC protocol (old protocol), there is a chime command.
For AC protocol (new protocol), it looks like doorbell uses a Group ON command.
So, I can certainly do something for doorbell using the old ARC protocol but for those using the new AC protocol that is more difficult because I cannot consider that if I receive a Group ON command, it comes necessarly from a doorbell.
I continue my thinking for AC doorbell.

More generally regarding group commands for AC and HomeEasy EU protocols, I think I will let the user defining which devices belong to the group. I will add a variable on the devices and the user will set the variable to 1 when the device is a member of the group. When a group command will be received, all devices having the variable set to 1 will be considered.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 28, 2012, 11:35:16 am
Dear Lolodomo,

When you live in the Netherlands, maybe it is an idea to send/bring to you my Koppla controller and one receiver to help you to make it work?
If you do so, send me your telephone number to make an appointment.

Regards Johan
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on June 28, 2012, 02:37:54 pm
Johan,

Ikea Koppla receiving is not supported by the RFXtrx433!!
See the RFXtrx User Guide on our download page chapter 2.1 which protocols are supported for receive and transmit.

Bert
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 28, 2012, 02:44:40 pm
Dear Lolodomo,

When you live in the Netherlands, maybe it is an idea to send/bring to you my Koppla controller and one receiver to help you to make it work?
If you do so, send me your telephone number to make an appointment.

Regards Johan

Johan, I am living in France. ;)
I don't think it is necessary to send me devices, I think we should be able to make it work relatively quickly now. I just have to find time to code the required changes.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 30, 2012, 07:07:41 am
Johan, I just finished to add Ikea Koppla support. Please try and give me a feedback.
You have to create the devices from the panel "device creation" (at the bottom of the page for Ikea Koppla). You must enter a system code and a channel first.
Once your Vera device is created, push ON or OFF button to associate the Vera with your device, the same way you will do with a normal Koppla remote.
Once the association is done, set the variable "KopplaProgrammed" to 0 on theVera  device and reload.
Now, ON and OFF commands should command your receiver.
Same principle for dimmer.

The updated sources are in the trunk: http://code.mios.com/trac/mios_rfxtrx/browser/trunk# You have to update all the *_RFXtrx.* files.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 30, 2012, 07:51:20 am
Support for Visonic PowerCode door/window/motion sensors has been added.
Updated files are in the trunk: http://code.mios.com/trac/mios_rfxtrx/browser/trunk#

As Visonic is not using 433 MHz frequency, RFXtrx devices currently sold are probably not able to manage Vinoic messages.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 30, 2012, 07:57:00 am
And I forgot to mention that support of La Crosse WS2300 has been added too (temperature, rain and wind). Changes are in the trunk. Firmware v44 is required.

A new alpha version will be released as soon as I have the confirmation that Ikea Koppla is working.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: ansandro on June 30, 2012, 10:50:10 am
And I forgot to mention that support of La Crosse WS2300 has been added too (temperature, rain and wind). Changes are in the trunk. Firmware v44 is required.

A new alpha version will be released as soon as I have the confirmation that Ikea Koppla is working.

And will AC/KAKU be implemented in the new Alpha Version?
Thanks again!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on June 30, 2012, 03:24:14 pm
Johan, I just finished to add Ikea Koppla support. Please try and give me a feedback.
You have to create the devices from the panel "device creation" (at the bottom of the page for Ikea Koppla). You must enter a system code and a channel first.
Once your Vera device is created, push ON or OFF button to associate the Vera with your device, the same way you will do with a normal Koppla remote.
Once the association is done, set the variable "KopplaProgrammed" to 0 on theVera  device and reload.
Now, ON and OFF commands should command your receiver.
Same principle for dimmer.

The updated sources are in the trunk: http://code.mios.com/trac/mios_rfxtrx/browser/trunk# You have to update all the *_RFXtrx.* files.

Hi Lolodomo,

I've tested your work and I am pleased to say that you're almost there. I have managed tot get the Koppla receivers working with Vera, but with the following remarks.

1) The system code "2" in Vera corresponds with system code "3" from Koppla and also 4 with 5; 6 with 7; 8 with 9; 10(A) with11; 12 (C) with 13; and 14 (E) with 15. The odd system codes in Vera does not match the even system codes and system code "1" from Koppla.
2) The ON and Off from the dimmer is working well.  The dimmerfunction works in reverse mode. Pressing the "+" brings the dimmer to 100% instead of 10% as shown on the Vera controller. The next "+" dims the light one step instead of increasing it to 20% level, and so on.
3) You only need the Koppla remote to program the Koppla receiver (system and receiver channel). The Koppla remote is not needed for association with Vera.
4) There is no need to push "ON" or "OFF" to associate the Vera with the device.
5) Once the device is created the variable "Device/Advanced/KopplaProgrammed" is to be set to 1 instead of 0,
6) Safe the changes that are made and the receiver is ready to use.

I hope this is for you enough information to finalize the Koopla support.

Regards Johan
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on June 30, 2012, 06:50:53 pm
And I forgot to mention that support of La Crosse WS2300 has been added too (temperature, rain and wind). Changes are in the trunk. Firmware v44 is required.

A new alpha version will be released as soon as I have the confirmation that Ikea Koppla is working.

And will AC/KAKU be implemented in the new Alpha Version?
Thanks again!

AC is already implemented ... since a long time. Is there something not working ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 01, 2012, 05:03:20 am
I've tested your work and I am pleased to say that you're almost there. I have managed tot get the Koppla receivers working with Vera, but with the following remarks.

1) The system code "2" in Vera corresponds with system code "3" from Koppla and also 4 with 5; 6 with 7; 8 with 9; 10(A) with11; 12 (C) with 13; and 14 (E) with 15. The odd system codes in Vera does not match the even system codes and system code "1" from Koppla.

This is something to be checked by RFXCOM, I am using the system code provided in the message. What is the range of values accepted by the remote ? 1 to 16 ? RFXCOM uses range 0 to 15.

Quote
2) The ON and Off from the dimmer is working well.  The dimmerfunction works in reverse mode. Pressing the "+" brings the dimmer to 100% instead of 10% as shown on the Vera controller. The next "+" dims the light one step instead of increasing it to 20% level, and so on.

Ok, I will change the order. Very easy.

Quote
3) You only need the Koppla remote to program the Koppla receiver (system and receiver channel). The Koppla remote is not needed for association with Vera.
4) There is no need to push "ON" or "OFF" to associate the Vera with the device.
5) Once the device is created the variable "Device/Advanced/KopplaProgrammed" is to be set to 1 instead of 0,

My idea was to provide something that did not require a previously setup with a remote. Maybe Koppla receivers are always sold with a remote ?
If you have a remote already setup with your receivers, that's true that you don't need to program an association with the Vera, just create the devices with the right system code and channel.
Ok, I might have lost time to implement the "program mode" in case every people have a remote ! I will change the default value as you suggest. Can you at least test that the association is doable directly from the Vera, just to validate ?

Quote
6) Safe the changes that are made and the receiver is ready to use.

Sorry, what do you mean exactly ?

Quote
I hope this is for you enough information to finalize the Koopla support.

Yes. The issue with the value of the system code has to be investiguated with Bert (RFXCOM). Can you check what range of value proposes RFXmngr application ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 01, 2012, 05:22:15 am
Johan, I have fixed dim levels order and default value of the KopplaProgrammed variable. Can you validate ?
Only L_RFXtrx.lua has been changed.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: ansandro on July 01, 2012, 06:19:38 am
And I forgot to mention that support of La Crosse WS2300 has been added too (temperature, rain and wind). Changes are in the trunk. Firmware v44 is required.

A new alpha version will be released as soon as I have the confirmation that Ikea Koppla is working.

And will AC/KAKU be implemented in the new Alpha Version?
Thanks again!

AC is already implemented ... since a long time. Is there something not working ?

Ah sorry, I mean the doorbell we've discussed earlier, also with Bert. Thanks.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: ansandro on July 01, 2012, 06:28:37 am
Can somebody please explain how to set AC/KAKU as dimmer (set level). My KAKU dimmer is recognised as ON/OFF device. Thanks in advance.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on July 01, 2012, 07:44:23 am
Johan, I have fixed dim levels order and default value of the KopplaProgrammed variable. Can you validate ?
Only L_RFXtrx.lua has been changed.

Hi Lolodomo,

The dimmer is working well now. ;D
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 02, 2012, 04:59:34 am
And I forgot to mention that support of La Crosse WS2300 has been added too (temperature, rain and wind). Changes are in the trunk. Firmware v44 is required.

A new alpha version will be released as soon as I have the confirmation that Ikea Koppla is working.

And will AC/KAKU be implemented in the new Alpha Version?
Thanks again!

AC is already implemented ... since a long time. Is there something not working ?

Ah sorry, I mean the doorbell we've discussed earlier, also with Bert. Thanks.

This will not be included in the next version. It is still not really clear in my mind how to handle it.

But ARC doorbell could be in the next version as there is a clear "chime" message I can handle.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 02, 2012, 05:02:26 am
Johan, I have fixed dim levels order and default value of the KopplaProgrammed variable. Can you validate ?
Only L_RFXtrx.lua has been changed.

Hi Lolodomo,

The dimmer is working well now. ;D

I discussed with Bert regarding the system code. I will manage in the plugin the shift between the value displayed by the remote and the value in the RFXtrx message. Can you confirm the range is 1 - 16 in the remote ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on July 02, 2012, 05:33:14 am
Johan, I have fixed dim levels order and default value of the KopplaProgrammed variable. Can you validate ?
Only L_RFXtrx.lua has been changed.

Hi Lolodomo,

The dimmer is working well now. ;D

I discussed with Bert regarding the system code. I will manage in the plugin the shift between the value displayed by the remote and the value in the RFXtrx message. Can you confirm the range is 1 - 16 in the remote ?

Yes, range system codes 01 - 16 and range channels 1 - 10
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jtmoore on July 03, 2012, 05:36:19 am
Hi lolodomo
I notice that Remote control and IR (ATI, Medion, PC Remote): not yet implemented.  Do you have plans to support this in future please? Thanks and regards,
jtmoore.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 03, 2012, 08:09:02 am
Hi lolodomo
I notice that Remote control and IR (ATI, Medion, PC Remote): not yet implemented.  Do you have plans to support this in future please? Thanks and regards,
jtmoore.

What would you expect exactly ?
A dedicated panel with buttons representing a kind of remote ?
I imagine I could easily add an action to send ATI commands for example. And you could invoke these actions from a scene for example. Is it what you need ?

Edit: I see now that the RFXtrx can receive and send remote orders. So we could even imagine to use such a remote as a replacement for a Z-Wave remote. What's the price range for such a remote ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jtmoore on July 03, 2012, 07:13:53 pm
Hi lolodomo.
I see lots of these ATI and Medion RF remotes on ebay in UK and US for well under $20 USD. I didn't find any new ones, so perhaps they are now discontinued. I do have an old Medion remote, and the RFXCOM test program picks up all the buttons very nicely. I imagined using this as a cheap alternative to Z-wave remote, although the LightwaveRF remotes (that you already support) might do this for me in stead. Thanks.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 05, 2012, 02:21:12 pm
Alpha 5 has just been released.
Plugin files are available at http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha5#
A ZIP file with all the plugin files is attached to the first message of that topic too.

What's new in version alpha 5:
- plugin is up to date with RFXtrx firmware v45
- add support for Ikea Koppla
- add support for La Crosse WS2300 (temperature, humidity, rain and wind sensors)
- add support for chime command (ARC protocol)
- add support for Visonic PowerCode door/window sensors and motion sensors
- add partial support for X10 security remotes (light management)
Title: Plugin for the USB RFXtrx from RFXCOM
Post by: ansandro on July 05, 2012, 03:47:31 pm
Can somebody name me an ARC doorbell available in The Netherlands?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jtmoore on July 06, 2012, 09:30:51 am
Can anyone tell me the correct method to upgrade from alpha 4 to alpha 5 please? I tried loading the new files, but the plugin stopped working with "device not ready" error message. I restored my Vera Lite to yesterday's backup, and it is all working again. Thanks in advance for any advice.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 06, 2012, 11:36:15 am
Can anyone tell me the correct method to upgrade from alpha 4 to alpha 5 please? I tried loading the new files, but the plugin stopped working with "device not ready" error message. I restored my Vera Lite to yesterday's backup, and it is all working again. Thanks in advance for any advice.

Download the plugin files. Then, from the dashboard, upload them to the Vera and finally reload.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 06, 2012, 12:04:38 pm
Can somebody name me an ARC doorbell available in The Netherlands?

You can search for this product: http://www.planete-domotique.com/kit-complet-carillon-prise-compatible-chacon.html
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jtmoore on July 06, 2012, 01:03:28 pm
Can anyone tell me the correct method to upgrade from alpha 4 to alpha 5 please? I tried loading the new files, but the plugin stopped working with "device not ready" error message. I restored my Vera Lite to yesterday's backup, and it is all working again. Thanks in advance for any advice.

Download the plugin files. Then, from the dashboard, upload them to the Vera and finally reload.

Hi lolodomo. I used the ZIP file and this time and upgrade works. I notice file size difference of L_RFXtrx.lua in the Truck, so perhaps there the file there is corrupted (or my download) which caused my earlier upgrade to fail.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 07, 2012, 03:02:04 am
Can anyone tell me the correct method to upgrade from alpha 4 to alpha 5 please? I tried loading the new files, but the plugin stopped working with "device not ready" error message. I restored my Vera Lite to yesterday's backup, and it is all working again. Thanks in advance for any advice.

Download the plugin files. Then, from the dashboard, upload them to the Vera and finally reload.

Hi lolodomo. I used the ZIP file and this time and upgrade works. I notice file size difference of L_RFXtrx.lua in the Truck, so perhaps there the file there is corrupted (or my download) which caused my earlier upgrade to fail.

I just checked, the L_RFXtrx.lua file has the right size (105343 bytes) in the trunk and in the alpha 5 version.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 07, 2012, 04:02:29 am
My updated TODO list is now:
1 - add support for remotes (ATI, Medion, ...)
2 - enhance X10 security support
3 - find a solution for "group" commands (ARC, AC, ...)
4 - create a description/help page
5 - release a first version to have the plugin available in the app store
Title: Plugin for the USB RFXtrx from RFXCOM
Post by: ansandro on July 07, 2012, 03:38:27 pm
Thanks a lot for your time and great work!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 08, 2012, 06:36:01 am
Johan, can you check that the problem with the system code for Ikea Koppla is now solved.
The user enters a value from 1 to 16 (the value from the remote) and I convert it to a value from 0 to 15.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on July 08, 2012, 01:09:39 pm
Johan, can you check that the problem with the system code for Ikea Koppla is now solved.
The user enters a value from 1 to 16 (the value from the remote) and I convert it to a value from 0 to 15.

Hello Lolodomo,

After uploading the RFXtrx.lua file and a reload only 0 and the even system codes from Vera matches the odd system codes from the Koppla.
I use RFXtrx Controler V.4 version alpha 5.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 10, 2012, 07:16:29 am
For people owning an X10 security remote, could you please indicate the model and provide a grab using the RFXmngr application of received messages for each button of the remote. Please do it for the different modes when different modes exist - for example for the SH264 mode.
That would help me to add support for these remotes, and that would allow checking that all buttons are managed by the RFXtrx device.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 10, 2012, 07:35:18 am
Just tested the Comfort Remote Control from Marmitek (reference SH624)
the bottom buttons are all recognized as light switches by your code, so that's fine.
The button about bright is yet not recognized:
up:
02   06/10/12 20:52:22.838   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 3 <0x2ef01680>
02   06/10/12 20:52:22.838   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 3D 41 00 03 60  <0x2ef01680>
down:
02   06/10/12 20:53:00.598   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 2 <0x2ef01680>
02   06/10/12 20:53:00.598   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 41 41 00 02 50  <0x2ef0168

The "All lamps" button is issuing a special code:
02   06/10/12 20:37:18.718   luup_log:34: RFXtrx: Lighting1 command not yet implemented: 6 <0x2ef01680>
02   06/10/12 20:37:18.718   luup_log:34: RFXtrx: Decoding not yet implemented for message 07 10 00 00 41 00 06 50

I just found again cboulang's message. It looks like for ON/OFF buttons, lighting1 message is used, not security1 message.

But I don't understand exactly in which case the security1 message is used to ON/OFF light1 and light2 (even if it is a feature already implemented in the plugin) ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 10, 2012, 05:04:14 pm
Please find in the trunk ( http://code.mios.com/trac/mios_rfxtrx/browser/trunk# ) a new test version including support for X10 security.

This is very easy: first use your remote to arm or disarm the X10 alarm panel and the plugin will create a new device. Then this device will be updated when you use your remote. From the Vera device, you can arm your X10 alarm or send a panic command. The disarm button is here but I have disabled the code to avoid a major security risk (disarm an alarm without entering a PIN code). In the next version, I will add a user option to enable disarm feature.
Please give me a feedback.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Thomasss on July 11, 2012, 10:07:12 am
Hello lolodomo,
Thank you for continuing to improve your plugging. I use it sinds alpha2 whitout any issue.
Even I don't need X10 security , I put the last alpha6 and everything is comming back.

At the Brico shop, I saw a Chacon doorbell kit at 10€. Even I know that doorbeel support is not yet fully implemented, I give it a chance.
Unfortunalty it's not recognized. It's this model : http://www.edomotique.com/vproduit--84151-carillon-sans-fil-eco-chacon--chacon--84151--84151--0-0-0-852695.aspx

Is there a chance for a futur support ? Can I help somehow ? I didn't see any relevant log on cgi-bin/cmh/log.sh?Device=LuaUPnP but maybe I need to ssh to acces these logs.

Thank you.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 11, 2012, 12:15:47 pm
Hello lolodomo,
Thank you for continuing to improve your plugging. I use it sinds alpha2 whitout any issue.
Even I don't need X10 security , I put the last alpha6 and everything is comming back.

At the Brico shop, I saw a Chacon doorbell kit at 10€. Even I know that doorbeel support is not yet fully implemented, I give it a chance.
Unfortunalty it's not recognized. It's this model : http://www.edomotique.com/vproduit--84151-carillon-sans-fil-eco-chacon--chacon--84151--84151--0-0-0-852695.aspx

Is there a chance for a futur support ? Can I help somehow ? I didn't see any relevant log on cgi-bin/cmh/log.sh?Device=LuaUPnP but maybe I need to ssh to acces these logs.

Thank you.

This is probably a new one using the AC protocol and a group ON command.
To help, you can grab with the RFXmngr application all the messages you received when you push the button and after.

AC doorbell is something I will manage probably in the next alpha release.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Thomasss on July 11, 2012, 01:52:13 pm
Thank you for replying.

I don't see anything in RFXmngr. I regulary see Oregon sensors entry so it looks like I correctly installed RFXMngr (never used before).
Even when checking all protocols or the "undec on" field, still nothing.
Can it be a proprietary implementation of RFX 433,92Mhz ? There were others pack more expensive with a strange logo "100% compatible" but they don't say what.
http://www.chacon.be/media/sync/84165/From%20Chacon/84165%20User%20Manual.pdf.pdf

No urgent need of reply, I was just wondering. I know that power users recieve a lot of request. I can wait for the alpha6.

Have a nice evening.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 11, 2012, 02:32:28 pm
It might be that this doorbell is not compatible with the RFXtrx device.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on July 11, 2012, 06:26:54 pm
Speaking of door bells, 

I have a Friedland Wireless Extender working with a wireless chime - both of which I think work/transmit on 433MHz (or maybe 866Mhz)

http://www.connevans.com/instructions/42fd271.pdf
http://www.connevans.com/instructions/42fd285.pdf

Am I right in saying that I could set my door bell up to work with the RFXtrx?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 11, 2012, 07:10:02 pm
Speaking of door bells, 

I have a Friedland Wireless Extender working with a wireless chime - both of which I think work/transmit on 433MHz (or maybe 866Mhz)

http://www.connevans.com/instructions/42fd271.pdf
http://www.connevans.com/instructions/42fd285.pdf

Am I right in saying that I could set my door bell up to work with the RFXtrx?

Ask RFXCOM but I don't believe this product is supported by the RFXtrx.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on July 12, 2012, 03:11:04 am
Thanks lolodomo,

I've emailed RFXcom, and will update this post with the news , just because I have been looking for a door bell to integrate within Vera for ages, and this might solve my problem.

Couple of quick questions

1) Are there any plans to support the RFXCOM Transceiver with LAN Interface?
2) From what I can see this plug in works as a single device, is there scope (unless I missed it) for individual devices to be created and controlled? E.g a single LightwaveRF light can sit under the lights Devices list etc.

Thanks
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 12, 2012, 05:24:40 am
1) Are there any plans to support the RFXCOM Transceiver with LAN Interface?

For current RFXCOM products with a LAN interface, there is another good plugin developed by evanes.
For future RFXCOM products with a LAN interface, I will adapt my plugin to be compatible as they will use the same protocol as the RFXtrx USB model. Normally I will have only few lines of code to add to be immediately compatible with these products coming in the future.

Quote
2) From what I can see this plug in works as a single device, is there scope (unless I missed it) for individual devices to be created and controlled? E.g a single LightwaveRF light can sit under the lights Devices list etc.

No, there is a main device mainly for setup of the plugin and then a new device is created for each thing, using standard devices when they exist: temperature device, humidity device, ON/OFF switch device, window covering device, ...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on July 12, 2012, 02:13:51 pm
Just an update on my door bell quest,

 it seem the Friedland Libra one I already have is not supported, but Bert tells me I can use this  http://www.klikaanklikuit.nl/shop/producten/deurbellen/belzender-cdb-6500b-1/ With my exisitng 2 wire bell.
 
Or this set with pushbutton transmitter included  http://www.klikaanklikuit.nl/shop/producten/op-op/draadloze-deurbel-cdb-6500ac-1/
 
Or this set with transmitter to be connected to my existing chime push button http://www.klikaanklikuit.nl/shop/producten/op-op/draadloze-deurbel-cdb-6500bc-1/

Lolodomo, when i asked Bert about a Vera quick reference guide, as he did not have one on his web site, yet he did for many of the other supported solution, he suggested if you (and he named you specifically) had one, he would be more than happy to publish it on his site?

So being new to all this myself, and looking to outlay £90 on a RFXrtx - by any chance do you (or anyone) have a up to date quick reference, showing step by step how to install and manag this plug in ?


Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on July 12, 2012, 03:07:33 pm
Hello Lolodomo

I've loaded the alpha 6 files from the trunk. The RFXtrx channels still don't match all channels of the Ikea Koppla receivers. Are you aware of that? Do you still want me to test for you?

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 12, 2012, 03:37:47 pm
So being new to all this myself, and looking to outlay £90 on a RFXrtx - by any chance do you (or anyone) have a up to date quick reference, showing step by step how to install and manag this plug in ?

No. It is on my TODO list before I release the plugin on the app store.
This is one of the reasons why the plugin is still in alpha version and not published on the store.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 12, 2012, 03:40:54 pm
Hello Lolodomo

I've loaded the alpha 6 files from the trunk. The RFXtrx channels still don't match all channels of the Ikea Koppla receivers. Are you aware of that? Do you still want me to test for you?

No, I understood from you previous message that all was ok with Ikea Koppla (in alpha 5) :(
When you create the device, you have to enter a system code from 1 to 16 and I shift it to 0-15 and keep this value for next usages.
What's wrong exactly ?

Edit: sorry you are talking about the channels not the system code. So what's the problem exactly ? Is it relative to multichannels ? I forgot this case and currently only the lower channel number is considered.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on July 12, 2012, 03:49:50 pm
Hello Lolodomo

I've loaded the alpha 6 files from the trunk. The RFXtrx channels still don't match all channels of the Ikea Koppla receivers. Are you aware of that? Do you still want me to test for you?

No, I understood from you previous message that all was ok with Ikea Koppla (in alpha 5) :(
When you create the device, you have to enter a system code from 1 to 16 and I shift it to 0-15 and keep this value for next usages.
What's wrong exactly ?

As I mentioned before, only the even channels from the RFXtrx matches the odd channels from the Kopple receivers, see tabel below.

RFXtrx system code                  Koppla/Ikea system code    Match?
          0                                            1                                OK
          1                                            2                                NO
          2                                            3                                OK
          3                                            4                                NO
          4                                            5                                OK
          5                                            6                                NO
          6                                            7                                OK
         etc
         14                                          15                               OK
         15                                          16                               NO

edit: Instead of the channel codes I meant the system codes. My apologies for the wrong use of words  ???
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 13, 2012, 04:35:25 am
Hello Lolodomo

I've loaded the alpha 6 files from the trunk. The RFXtrx channels still don't match all channels of the Ikea Koppla receivers. Are you aware of that? Do you still want me to test for you?

No, I understood from you previous message that all was ok with Ikea Koppla (in alpha 5) :(
When you create the device, you have to enter a system code from 1 to 16 and I shift it to 0-15 and keep this value for next usages.
What's wrong exactly ?

As I mentioned before, only the even channels from the RFXtrx matches the odd channels from the Kopple receivers, see tabel below.

RFXtrx system code                  Koppla/Ikea system code    Match?
          0                                            1                                OK
          1                                            2                                NO
          2                                            3                                OK
          3                                            4                                NO
          4                                            5                                OK
          5                                            6                                NO
          6                                            7                                OK
         etc
         14                                          15                               OK
         15                                          16                               NO

edit: Instead of the channel codes I meant the system codes. My apologies for the wrong use of words  ???

Ok, that is clear now. That could be a bug in the RFXtrx in that case. RFXCOM is reading us but I will mail Bert to inform him.
Did you check if 1 (RFXtrx) is not matching 1 (Koppla) ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on July 13, 2012, 07:57:02 am
Quote
Ok, that is clear now. That could be a bug in the RFXtrx in that case. RFXCOM is reading us but I will mail Bert to inform him.
Did you check if 1 (RFXtrx) is not matching 1 (Koppla) ?

Yes, I have tried out all possible combinations. I have already received a e-mail of Bert.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on July 13, 2012, 01:37:31 pm
Hello Lolodomo,

Together with Bert, the RFXtrx433 is now working fully with Ikea Koppla Receivers. Many thanks for your efforts.
To you and Bert a job well done. ;D ;D

Regards Johan
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jibdata on July 16, 2012, 04:43:36 pm
Hi Lolodomo,

Is it possible to have more than one RFXtrx433 device with your plugin?
I'm considering this because I'm having conflict with the protocols I want to have enabled.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 16, 2012, 06:55:26 pm
Hi Lolodomo,

Is it possible to have more than one RFXtrx433 device with your plugin?
I'm considering this because I'm having conflict with the protocols I want to have enabled.

Hi

I have not tested it but I see no reason why it should not be possible.
We will have to create two devices and associate each of them to a different serial port.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jibdata on July 16, 2012, 07:22:57 pm
Ok!

I have ordered a second device.
I'll let you know when I have tried.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 17, 2012, 05:14:35 am
Hello Lolodomo,

Together with Bert, the RFXtrx433 is now working fully with Ikea Koppla Receivers. Many thanks for your efforts.
To you and Bert a job well done. ;D ;D

Regards Johan

Remains to handle (by my plugin) multichannels commands coming from the remote. Unfortunately, it requires a major change in my plugin. Will be included in next version.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jibdata on July 18, 2012, 06:18:52 pm
Hi Lolodomo,

Is it possible to have more than one RFXtrx433 device with your plugin?
I'm considering this because I'm having conflict with the protocols I want to have enabled.

Hi

I have not tested it but I see no reason why it should not be possible.
We will have to create two devices and associate each of them to a different serial port.

Lolodomo, I have now installed a second device.
My configuration is: Vera Lite -> USB HUB (on external power) -> 2 x RFXtrx433 devices, each with separate RFXtrx plugin device instance and port.
Works like a charm  :) and no more protocol conflicts.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on July 20, 2012, 05:13:38 am
Hi Lolodomo,

Is it possible to have more than one RFXtrx433 device with your plugin?
I'm considering this because I'm having conflict with the protocols I want to have enabled.

Hi

I have not tested it but I see no reason why it should not be possible.
We will have to create two devices and associate each of them to a different serial port.

Lolodomo, I have now installed a second device.
My configuration is: Vera Lite -> USB HUB (on external power) -> 2 x RFXtrx433 devices, each with separate RFXtrx plugin device instance and port.
Works like a charm  :) and no more protocol conflicts.

Thank you for the test and confirmation 8)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on July 26, 2012, 07:58:09 pm
Hi

As I'm seriously looking to get one of these transceivers, I thought I would look at the wiki page  http://code.mios.com/trac/mios_rfxtrx  however it' actually shows me information on "Trac 0.12.3" !?

It would be really good to see an up to date user/install guide and the solution etc.

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: grahamparsons on July 29, 2012, 09:31:23 am
Has anyone found a way to read code from RF 433MHz to control the following Blind control reciever. This system was pre installed in my roller blinds that use a simple Remote control over 433MHz, I would like to find a way to read this code and program it using Vera RFXcom to send UP/Down to motor.

aoksz.com/ShowProducts.asp?ID=36

I have tried all of the available options with the RFXcom Manager but it just not read any signals from my remote.

Any help !!!!, or am I missing someway to read the code and program manual the code to transmit to receiver.

 ???
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: strangely on July 29, 2012, 04:30:11 pm
Have you tried it with the diagnostic utility on the computer? If this can see data being transmitted then you have a chance that support can be added for it.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: grahamparsons on July 29, 2012, 08:22:25 pm
If you mean using the RFXmngr, I am not really sure how this works. I have tried selecting seveal devices but once I select the receive tab and press the button on remote nothing comes up. Do you have any advice on how to use this program to wait for a none listed device so that it could at lease pick up the code from my hand held transmitter, It should pick up something as it is using the same frequency 433MHz. Any idears ?, or if there is any other softwarethat works with RFXcom so it could be put in a mode were it waits for a transmition and displays the code.

Graham ???
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Peter on August 02, 2012, 06:16:15 pm
Hello I am Peter and I'am new with de vera.

With the rfxmngr on windows i receive a lot of messages
i can install the plugin RFXtrx without error and i think it shoud be working.
I have the old usb rfx receiver from 2010.
I did some test from the forum with x10 devices (remotes, motion sensors dooralarms. But I don't get new devices in my new vera lite.
Can this work without the alarmpannel or should it connectec to a alarmpannel?

usb 1-1.4: new full speed USB device using rt3883-ehci and address 6
ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
usb 1-1.4: Detected FT232RL
usb 1-1.4: Number of endpoints 2
usb 1-1.4: Endpoint 1 MaxPacketSize 64
usb 1-1.4: Endpoint 2 MaxPacketSize 64
usb 1-1.4: Setting MaxPacketSize 64
usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0

root@MiOS_35101298:/tmp/log/cmh# ls -ltr /dev/tty*
crw-rw-rw-    1 root     root        5,   0 Jan  1  1970 /dev/tty
crw-rw-rw-    1 root     root        4,  65 Jan  1  1970 /dev/ttyS1
crw-rw-rw-    1 root     root      188,   0 Aug  2 23:55 /dev/ttyUSB0
crw-rw-rw-    1 root     root        4,  64 Aug  2 23:59 /dev/ttyS0

root@MiOS_35101298:/tmp/log/cmh# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0606
Bus 001 Device 003: ID 0951:1607
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 006: ID 0403:6001
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 03, 2012, 02:41:15 am
This plugin should not be compatible with the old USB RFXCOM.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Brientim on August 03, 2012, 03:26:05 am
Hello,

Just noticed there is an error in D_RFXtrx.json. The PluginVersion and FirmwareVersion are appearing in the top of the Device creation which results in the House Code not being displayed.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on August 03, 2012, 08:07:51 am
Anyone interested in a How To/Set Up  guide, I found this from RollerTrol..
http://rollertrol.com/vera-lite-wifi-control-shade-blind%20motors-instructions-3
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 04, 2012, 04:55:46 am
Hello,

Just noticed there is an error in D_RFXtrx.json. The PluginVersion and FirmwareVersion are appearing in the top of the Device creation which results in the House Code not being displayed.

Unfortunately, it is not a plugin bug but a firmware (1.5.408) bug :(

http://forum.micasaverde.com/index.php/topic,11061.msg78587.html#msg78587

The solution: either waiting for a new beta firmware or restoring firmware 1.5.346.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 04, 2012, 04:59:35 am
If you mean using the RFXmngr, I am not really sure how this works. I have tried selecting seveal devices but once I select the receive tab and press the button on remote nothing comes up. Do you have any advice on how to use this program to wait for a none listed device so that it could at lease pick up the code from my hand held transmitter, It should pick up something as it is using the same frequency 433MHz. Any idears ?, or if there is any other softwarethat works with RFXcom so it could be put in a mode were it waits for a transmition and displays the code.

Graham ???

You have to discuss directly with RFXCOM. Normally, you have an option in the RFXmngr application to display undecoded message.

Of course, the Vera plugin can only manage devices that are first supported by the RFXtrx device.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 04, 2012, 05:05:36 am
Hello Lolodomo,

Together with Bert, the RFXtrx433 is now working fully with Ikea Koppla Receivers. Many thanks for your efforts.
To you and Bert a job well done. ;D ;D

Regards Johan

Remains to handle (by my plugin) multichannels commands coming from the remote. Unfortunately, it requires a major change in my plugin. Will be included in next version.

One time again I forgot that Koppla receiving is not possible with RFXtrx !

But anyway, I will improve child devices management in the plugin. Work in progress...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on August 04, 2012, 12:46:54 pm
Lolodomo,

it seems that one of the correction I performed has not gone through Alpha5 build that I just installed... and Arm/Bypass stops working again.
It is probably because I forgot to send it t you  :-[

First part, in the LUA code, the working part is:

Code: [Select]
function SetArmed(device, newArmedValue)

local id = luup.devices[device].id
log("setArmed " .. id .. " target " .. newArmedValue)
-- log("setArmed not yet implemented", 2)
variable = tabVars["VAR_ARMED"]
luup.variable_set(variable[1], variable[2], newArmedValue, device)

end

Second part is in the I_RFXTRX.xml:
Code: [Select]
    <action>
    <serviceId>urn:micasaverde-com:serviceId:SecuritySensor1</serviceId>
    <name>SetArmed</name>
    <run>if (pluginLib ~= nil) then pluginLib.SetArmed(lul_device, lul_settings.newArmedValue) end</run>
    </action>

It seems that it was working better with a capital 'S' than an 's'.
When correcting online, I had to remove the device and let it rediscover everything before that the Arm/Bypass does work again.

Hope it helps.
Chris
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 05, 2012, 04:35:54 am
Lolodomo,

it seems that one of the correction I performed has not gone through Alpha5 build that I just installed... and Arm/Bypass stops working again.

Hi Chris.

I thought it was already corrected in the alpha 5 but after checking the fix is only in the trunk. So the correction (using a small starting "s" ;) ) will be in the next alpha version.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Peter on August 07, 2012, 10:13:50 am
Has someone experiance with the old Rfxcom usb receiver.
Is there a plugin who can communicate with the old Rfxcom usb receiver?
Or is there a way to change the protocol in this plugin to get it work?

Peter

Old Post:

Hello I am Peter and I'am new with de vera.

With the rfxmngr on windows i receive a lot of messages
i can install the plugin RFXtrx without error and i think it shoud be working.
I have the old usb rfx receiver from 2010.
I did some test from the forum with x10 devices (remotes, motion sensors dooralarms. But I don't get new devices in my new vera lite.
Can this work without the alarmpannel or should it connectec to a alarmpannel?

usb 1-1.4: new full speed USB device using rt3883-ehci and address 6
ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
usb 1-1.4: Detected FT232RL
usb 1-1.4: Number of endpoints 2
usb 1-1.4: Endpoint 1 MaxPacketSize 64
usb 1-1.4: Endpoint 2 MaxPacketSize 64
usb 1-1.4: Setting MaxPacketSize 64
usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0

root@MiOS_35101298:/tmp/log/cmh# ls -ltr /dev/tty*
crw-rw-rw-    1 root     root        5,   0 Jan  1  1970 /dev/tty
crw-rw-rw-    1 root     root        4,  65 Jan  1  1970 /dev/ttyS1
crw-rw-rw-    1 root     root      188,   0 Aug  2 23:55 /dev/ttyUSB0
crw-rw-rw-    1 root     root        4,  64 Aug  2 23:59 /dev/ttyS0

root@MiOS_35101298:/tmp/log/cmh# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0606
Bus 001 Device 003: ID 0951:1607
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 006: ID 0403:6001
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 07, 2012, 03:35:57 pm
Has someone experiance with the old Rfxcom usb receiver.
Is there a plugin who can communicate with the old Rfxcom usb receiver?
Or is there a way to change the protocol in this plugin to get it work?

Peter

I imagine the protocol could be similar to the one used by the RFX LAN. That's something to be confirmed by RFXCOM. In this case, the other RFXCOM plugin would be a better start point.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jtmoore on August 09, 2012, 05:40:28 am
I have several Oregon Scientific and other brands of supported temperature sensors. Some of the readings between these devices in the same location (for testing) can disagree by up to 2 degrees Celsius. It would be nice if I could get them to match my T-Stat reading.
Is there any way to calibrate these Temperature readings in the RFXCOM interface or with the D_TemperatureSensor1.xml standard device to add a simple offset to the readings? Perhaps the RFXCOM plugin could read a new "offset" variable (if present) on each device before writing the value out. Is this possible, or beyond what is achievable with the current architecture?

Thanks
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 09, 2012, 08:06:54 am
I have several Oregon Scientific and other brands of supported temperature sensors. Some of the readings between these devices in the same location (for testing) can disagree by up to 2 degrees Celsius. It would be nice if I could get them to match my T-Stat reading.
Is there any way to calibrate these Temperature readings in the RFXCOM interface or with the D_TemperatureSensor1.xml standard device to add a simple offset to the readings? Perhaps the RFXCOM plugin could read a new "offset" variable (if present) on each device before writing the value out. Is this possible, or beyond what is achievable with the current architecture?

Thanks

There is nothing standard to handle that but as you explained the plugin could read an offset in a variable of the device and take it into account when assigning the updated value. That is even something easy to do. The only annoying thing is that the user will have to add the variable manually on each temperature device, so not something very friendly.
It is an interesting feature request, I will implement it in the next version.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jtmoore on August 09, 2012, 12:31:50 pm
Many thanks. I look forward to seeing in a future release.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: msevestre on August 15, 2012, 12:28:21 pm
Hello

I use a VeraLite. I set up a few weeks ago my RFXTrx v42 with plugin in alpha 5 version.

I could activate Oregon protocol and everything was working perfectly.

I updated my RFXTrx to v46.

RFXMng see a correct functionnality, the rfxtrx probing correctly my temperature probes.

When I plug the RFXTrx on my vera, it is correctly detected as a v46, but there is no way to activate the protocols I need: as soon as I click on a "Enable" button, it switchs back to the "Disable" state in the next second... then I cannot see me probes from my Vera :(

I tried to delete/reinstall the plugin and create again the virtual module, rebooted teh veralite... but I keep the exact same behavior (which is the same under Chrome, Safari, Firefox and IE... then not linked to the web browser...)

Thanks for any help
Matt
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: msevestre on August 15, 2012, 12:31:34 pm
Auto reply: found. "RollerTrol" protocol was the only one enabled by default. Disabling it allowed me to enable la cross & oregon protocols.

Matt
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on August 24, 2012, 05:52:54 pm
Hi,

I have just revived my Rfxrtx 433 and installed it and then the plugin, and all of that seemed to go pretty well, however i would really appreciate it if someone clud help answer my initial findings.

1.) how are the initially enabled products chosen? As it looks like I have 9 set to Enabled by default?

2.) along with having a device with version alpha5 on, I also have a battery powered 'Power Meter" device called RFX Power ELEC2/29058 which is reporting a static value of "2059062" as the KWH used?*

* Looking at an earlier post and the RFXCOM site, ELEC2 is the category for an OWL119 or CM160 which I have neither, but what I do have is OWL Power Saver Remote Control Power Socket? Does this mean the plugin works under the Oregon profile (as RFCom lists it there) and can i help you get the plug to support OWL products now ? No idea why the battery icon is there either.

3.) I'm looking to get an OWL energy monitor OWL119, so your answer to the above question will help loads ;)

4.) Simular to point 1, why are some options preset on the Device Options tab?

5.) The wiki page  http://code.mios.com/trac/mios_rfxtrx  sadly does not show any information, do you want some help to populate it, as some photos and FAQs would be so helpfull to a newbie.

6.) Does it cause any issues to Vera if you regularly unplug the RFXrtx433 so you can use it with your PC?

7.) has anyone modified the JSON file so the text is bigger, bolder ideally with the temperature degree id added

8.) Why does trying to rename a new device result in it being removed/deleted? Are the names fixed ?

9.) Currently the RfXrfx433 is plugged directly into the Veralite, if I want to move it so it comes off a powered hub, will this affect anything?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 25, 2012, 02:51:02 pm
1.) how are the initially enabled products chosen? As it looks like I have 9 set to Enabled by default?

It is something hardcoded in the firmware. So the choice is done by RFXCOM. But then you can change and save your changes.

Quote
2.) along with having a device with version alpha5 on, I also have a battery powered 'Power Meter" device called RFX Power ELEC2/29058 which is reporting a static value of "2059062" as the KWH used?*

* Looking at an earlier post and the RFXCOM site, ELEC2 is the category for an OWL119 or CM160 which I have neither, but what I do have is OWL Power Saver Remote Control Power Socket? Does this mean the plugin works under the Oregon profile (as RFCom lists it there) and can i help you get the plug to support OWL products now ? No idea why the battery icon is there either.

That might be something to check directly with RFXCOM.
Only receiving is supported by the RFXtrx for OWL products. So in the best case, we could update switch power devices in the Vera when you use your remote, but not control the switch powers from the Vera (replacing your remote).
Can you check and provide the received messages when you push the buttons of your remote, using the RFXmngr test application ?

Quote
3.) I'm looking to get an OWL energy monitor OWL119, so your answer to the above question will help loads ;)

I am interesting to know if the decoded values by my plugin are correct.
I got no feedback until now with OWL (119 or 160).
But it should work.

Quote
4.) Simular to point 1, why are some options preset on the Device Options tab?

It is just a bug introduced with Vera firmware 1.5.408 !!! I hope next firmware will correct that. This was ok with previous firmware (1.5.346).

Quote
5.) The wiki page  http://code.mios.com/trac/mios_rfxtrx  sadly does not show any information, do you want some help to populate it, as some photos and FAQs would be so helpfull to a newbie.

Why not. If you have something interesting to provide, I will pubish it.
When I decide to spend time on the plugin, that's true that I prefer add features than writing a doc, even more when english is not my natural language and my english is not really fluent. ;D

Quote
6.) Does it cause any issues to Vera if you regularly unplug the RFXrtx433 so you can use it with your PC?

What I have noticed and may be a bug of the Vera firmware is that you have sometimes to setup again the serial port configuration when you connect the RFXtrx. But I think sometimes I have nothing special to do.
I have not tested all that (deconnect/reconnect) deeply.

Quote
7.) has anyone modified the JSON file so the text is bigger, bolder ideally with the temperature degree id added

When they exist, standard Vera devices are used by my plugin. That's the case for temperature and humidity for example.

Quote
8.) Why does trying to rename a new device result in it being removed/deleted? Are the names fixed ?

I am not aware of this problem but I did not try recently (with last firmware). Normally, you can rename the devices. The name is not used by the plugin. What you must not touch is the "altid".

Quote
9.) Currently the RfXrfx433 is plugged directly into the Veralite, if I want to move it so it comes off a powered hub, will this affect anything?

It could reduce sensibility of the RFXtrx. That is what I noticed but my hub is not a powered hub. With a powered hub, normally, it should make no difference.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on August 25, 2012, 06:10:05 pm
Thanks so much for responding..

I'll aim to get you some more information.

While i have the floor, I have a quick LightwaveRf question which I hope someone can answer.

I have a double (master) lightwaverf socket and I was wondering if I could use the second switch another way? Could i just connect it to the power (live only with the earth two) so that it would registers via the plugin and Vera, and then I'm curious if I can use it as a trigger for a Vera scene (maybe like a volume control) ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 26, 2012, 05:18:26 am
For scene triggering, please read this topic: http://forum.micasaverde.com/index.php/topic,11080.0.html
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on August 26, 2012, 05:13:10 pm
Hi @lolodomo

A couple of things for you

In regards to documentation, I've had a go at the first part of a user guide for you on my tech blog site, intially to help people starting off, please have a look ant let me have any/all feedback - http://nodecentral.wordpress.com/2012/08/26/working-vera-on-a-different-frequency-rfxcoms-rfxrtx433/ - if you like any we can use it on the wiki, I'll aim to move on to the modes and other settings on the next post.

In regards to the Owl Power Saver multi socket i mentioned earlier, looking in the RFXmngr it's reporting the following, however if I turn the power socket off at the wall, the same information came up, so i did some digging and you will not believe this - the signal only turned out to be from my neighbour who has an old CM119, that still has some batteries in, yet not connected.. !!

------------------------------------------------
115A015B7182000000000000001B73512679
Packettype    = ENERGY
subtype       = ELEC2 - OWL CM119, CM160
Sequence nbr  = 91
ID            = 29058
Count         = 0
Instant usage = 0 Watt
total usage   = 2059062.37872542 Wh
Signal level  = 8
Battery       = OK
------------------------------------------------

in regards to the OWL Powersaver and its associated remote, If I put on ARC mode it will captures all the commands i send from each of the 4 control buttons I press (extract below)

------------------------------------------------
080301751900000000
Packettype        = UNDECODED RF Message
UNDECODED ARC:1900000000
------------------------------------------------

Is this the sort of information Bert and RFXCOM needs to explore adding the functionality ?
Your help and guidance on the above would be greatly appreciated.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 27, 2012, 08:42:35 am
in regards to the OWL Powersaver and its associated remote, If I put on ARC mode it will captures all the commands i send from each of the 4 control buttons I press (extract below)

------------------------------------------------
080301751900000000
Packettype        = UNDECODED RF Message
UNDECODED ARC:1900000000
------------------------------------------------

Is this the sort of information Bert and RFXCOM needs to explore adding the functionality ?

Yes
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 27, 2012, 09:45:37 am
In regards to documentation, I've had a go at the first part of a user guide for you on my tech blog site, intially to help people starting off, please have a look ant let me have any/all feedback - http://nodecentral.wordpress.com/2012/08/26/working-vera-on-a-different-frequency-rfxcoms-rfxrtx433/ - if you like any we can use it on the wiki, I'll aim to move on to the modes and other settings on the next post.

Here is the minimal summary I would expect
- Presentation
- Installation and setup (what you have done is a very good start point - what is missing is mainly a descripton of how to setup what protocol have to be received by the RFXtrx)
- Automatic and manual creation of Vera devices
- How to change the type of certain Vera device
- How to setup temperature and speed units
- List of devices supported by the plugin and limitations (using a table)

There are few advanced usages to describe in a full documentation like
- how to associate several physical devices to a unique Vera device (variable Association)
- variable RepeatEvent on BinaryLight devices
- variable KopplaProgrammed
- variable AdjustConst on temperature, humidity, barometer and UV devices
...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on August 27, 2012, 09:56:56 am
in regards to the OWL Powersaver and its associated remote, If I put on ARC mode it will captures all the commands i send from each of the 4 control buttons I press (extract below)

------------------------------------------------
080301751900000000
Packettype        = UNDECODED RF Message
UNDECODED ARC:1900000000
------------------------------------------------

Is this the sort of information Bert and RFXCOM needs to explore adding the functionality ?

Yes

@lolodomo - I spoke to Bert and sadly it's not possible to add the OWL remote I have, as it's using a protocol that is about the same as the ARC protocol but using another format. So the RFXtrx433 is not able to decode it. The CM119 however is now connected and looks to be working really well?

Regarding documentation,(Thanks for your feedback) Bert has taken my initial posting on how to set up the RFXrtx433 with Vera and published it on his site http://www.rfxcom.com/downloads.htm. - So you might want to add this (or maybe my blog post) to your first post,  as we can develop it together to benefit not just this forum but others too.

With your help I'd really like to go into the process of how to use each tab too, (we can perhaos leave some stuff to the RFXCOM site) but as I only got my RFXrtx a couple of days ago and I do not have very many devices running - if you want to private message me some of your notes, I can write them up.?

I also think an FAQ is a great thing to have too, every plug in on this site and the marketplace should have one by default, it saves lots of time in the long run.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 27, 2012, 06:17:59 pm
For very curious and/or impatient users, amongst changes I have committed this evening in the trunk, you can find:
- Ability to repeat ON and OFF events for BinaryLight devices setting variable RepeatEvent to 1 => this will allow triggering Vera scene using remotes
- Ability to adjust reported values for temperature, humidity, UV and barometric sensors using variable AdjustConst => this will allow calibrating sensors

In the two cases, no need to create manually the variable(s), the variables are automatically added after the first restart done after the installation of new files. When you modify one of these variables in the advanced panel, don't forget to reload after the change.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 28, 2012, 04:04:05 pm
For very curious and/or impatient users, amongst changes I have committed this evening in the trunk, you can find:
- Ability to repeat ON and OFF events for BinaryLight devices setting variable RepeatEvent to 1 => this will allow triggering Vera scene using remotes

I just committed a new change because, as I explained in another topic; I decided to change my approach to manage remote controls.
Now I create a device of type SceneControl1. This device triggers events when ON buttons or OFF buttons of the remote are pushed.

When you will push the ON button "2" of your remote (button matching device id C02 for example), two devices will be created:
- a BinaryLight device corresponding to C02 + status will be set to ON
- a scene controller device corresponding to your remote + event "scene number 2 is activated" will be triggered

As a conclusion, the RepeatEvent variable is no more necessary as we can use the event from the scene controller (event is repeated on this device) rather than the event from the binary light (that is not repeated.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: apmcconv on August 29, 2012, 01:17:37 pm
Hi,

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.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: apmcconv on August 29, 2012, 02:59:13 pm
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.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: jtmoore on August 29, 2012, 06:52:12 pm
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.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: apmcconv on August 30, 2012, 05:25:43 am
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.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on August 30, 2012, 05:56:03 am
@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.

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: apmcconv on August 30, 2012, 06:26:12 am
b_weijenberg, well spotted. You are correct and that explains why it didn't work. Thank you.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on August 30, 2012, 12:14:51 pm
@lolodomo

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?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 30, 2012, 02:09:04 pm
@lolodomo

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?

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).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on August 30, 2012, 02:43:26 pm
@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..
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on August 30, 2012, 03:00:40 pm
@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?

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.

Quote
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, ...

Quote
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..


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).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on August 30, 2012, 03:08:39 pm
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 ;)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 01, 2012, 02:43:05 am
@lolodomo

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.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 01, 2012, 05:22:25 am
@lolodomo

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 will try to finish security and remote stuff this week-end...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on September 02, 2012, 06:56:25 pm
Hi lolodomo :)

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)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 03, 2012, 04:13:54 am
Hi lolodomo :)

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)

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.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: kevinvanlooy on September 05, 2012, 11:23:42 am
HI All,

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 ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on September 05, 2012, 02:59:37 pm
ELRO AB400 receive is not supported!

See the list of devices supported for receive and/or transmit in chapter 2.2
http://www.rfxcom.com/documents/RFXtrx%20User%20Guide.pdf

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.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 05, 2012, 03:25:16 pm
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...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 06, 2012, 08:14:55 am
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 ;)

But the message logged will be a non-decode message.
I am not really sure to understand what could the usage...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 06, 2012, 08:24:04 am
mood settings (as mood is normally used for room in terms of LWRF, but plugin has only global mood settings)

If I create a new device for each LightwaveRF remote with 5 mood buttons, would it be ok ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: kevinvanlooy on September 06, 2012, 01:34:45 pm
Hi All,  yes me again :)

Today received  my cresta temperature sensors (2)  Powered them and "Voila..." visible in Vera thru the RfxCom miracle :)
the only problem (propably not) is that it created multiple devices which doesn't do anything... is this because it can have 3 channels?
so per sensor I have a temp and a  hygro, but then times 3 .

Can these device be removed(they come back on the next data push) or are they needed?


ps.

Sorry to Hijack this thread again, but didn't find the info needed and making a new topic for it seemed kinda trivial..

Regards
Kevin
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 06, 2012, 02:12:24 pm
Hi All,  yes me again :)

Today received  my cresta temperature sensors (2)  Powered them and "Voila..." visible in Vera thru the RfxCom miracle :)
the only problem (propably not) is that it created multiple devices which doesn't do anything... is this because it can have 3 channels?
so per sensor I have a temp and a  hygro, but then times 3 .

Strange. The three temperature devices for one sensor are displaying the same value ?
You should contact RFXCOM to check if it is normal. Or RFXCOM will probably answer directly in this topic.

Quote
Can these device be removed(they come back on the next data push) or are they needed?

One solution is to set variable AutoCreate to value 0 and reload. Then you suppress the devices you don't need. And that's all.

Quote
Sorry to Hijack this thread again, but didn't find the info needed and making a new topic for it seemed kinda trivial..

No problem, I think you posted at the right place.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 06, 2012, 05:57:04 pm
Hi, I've just got some Siemens LightwaveRF power sockets which came with a remote control and I'm having real trouble seeing/creating anything to do with them via the plug-in.

Protocol wise - I only have AC and Oregon Scientific Selected.

A power socket is in position and paired with button '3' on the remote with the slider (which has options a-d) set to 'a' yet nothing is appearing on the Vera UI.  Even if i click any button on the remote nothing happens.

What am I missing ?

My goal is to have Vera know and use the '3' remote code to turn on/off the socket
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: kevinvanlooy on September 07, 2012, 02:37:01 am
In order to show what I have with the multiple devices for the cresta temp sensors,
see the attached screen cap.

The values aren't duplicate just a number of devices that just sit there..

Regards
Kef
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 07, 2012, 02:52:20 am
Hi, I've just got some Siemens LightwaveRF power sockets which came with a remote control and I'm having real trouble seeing/creating anything to do with them via the plug-in.

Protocol wise - I only have AC and Oregon Scientific Selected.

A power socket is in position and paired with button '3' on the remote with the slider (which has options a-d) set to 'a' yet nothing is appearing on the Vera UI.  Even if i click any button on the remote nothing happens.

What am I missing ?

My goal is to have Vera know and use the '3' remote code to turn on/off the socket

Siemens uses LightwaveRF (AD) protocol.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 07, 2012, 02:54:06 am
In order to show what I have with the multiple devices for the cresta temp sensors,
see the attached screen cap.

The values aren't duplicate just a number of devices that just sit there..

Regards
Kef

Please check with the RFXmngr RFXCOM application what messages re received.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: bthovda on September 07, 2012, 06:38:49 am
Hi again!

Any progress on including security devices like the smoke detectors from Nexa. KD101?

- BT
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 07, 2012, 07:18:05 am
Hi again!

Any progress on including security devices like the smoke detectors from Nexa. KD101?

- BT

I will add KD101 in the coming soon release.

I hope I will find time to finish and release alpha 6 version before the end of the coming week-end.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 07, 2012, 07:20:07 am
Is KD101 only smoke detector ?
What is the "pair" feature ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: bthovda on September 07, 2012, 07:43:22 am
Is KD101 only smoke detector ?
What is the "pair" feature ?

Well i guess you can pair the detectors.
this way they "see" each other.
When one detector is activated, the other detectors that its paired with, will also make some alarm beeps..
I guess the pairing process is done when installing them.

- BT
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 07, 2012, 05:46:59 pm
Siemens uses LightwaveRF (AD) protocol.

Hi @lolodomo

Thanks for the direction on using AD, I completely misread the protocol on the rfxcom user guide. The problem I now have is that the plug and one press of the remote, it's created the following 2 devices.

1 = A Binary Light called "RFX Light L5.0/F0D664/03"
2 = A Window Covering called "RFX Window WC/L5.0/000003/03"

The above Binary Light device works well (on/off) which allows me to control the socket (love it!) but it seems strange that Vera deems a power socket/outlet as a light

Lolodomo - Doyou have any idea why the plug is being seen as a Window Covering?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 07, 2012, 06:10:05 pm
Siemens uses LightwaveRF (AD) protocol.

Hi @lolodomo

Thanks for the direction on using AD, I completely misread the protocol on the rfxcom user guide. The problem I now have is that the plug and one press of the remote, it's created the following 2 devices.

1 = A Binary Light called "RFX Light L5.0/F0D664/03"
2 = A Window Covering called "RFX Window WC/L5.0/000003/03"

The above Binary Light device works well (on/off) which allows me to control the socket (love it!) but it seems strange that Vera deems a power socket/outlet as a light

Lolodomo - Doyou have any idea why the plug is being seen as a Window Covering?

It looks like the binary light device has been created by a command coming from a remote having id F0D664 while the window covering device has been created by a command coming from a remote having id 000003.
Do you have only one remote ?
Maybe an error of the RFXtrx ?
Try deleting the WC device, reload and check if the device is created again when you push the remote button.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 07, 2012, 06:22:40 pm
Hi@lolodomo

I only have the 1 remote and the only button I pressed (was the one paired with the plug which) was button 3 on the remote.  To help you, I've just pressed all the other buttons 1,2 & 4 which have all created a binary light on the UI devices called as follows...

"RFX Light L5.0/F0D664/01"
"RFX Light L5.0/F0D664/02"
"RFX Light L5.0/F0D664/04"

"RFX Light L5.0/F0D664/03" - is the one paired with a plug socket.

As I have bought a pack of 3 Siemens sockets with remote, I will try and remove and then install and pair up another socket and see what comes up.

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 08, 2012, 03:43:06 am
Hi - I removed the Window Covering called RFX Window WC/L5.0/000003/03 and have so far been unable to make it come back.

Therefore I can only assume the RFXrtx misread the remote signal and that's what your plugin translated..

It's a shame there's not a device profile/icon in Vera more suited to a power socket, however I understand the concept of a binary light and it being either on/off, plus I guess there is no way for the system to know what the remote is being used to control..
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 08, 2012, 09:51:28 am
For impatient users, I just committed new code that completes security part and add scene control from security/X10/ARC/AC/LightwaveRF remotes.


That means that now ARC (old protocol) and AC (new protocol) doorbells can be managed.
For ARC doorbell, scene with a number from 33 to 48 (it depends on the unit code defined for the doorbell) will be activated. I have suppressed the door device.
For AC doorbell, scene nimber 100 will be activated.

Before the final release, remains to do:
- new remote device for LightwaveRF including mood buttons
- new remote device for ATI/PC Medion remotes
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 08, 2012, 04:40:35 pm
Hi @lolodomo - it's always great to see what your working on..

And the last thing I ever want to do is sound impatient, but I did want to see if i could try and keep the idea we discussed a while back (below) on your radar/road map for a future release ;)

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 ;)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 08, 2012, 04:50:32 pm
Hi @lolodomo - it's always great to see what your working on..

And the last thing I ever want to do is sound impatient, but I did want to see if i could try and keep the idea we discussed a while back (below) on your radar/road map for the future ;)

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 keep the idea but only for a future version.

I want to release a new version as soon as possible because the gap is already big between the new and the previous version, and so my priority is to finish first the current work.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 09, 2012, 05:52:28 am
@lolodomo

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 just committed changes that add support for ATI and Medion remotes.
Please try and give me a feedback.
A Vera event will be triggerred each time you push a button of the remote, the scene number is the code of the button (please check the RFXCOM documentation).
You can send a command from the Vera UI, enter the code and push the "Send" button. And you can send an order from a scene using the callback "SendCode" (luup.call_action ...).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 09, 2012, 05:54:32 am
I have done some changes with scene numbers:

-- ON/OFF (activated/deactivated): 1-16
-- SET LEVEL (activated only): 17-32
-- LOCK/UNLOCK (activated/deactivated): 33-48
-- OPEN (activated only): 49-64
-- CLOSE (activated only): 65-80
-- STOP (activated only): 81-96
-- GROUP ON/OFF (activated/deactivated): 100
-- GROUP LEVEL (activated only): 101
-- DIM (activated only): 102
-- BRIGHT (activated only): 103
-- ALL LOCK (activated only): 105
-- MOOD1 (activated only): 111
-- MOOD2 (activated only): 112
-- MOOD3 (activated only): 113
-- MOOD4 (activated only): 114
-- MOOD5 (activated only): 115
-- PANIC/END PANIC (activated/deactivated): 120
-- ARM AWAY (activated only): 121
-- ARM HOME (activated only): 122
-- DISARM (activated only): 123
-- PAIR (KD101) (activated only): 124
-- CHIME (activated only): 131-146
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 09, 2012, 05:57:21 am
For impatient users, I just committed new code that completes security part and add scene control from security/X10/ARC/AC/LightwaveRF remotes.

I have done final changes to display few buttons directly on the dashboard.



I am now very close to release the alpha 6 version...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 11, 2012, 11:31:52 am
Hi @lolodomo - it's always great to see what your working on..

And the last thing I ever want to do is sound impatient, but I did want to see if i could try and keep the idea we discussed a while back (below) on your radar/road map for a future release ;)

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 ;)

What do you expect for each message. I will not decode each message like RFXmngr is doing. I would have only one line per message and this line would contain mainly the undecoded message.

Did you think about the datamine and logging plugin ? If I put the content of each new message in a variable, this plugin allows you, I think, to log all changes on this variable.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 11, 2012, 07:20:16 pm
I just committed a change that could interest certain people. It allows the Vera to exchange with an USB RFXtrx not connected locally to the Vera but connected to a remote PC.
I did my tests with a PC running Windows XP and the software VSPE (virtual serial ports emulator). This software provide a remote TCP access to a local serial port. You have to select type "TcpServer" when creating the virtual device in VSPE and port 10000 (the port value is currently forced to this value in my code).
Note that it should work on other OS and with other softwares than VSPE too.
http://www.eterlogic.com/Products.VSPE.html

PS: I now plan to release a new version (alpha 6) probably in the next evening.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Quinten on September 12, 2012, 03:38:54 am
I just committed a change that could interest certain people. It allows the Vera to exchange with an USB RFXtrx not connected locally to the Vera but connected to a remote PC.
I did my tests with a PC running Windows XP and the software VSPE (virtual serial ports emulator). This software provide a remote TCP access to a local serial port. You have to select type "TcpServer" when creating the virtual device in VSPE and port 10000 (the port value is currently forced to this value in my code).
Note that it should work on other OS and with other softwares than VSPE too.
http://www.eterlogic.com/Products.VSPE.html

PS: I now plan to release a new version (alpha 6) probably in the next evening.

That is great, thanks!  I've not been very active with my HA progress the last couple of months, but am collecting momentum to start it all up again, and this may have just filled the bucket to the top or over ;)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 12, 2012, 02:04:23 pm
New version alpha 6 of the plugin is now available.
Plugin files are available at http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha6#

What's new in version alpha 6:
- Plugin is up to date with RFXtrx firmware v49
- Child devices management revisited (fixed and enhanced)
- Support for X10 security remotes added
- Support for Meiantech/Atlantic security remotes added
- Support for KD101 smoke detector added
- Support for RUBiCSON temperature sensor added
- Support for Viking 02035, 02038 humidity sensors added
- Support for TFA 30.3133 temperature sensor added
- Support for Hasta blinds added
- Support for Philips SBC lighting added
- New devices created to match remote controls and give ability to trigger Vera scene from remote buttons, plus new buttons to send specific commands like group off, dim, bright, mood, ... etc
- LightwaveRF panel suppressed from the main plugin device; replaced by a new dedicated device
- Support for ATI and Medion remotes added
- Setup of received protocols updated
- "Logs" and "Notifications" panels added to barometer, rain, wind and UV devices
- Ability to adjust reported values for temperature, humidity, UV and barometric sensors using the variable "AdjustConst"
- Ability to repeat ON and OFF events for BinaryLight devices setting the variable "RepeatEvent" to 1
- Callback added to simulate receiving of message (for testing purposes)
- Support added for USB RFXtrx connected to a remote machine providing an IP access to a local serial port (using VSPE on Windows for example)

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 12, 2012, 05:30:16 pm
What do you expect for each message. I will not decode each message like RFXmngr is doing. I would have only one line per message and this line would contain mainly the undecoded message.

Did you think about the datamine and logging plugin ? If I put the content of each new message in a variable, this plugin allows you, I think, to log all changes on this variable.

Hi lolodomo, the desire is to somehow see the stream of information thats being seen by the rfxrtx433 unit via the UI.

Just to confirm my own thinking/understanding - Am I correct in saying that any information/message that the plugin can 'decode' will a) be created into a new device (if not already present) and b) will then going forward, update that particular devices variables with new information it receives ?

If so, then to keep it simple, the focus is really only on the information that your plugin is seeing but cannot or is not decoding?

I'm afaid i do not know what a normal/undecoded stream looks like, is it one long string or is it broken up over multiple lines? 

If it's recieves one long string then that message/information can be placed in a single new variable
If its received as multiple lines of information then multiple variables would be good, representing each line e.g RFXrtx undec L1, RFXrtx undec L2, RFXrtx undec L3 etc.?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on September 13, 2012, 04:18:54 am
parkerc,

undec is only for diagnostic purposes to enable RFXCOM to add new device protocols.
For normal use do not enable undec because you will also receive a lot of rubbish due to received RF noise packets.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 13, 2012, 05:17:02 am
What I could do easily is to log the last received message (hexadecimal format) in a variable + add the messages in the logs. A tail + grep command on the log file will show you in real time all the received messages. And you could even use the datamine plugin to trace all changes of the variable.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TommyE on September 13, 2012, 06:18:03 am
New version alpha 6 of the plugin is now available.
Plugin files are available at http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha6#

What's new in version alpha 6:
- Plugin is up to date with RFXtrx firmware v49
- Child devices management revisited (fixed and enhanced)
- Support for X10 security remotes added
- Support for Meiantech/Atlantic security remotes added
- Support for KD101 smoke detector added
- Support for RUBiCSON temperature sensor added
- Support for Viking 02035, 02038 humidity sensors added
- Support for TFA 30.3133 temperature sensor added
- Support for Hasta blinds added
- Support for Philips SBC lighting added
- New devices created to match remote controls and give ability to trigger Vera scene from remote buttons, plus new buttons to send specific commands like group off, dim, bright, mood, ... etc
- LightwaveRF panel suppressed from the main plugin device; replaced by a new dedicated device
- Support for ATI and Medion remotes added
- Setup of received protocols updated
- "Logs" and "Notifications" panels added to barometer, rain, wind and UV devices
- Ability to adjust reported values for temperature, humidity, UV and barometric sensors using the variable "AdjustConst"
- Ability to repeat ON and OFF events for BinaryLight devices setting the variable "RepeatEvent" to 1
- Callback added to simulate receiving of message (for testing purposes)
- Support added for USB RFXtrx connected to a remote machine providing an IP access to a local serial port (using VSPE on Windows for example)

Hello

I just bought an RFXCOM, and tried your plugin.

I must say it is an impressive piece of work !!

It works great with some ESIC WT450 Temperature and Humidity sensors, bought at ClasOhlson i Norway, even shows battery status :) Cool.

I have a few KD101 smoke detectors around the house, seeing Alpha6 supports them I wonder do I need to do anything to make them appear in Vera?


Thanks
TommyE
Title: Plugin for the USB RFXtrx from RFXCOM
Post by: bthovda on September 14, 2012, 02:18:18 am
New version alpha 6 of the plugin is now available.
Plugin files are available at http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha6#

What's new in version alpha 6:
- Plugin is up to date with RFXtrx firmware v49
- Child devices management revisited (fixed and enhanced)
- Support for X10 security remotes added
- Support for Meiantech/Atlantic security remotes added
- Support for KD101 smoke detector added
- Support for RUBiCSON temperature sensor added
- Support for Viking 02035, 02038 humidity sensors added
- Support for TFA 30.3133 temperature sensor added
- Support for Hasta blinds added
- Support for Philips SBC lighting added
- New devices created to match remote controls and give ability to trigger Vera scene from remote buttons, plus new buttons to send specific commands like group off, dim, bright, mood, ... etc
- LightwaveRF panel suppressed from the main plugin device; replaced by a new dedicated device
- Support for ATI and Medion remotes added
- Setup of received protocols updated
- "Logs" and "Notifications" panels added to barometer, rain, wind and UV devices
- Ability to adjust reported values for temperature, humidity, UV and barometric sensors using the variable "AdjustConst"
- Ability to repeat ON and OFF events for BinaryLight devices setting the variable "RepeatEvent" to 1
- Callback added to simulate receiving of message (for testing purposes)
- Support added for USB RFXtrx connected to a remote machine providing an IP access to a local serial port (using VSPE on Windows for example)

Hello

I just bought an RFXCOM, and tried your plugin.

I must say it is an impressive piece of work !!

It works great with some ESIC WT450 Temperature and Humidity sensors, bought at ClasOhlson i Norway, even shows battery status :) Cool.

I have a few KD101 smoke detectors around the house, seeing Alpha6 supports them I wonder do I need to do anything to make them appear in Vera?


Thanks
TommyE

Regarding kd101, Wondering about the same! Should it be added automatically or manually?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 14, 2012, 06:56:27 am
For JD101, you have to push the test button on the KD101 and a dev ice will be added in the Vera.
The device created will be a security remote device, not a smoke detector. This device has the ability to send a panic order to the smoke detectors.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TommyE on September 14, 2012, 09:47:03 am
For JD101, you have to push the test button on the KD101 and a dev ice will be added in the Vera.
The device created will be a security remote device, not a smoke detector. This device has the ability to send a panic order to the smoke detectors.

I tried that already, to no avail.

My detector says KD-101LD, maybe it is not the same thing?

Also, which RFXCOM protocol do I have to enable for the KD-101

Thanks
Tommy
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 15, 2012, 04:18:05 am
For JD101, you have to push the test button on the KD101 and a dev ice will be added in the Vera.
The device created will be a security remote device, not a smoke detector. This device has the ability to send a panic order to the smoke detectors.

I tried that already, to no avail.

My detector says KD-101LD, maybe it is not the same thing?

Also, which RFXCOM protocol do I have to enable for the KD-101

Thanks
Tommy

I don't know, that's not mentioned in the RFXtrx user manual. You have to ask RFXCOM support.


For information, I already got a positive feedback from a user using a KD101 clone.
Note that you can trigger through the Vera UI (panic button) the siren on the KD101, but there is no way to stop it from the Vera ! I assume the siren stops after few seconds.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Intrepid on September 15, 2012, 08:43:52 am
Any idea about adding support for these?

http://www.blinds.com/control/product/productID,97658

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 15, 2012, 09:19:12 am
Any idea about adding support for these?

http://www.blinds.com/control/product/productID,97658

At my knowledge, it is not a product supported by the RFXCOM RFXtrx.
First question would be to know if it used 433 MHz ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 15, 2012, 09:20:40 am
For JD101, you have to push the test button on the KD101 and a dev ice will be added in the Vera.
The device created will be a security remote device, not a smoke detector. This device has the ability to send a panic order to the smoke detectors.

I tried that already, to no avail.

My detector says KD-101LD, maybe it is not the same thing?

Also, which RFXCOM protocol do I have to enable for the KD-101

Thanks
Tommy

I don't know, that's not mentioned in the RFXtrx user manual. You have to ask RFXCOM support.

I was informed (PM) that the protocol to enable is X10.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 16, 2012, 04:40:33 am
Parkerc,

I just initialized the wiki page. Ok, this is currently mainly a summary. ;D
I point to your blog for the installation guide. Is it ok for you like that ?
http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 16, 2012, 06:32:35 am
Parkerc,

I just initialized the wiki page. Ok, this is currently mainly a summary. ;D
I point to your blog for the installation guide. Is it ok for you like that ?
http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#

@lolodomo - that is totally fine with me, in fact it's my pleasure to help and contribute to all you have done ;)  I also have another post in draft designed to help people through selecting the various protocols - I'll post the link here later for you to comment/approve.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Intrepid on September 16, 2012, 08:06:52 am
Any idea about adding support for these?

http://www.blinds.com/control/product/productID,97658

At my knowledge, it is a product supported by the RFXCOM RFXtrx.
First question would be to know if it used 433 MHz ?

Reply from rxfcom:

Quote
No, this type is not supported.
The RFXtrx433 can control rollertrol.com motors.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: DRuw on September 16, 2012, 03:29:40 pm
Hello all!
First of all, let me apologise for my noob-ness...
I am a complete amature in domotica but I am very eager to learn:)
I bought some items including a Vera3 and a RFXCOM unit but I cant seem to get them to work for some reason.
It starts with the manual in the topic start: I cant seem to get the files uploaded since my vera only displays the first 10 luup files "upload boxes".
I thought that in that case, I can install the app in the "Install Apps" menu and that worked: plugin appeared.
Now the problem started... it says IP Address attribute must be configured. and the RFXCOM controller device notes a red flag with "Lua Startup Failure".
The Serial port has been changed acc. starter post but this doesnt change anything.

What am I doing wrong?
If I go to the settings and change the "Controlled via" dropdown to "RFXCOM controlled device" the device dissapears.. (crossreference I think?)

I am guessing that my Vera does not know where my RFXCOM is and needs an adress or something but where can I find this?

Thanks for the help!!

edit: when I go to the settings of the RFXCOM controller device, the only thing I can change in teh Settings tab is the Harrison curtain (which I can add)
edit2: when I create another device in the apps-> rfxcom menu, a second one appears (same error) but when I want to remove this one, I have to remove the complete plugin as well???
edit3: when I change the controlled via window to ftdi_sio (which I recognozed from the serial port settings, it error disappears but how do I add devices then? (and is this even correct???)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 16, 2012, 04:32:24 pm
Parkerc,

I just initialized the wiki page. Ok, this is currently mainly a summary. ;D
I point to your blog for the installation guide. Is it ok for you like that ?
http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#

@lolodomo - that is totally fine with me, in fact it's my pleasure to help and contribute to all you have done ;)  I also have another post in draft designed to help people through selecting the various protocols - I'll post the link here later for you to comment/approve.

That would be even better if you can provide directly the text (and pictures ?) for the wiki page.
You are welcome if you want to contribute to the wiki page.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 16, 2012, 04:33:20 pm
Any idea about adding support for these?

http://www.blinds.com/control/product/productID,97658

At my knowledge, it is a product supported by the RFXCOM RFXtrx.
First question would be to know if it used 433 MHz ?

Reply from rxfcom:

Quote
No, this type is not supported.
The RFXtrx433 can control rollertrol.com motors.

Oups, the "not" was missing in my sentence: it is not a product supported ...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 16, 2012, 04:38:07 pm
Hello all!
First of all, let me apologise for my noob-ness...
I am a complete amature in domotica but I am very eager to learn:)
I bought some items including a Vera3 and a RFXCOM unit but I cant seem to get them to work for some reason.
It starts with the manual in the topic start: I cant seem to get the files uploaded since my vera only displays the first 10 luup files "upload boxes".
I thought that in that case, I can install the app in the "Install Apps" menu and that worked: plugin appeared.
Now the problem started... it says IP Address attribute must be configured. and the RFXCOM controller device notes a red flag with "Lua Startup Failure".
The Serial port has been changed acc. starter post but this doesnt change anything.

What am I doing wrong?
If I go to the settings and change the "Controlled via" dropdown to "RFXCOM controlled device" the device dissapears.. (crossreference I think?)

I am guessing that my Vera does not know where my RFXCOM is and needs an adress or something but where can I find this?

Thanks for the help!!

edit: when I go to the settings of the RFXCOM controller device, the only thing I can change in teh Settings tab is the Harrison curtain (which I can add)
edit2: when I create another device in the apps-> rfxcom menu, a second one appears (same error) but when I want to remove this one, I have to remove the complete plugin as well???
edit3: when I change the controlled via window to ftdi_sio (which I recognozed from the serial port settings, it error disappears but how do I add devices then? (and is this even correct???)

I think you have installed the wrong plugin.
What RFXCOM product did you buy ? USB or LAN version ?
It exists 2 Vera plugins, one for each product, one for the USB RFXtrx433 (my plugin) and one for the RFXLAN managed by evanes.
If you installed from the App Store, you installed the plugin for the RFXLAN as my plugin is not yet available on the App Store.
To upload the files, you can do it in several steps. Just restart after uploading all the files.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 17, 2012, 03:39:08 am
For JD101, you have to push the test button on the KD101 and a dev ice will be added in the Vera.
The device created will be a security remote device, not a smoke detector. This device has the ability to send a panic order to the smoke detectors.

I tried that already, to no avail.

My detector says KD-101LD, maybe it is not the same thing?

Also, which RFXCOM protocol do I have to enable for the KD-101

Thanks
Tommy

I don't know, that's not mentioned in the RFXtrx user manual. You have to ask RFXCOM support.

I was informed (PM) that the protocol to enable is X10.

Finally, after checking, RFXCOM informed me that KD101 does not require X10 protocol enabling. KD101 is always taken into account.

RFXCOM tested with model KD-101LA.

Ap15e reported to me a positive feedback using a KD101 clone: Flamingo FA20RF

So, for the KD-101LD, you might need to exchange directly with RFXCOM support.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 17, 2012, 03:39:53 am
That would be even better if you can provide directly the text (and pictures ?) for the wiki page.
You are welcome if you want to contribute to the wiki page.

While its always nice to have people visit my blog (for some insightful commentary on the world of HA ;) (yeah right!) - i agree, it would be sensible to use the wiki. I assumed it would need to go there eventually, maybe at Beta or full release stage. I think i have an account to the wiki site, so happy to help out there too if you want to give me access as an editor.

While you do that, here's a link to an early draft of my next post on the 433mhz Protocols. http://nodecentral.wordpress.com/2012/09/16/138/ - please let me have any comments/suggestions you have.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on September 17, 2012, 06:11:31 pm
Hi folks,

Lolodomo, thanks for your hard work !

I've start digging into the Blyss/Avidsen support, that the last firmware of the RFXtrx is supporting.
So I've bought one of the Blyss plug to see how it was working.
Those devices are one way only (for 433Mhz ones supported by the RFXtrx): a message is sent from a remote traditionally or in our case the Vera.
So it is far more complex than the X10 security devices :-)

On another box, a association message is issued to the plug, then off/on message are sent.
So we need those four messages from the RFX/TRX an I guess a particular modus operandi to create the device (I guess something like a manual process that would include this association message).

Anyone would have seen those message codes somewhere ?

Chris
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on September 17, 2012, 06:43:52 pm
Oups, actually found the documentation on RFXcom web site.

0x0B - 0x15 - 0x00 that's for Blyss.
then seq number
then id+ groupcode + unitcode.
then the cmd:  0x02 for group on, then seqcmdnbr = 0x00

Will try to code over the next days and see how it works.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: deursen on September 18, 2012, 05:15:24 am
Maybe a silly question, but what is the difference between alfa6 and the version that is available at mios app store? There it is named v1.1
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 18, 2012, 07:06:09 am
Maybe a silly question, but what is the difference between alfa6 and the version that is available at mios app store? There it is named v1.1

It erxists 2 plugins for two different RFXCOM products.

In code.mios.com, the two versions are available:
http://code.mios.com/trac/mios_rfxcom# for the RFXLAN product
http://code.mios.com/trac/mios_rfxtrx# for the USB RFXtrx product

At Mios app store, only the first plugin is available, mine is not yet (will be soon).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 18, 2012, 07:10:00 am
Oups, actually found the documentation on RFXcom web site.

0x0B - 0x15 - 0x00 that's for Blyss.
then seq number
then id+ groupcode + unitcode.
then the cmd:  0x02 for group on, then seqcmdnbr = 0x00

Will try to code over the next days and see how it works.

The message for Blyss is described in the RFXCOM SDK.
What is different with similar protocols is that you have a notion of group. That's not clear for me.

And sorry, I did not understand your explanations relative to the association messages.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on September 18, 2012, 08:06:58 am
The Blyss remote has 4 On/Off buttons and a group code (a b c d) switch.
And each remote has a unique ID.
These parameters are used by the RFXtrx433 to transmit a Blyss command.

See the picture of the Blyss remote
http://www.touteladomotique.com/index.php?option=com_content&view=article&id=545:2012082001&catid=25:domotique&Itemid=13
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 18, 2012, 08:53:52 am
What's new in version alpha 6:
- Support added for USB RFXtrx connected to a remote machine providing an IP access to a local serial port (using VSPE on Windows for example)

Hi lolodomo, I've had a go at installing VCPE (by eterlogic.com) on a Windows 7 machines but I just can't seem to work out what i need to update in Alpha 6 so it looks for that rather than a local port, I tired to create a device type in VCPE for the rfxrtx433 to be a TCP server? Was that right ? What settings did you use ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 18, 2012, 09:47:27 am
While you do that, here's a link to an early draft of my next post on the 433mhz Protocols. http://nodecentral.wordpress.com/2012/09/16/138/ - please let me have any comments/suggestions you have.

What is missing, IMHO:
- the protocols to be enabled or disabled concern only receiving/decoding by the RFXtrx
- explain that these settings are saved in a non volatile memory (in the RFXtrx)
- explain why and when saving the settings

FYI, the firmware defines what are the protocols enabled by default. They are updated after each firmware installation.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 18, 2012, 09:53:32 am
What's new in version alpha 6:
- Support added for USB RFXtrx connected to a remote machine providing an IP access to a local serial port (using VSPE on Windows for example)

Hi lolodomo, I've had a go at installing VCPE (by eterlogic.com) on a Windows 7 machines but I just can't seem to work out what i need to update in Alpha 6 so it looks for that rather than a local port, I tired to create a device type in VCPE for the rfxrtx433 to be a TCP server? Was that right ? What settings did you use ?

VSPE, not VCPE.

I wrote an explanation on this french forum: http://www.touteladomotique.com/forum/viewtopic.php?f=48&t=7218&start=324#p68693
If a Google translation is not sufficient, I will explain again.
But it is very simple.
Main things to remind: define a device of type TcpServer in VSPE and use port 10000. Then create a new device in Vera UI setting the IP address with the IP of your PC.
That's all.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 18, 2012, 09:56:16 am
The Blyss remote has 4 On/Off buttons and a group code (a b c d) switch.
And each remote has a unique ID.
These parameters are used by the RFXtrx433 to transmit a Blyss command.

See the picture of the Blyss remote
http://www.touteladomotique.com/index.php?option=com_content&view=article&id=545:2012082001&catid=25:domotique&Itemid=13

Ok.

Is there something special to consider regarding the association process, like cboulang tried to explain ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on September 18, 2012, 02:35:47 pm
Nothing special.
Pair the Blyss with an ID, group code and unit number. From now on you will be able to control this Blyss module using these codes.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on September 18, 2012, 03:49:45 pm
Bert,

so from your standpoint at the pairing does the plug (in my case) ever send a message or not ?
if not, it would mean that, where on x10 we were receiving Id from devices, we have to create and assign id/groupid to the device ?

if this is corect, does it mean that we need to manage (and store ) id, group id, etc within the plugin as it would failed if pairing details are given by the user, may reuse id+group id that have been used already and therefore break the whole stuff ?

Chris
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 18, 2012, 03:49:51 pm
Nothing special.
Pair the Blyss with an ID, group code and unit number. From now on you will be able to control this Blyss module using these codes.

No association process is required ?
And what about the group code and unit number of a device (socket for example) ? Is it something that is hardcoded ? Or can the user do the setup of these two data ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 18, 2012, 04:03:31 pm
Bert,

so from your standpoint at the pairing does the plug (in my case) ever send a message or not ?
if not, it would mean that, where on x10 we were receiving Id from devices, we have to create and assign id/groupid to the device ?

if this is corect, does it mean that we need to manage (and store ) id, group id, etc within the plugin as it would failed if pairing details are given by the user, may reuse id+group id that have been used already and therefore break the whole stuff ?

Chris

I think we have to store the remote id, the group code and the unit number to identify a Vera device, that is the same principle as for the other protocols already managed. And the association feature of the plugin will allow users to define a unique Vera device even if they have several remotes controlling the same physical device.

The only think I need to understand is how is done the association between a remote button and a socket device, and if the group code / unit number is defined by the remote or by the controlled unit ?
Is there a button on the socket device to validate the association for example ?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: DRuw on September 18, 2012, 04:20:38 pm
I think you have installed the wrong plugin.
What RFXCOM product did you buy ? USB or LAN version ?
It exists 2 Vera plugins, one for each product, one for the USB RFXtrx433 (my plugin) and one for the RFXLAN managed by evanes.
If you installed from the App Store, you installed the plugin for the RFXLAN as my plugin is not yet available on the App Store.
To upload the files, you can do it in several steps. Just restart after uploading all the files.

Damn... that was kinda stupid... thanks for the help!
RFXCOM is working fine now.. now I have other issues with my Duwi thingies but one thing at a time.
Thanks again for the support!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on September 18, 2012, 05:40:27 pm
Bert,

so from your standpoint at the pairing does the plug (in my case) ever send a message or not ?
if not, it would mean that, where on x10 we were receiving Id from devices, we have to create and assign id/groupid to the device ?

if this is corect, does it mean that we need to manage (and store ) id, group id, etc within the plugin as it would failed if pairing details are given by the user, may reuse id+group id that have been used already and therefore break the whole stuff ?

Chris

I think we have to store the remote id, the group code and the unit number to identify a Vera device, that is the same principle as for the other protocols already managed. And the association feature of the plugin will allow users to define a unique Vera device even if they have several remotes controlling the same physical device.
I agree, but if you refer to the x10 or the code I read, this is where I identify the catch: you are not only storing id sent by the device for later access, I understand there that you have to create the Id, group id, and iterate for each new device. if you have already done this for other device, that's great. if not it means a quite new laege piece of work to be done.

Quote
The only think I need to understand is how is done the association between a remote button and a socket device,
let's wait for Bert feedback.
Quote
and if the group code / unit number is defined by the remote or by the controlled unit ?
You mean a Blyss remote or the Blyss box in this case ? I guess they both can do it. That's what i understand from the blog of the arduino guys who hacked thr Blyss stuff. may be I was over assuming.
Quote
Is there a button on the socket device to validate the association for example ?
no, you press for several second the only button on the plug/socket, then the remote, there's association, and you're done. the only other thing you can do it remove the association with the remote by pressing the button for a long time.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 18, 2012, 05:55:44 pm
Ok, I just received a clear explanation from Bert.
That's very simple, nothing really special to manage compared to other protocols (Chacon for example).
I can add the support for Blyss easily, what will take most of time is adding new interfaces for creating Blyss devices.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: cboulang on September 18, 2012, 07:55:23 pm
Ok, I just received a clear explanation from Bert.
That's very simple, nothing really special to manage compared to other protocols (Chacon for example).
I can add the support for Blyss easily, what will take most of time is adding new interfaces for creating Blyss devices.

Ok great, I was actually reviewing Chacon's code and seeing most of what is requested is already there. Let me know if you want me to run tests.

Chris
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TommyE on September 19, 2012, 06:46:33 am
For JD101, you have to push the test button on the KD101 and a dev ice will be added in the Vera.
The device created will be a security remote device, not a smoke detector. This device has the ability to send a panic order to the smoke detectors.

I tried that already, to no avail.

My detector says KD-101LD, maybe it is not the same thing?

Also, which RFXCOM protocol do I have to enable for the KD-101

Thanks
Tommy

I don't know, that's not mentioned in the RFXtrx user manual. You have to ask RFXCOM support.

I was informed (PM) that the protocol to enable is X10.

Finally, after checking, RFXCOM informed me that KD101 does not require X10 protocol enabling. KD101 is always taken into account.

RFXCOM tested with model KD-101LA.

Ap15e reported to me a positive feedback using a KD101 clone: Flamingo FA20RF

So, for the KD-101LD, you might need to exchange directly with RFXCOM support.

Thanks, I will do that.

Will report back.

TommyE
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Johan on September 19, 2012, 06:48:57 am
Dear Lolodomo,

I uploaded your latest version of alpha 6 and I found out that it is not possible to create X10 devices. The housecode box is missing (see the attached file).

Regards Johan
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 19, 2012, 08:13:17 am
Dear Lolodomo,

I uploaded your latest version of alpha 6 and I found out that it is not possible to create X10 devices. The housecode box is missing (see the attached file).

Regards Johan

Yes, I know, this is due to a bug in firmware 1.5.408.
We are all waiting for a firmware fix.
You can return to firmware version 1.5.346 to avoid this problem.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 22, 2012, 05:11:34 am
While you do that, here's a link to an early draft of my next post on the 433mhz Protocols. http://nodecentral.wordpress.com/2012/09/16/138/ - please let me have any comments/suggestions you have.

This chapter is now written in the wiki page, I have mainly done a copy/paste from your page and the RFXCOM user manual.

If I finish one chapter per week, in few weeks/months, the wiki page should be finished ;D

http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 23, 2012, 11:55:21 am
;) - Happy the help you more lolodomo if you need it -  ;)

While I have you..

Do you know if LightwaveRf devices (light switches for example) report back to say the requested change was successfully or not? I've noticed a few missed Vera sent commands, so was curious?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 23, 2012, 01:50:16 pm
;) - Happy the help you more lolodomo if you need it -  ;)

Yes, you can, you were supposed to test your ATI Remote Wonder...

Quote
Do you know if LightwaveRf devices (light switches for example) report back to say the requested change was successfully or not? I've noticed a few missed Vera sent commands, so was curious?

Not at my knowledge.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 23, 2012, 02:48:51 pm
;) - Happy the help you more lolodomo if you need it -  ;)

Yes, you can, you were supposed to test your ATI Remote Wonder...

Sorry, I meant to get back to you on that,

Ok, here goes, upon pressing one of the buttons on my ATI Wonder Remote Control, it quickly created a new device in the UI called 'RFX Remote RC0/0F' which has 3 tabs.

At this point, I was really intrigued to see if this new device would either be a substitute for my remote? (so act as a virtual remote/keypad) or if it would just be tool to trigger Scenes ?

Tab 1 called 'Control' suggests I could send a command of my choice? Is that true? It provides me with a field to enter a single value and then press send - To test this, I need to install the ATI Remote software on an old XP PC (which i'll need to build/set up) as there does not seem to be any drivers for Win7

Tab 3 called 'Notification' looks to be a trigger for the remote to run scenes, is it?
but I will admit it was a little confusing as the drop down gave me only 1 option under Add Notification for: which was "When Scene Activated', which when selected allowed me to give the notification a name and enter a scene number. So I created a Notification adding a suitable Scene number, but unfortunately pressing  any button on the remote did not seem to activate it?

As the ATi Protocol is flagged by RFXCOM as one that can conflicts with the Oregon Scientific protocol, I'm keeping my eye on all my temperature sensors and energy monitor.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 23, 2012, 06:09:27 pm
I have 3 x Oregon Scientific Thermometers , each have 3 possible channels and each one is set to a unique channel.

My question is,  can I add more sensors , or will it start creating conflicts if the same channel is used?
i assume so, but would like to check as it would suggests I would need to look at the 10 channel sensors etc if I wanted to add more Oregon sensors?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 24, 2012, 03:44:38 am
At this point, I was really intrigued to see if this new device would either be a substitute for my remote? (so act as a virtual remote/keypad) or if it would just be tool to trigger Scenes ?

Both

Quote
Tab 1 called 'Control' suggests I could send a command of my choice? Is that true? It provides me with a field to enter a single value and then press send - To test this, I need to install the ATI Remote software on an old XP PC (which i'll need to build/set up) as there does not seem to be any drivers for Win7

It allows to send a command like your rempte is doing. You must use the decimal value of the buttons defined in the RFXtrx user manual. For example, button CHAN+ matches code 11.
You can even use the callback SendCommand (name to check) inside a scene.

I will add in the next release the ability to create manually a "ATI like" remote device. Then every user would be able to simulate this kind of remote through the RFXtrx even without owning such a remote.

Quote
Tab 3 called 'Notification' looks to be a trigger for the remote to run scenes, is it?
but I will admit it was a little confusing as the drop down gave me only 1 option under Add Notification for: which was "When Scene Activated', which when selected allowed me to give the notification a name and enter a scene number. So I created a Notification adding a suitable Scene number, but unfortunately pressing  any button on the remote did not seem to activate it?

As a scene trigger (or notification), you have to use the decimal value of the button as the scene number. Please check the RFXtrx user manual for list of codes.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 24, 2012, 03:47:40 am
My question is,  can I add more sensors , or will it start creating conflicts if the same channel is used?
i assume so, but would like to check as it would suggests I would need to look at the 10 channel sensors etc if I wanted to add more Oregon sensors?

Read the explanation on the RFXCOM web site.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on September 24, 2012, 03:15:45 pm
Ok, thanks for the push back, sorry I had missed that link.. http://www.rfxcom.com/oregon.htm

"The maximum number of sensors per category is limited by the number of channels available on the sensors in each category."

Cool, this suggests I can have 3 from TEMP1, 3 from TEMP2 etc. Which is a good thing to keep in mind..
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: bthovda on September 25, 2012, 06:00:47 am
New version alpha 6 of the plugin is now available.
Plugin files are available at http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha6#

What's new in version alpha 6:
- Plugin is up to date with RFXtrx firmware v49
- Child devices management revisited (fixed and enhanced)
- Support for X10 security remotes added
- Support for Meiantech/Atlantic security remotes added
- Support for KD101 smoke detector added
- Support for RUBiCSON temperature sensor added
- Support for Viking 02035, 02038 humidity sensors added
- Support for TFA 30.3133 temperature sensor added
- Support for Hasta blinds added
- Support for Philips SBC lighting added
- New devices created to match remote controls and give ability to trigger Vera scene from remote buttons, plus new buttons to send specific commands like group off, dim, bright, mood, ... etc
- LightwaveRF panel suppressed from the main plugin device; replaced by a new dedicated device
- Support for ATI and Medion remotes added
- Setup of received protocols updated
- "Logs" and "Notifications" panels added to barometer, rain, wind and UV devices
- Ability to adjust reported values for temperature, humidity, UV and barometric sensors using the variable "AdjustConst"
- Ability to repeat ON and OFF events for BinaryLight devices setting the variable "RepeatEvent" to 1
- Callback added to simulate receiving of message (for testing purposes)
- Support added for USB RFXtrx connected to a remote machine providing an IP access to a local serial port (using VSPE on Windows for example)

Hello

I just bought an RFXCOM, and tried your plugin.

I must say it is an impressive piece of work !!

It works great with some ESIC WT450 Temperature and Humidity sensors, bought at ClasOhlson i Norway, even shows battery status :) Cool.

I have a few KD101 smoke detectors around the house, seeing Alpha6 supports them I wonder do I need to do anything to make them appear in Vera?


Thanks
TommyE


Hey TommyE.

is the esic wt450 sensor this one: http://www.clasohlson.com/no/Ekstra-temperaturgiver/Pr361797000
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: TommyE on September 26, 2012, 02:52:01 am
New version alpha 6 of the plugin is now available.
Plugin files are available at http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha6#

What's new in version alpha 6:
- Plugin is up to date with RFXtrx firmware v49
- Child devices management revisited (fixed and enhanced)
- Support for X10 security remotes added
- Support for Meiantech/Atlantic security remotes added
- Support for KD101 smoke detector added
- Support for RUBiCSON temperature sensor added
- Support for Viking 02035, 02038 humidity sensors added
- Support for TFA 30.3133 temperature sensor added
- Support for Hasta blinds added
- Support for Philips SBC lighting added
- New devices created to match remote controls and give ability to trigger Vera scene from remote buttons, plus new buttons to send specific commands like group off, dim, bright, mood, ... etc
- LightwaveRF panel suppressed from the main plugin device; replaced by a new dedicated device
- Support for ATI and Medion remotes added
- Setup of received protocols updated
- "Logs" and "Notifications" panels added to barometer, rain, wind and UV devices
- Ability to adjust reported values for temperature, humidity, UV and barometric sensors using the variable "AdjustConst"
- Ability to repeat ON and OFF events for BinaryLight devices setting the variable "RepeatEvent" to 1
- Callback added to simulate receiving of message (for testing purposes)
- Support added for USB RFXtrx connected to a remote machine providing an IP access to a local serial port (using VSPE on Windows for example)

Hello

I just bought an RFXCOM, and tried your plugin.

I must say it is an impressive piece of work !!

It works great with some ESIC WT450 Temperature and Humidity sensors, bought at ClasOhlson i Norway, even shows battery status :) Cool.

I have a few KD101 smoke detectors around the house, seeing Alpha6 supports them I wonder do I need to do anything to make them appear in Vera?


Thanks
TommyE


Hey TommyE.

is the esic wt450 sensor this one: http://www.clasohlson.com/no/Ekstra-temperaturgiver/Pr361797000


Hello

Yes, thats the one :)

Tommy
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on September 27, 2012, 06:21:45 am
The WT450H sensors have a bad transmit range!
See http://www.domoticaforum.eu/viewtopic.php?f=27&t=7843&p=58076#p58076

IMO it is preferred to use Oregon sensors.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: audunv on September 28, 2012, 04:59:46 am
I have a couple of the WT450H sensor and can confirm that the transmit range is very bad.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: audunv on September 28, 2012, 05:11:29 am
First I want to say thanks for a very nice plugin.
I see that the rfxmeter is not yet supported in the plugin, and was wondering if you have any plans on implementing support for the rfxmeter?
I have a rfxmeter to measure power usage, and I'am looking forward for support for that.
If I can be of any help to get the rfxmeter implementet just let me know and I will help as best I can.

Audun
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 28, 2012, 08:21:06 am
First I want to say thanks for a very nice plugin.
I see that the rfxmeter is not yet supported in the plugin, and was wondering if you have any plans on implementing support for the rfxmeter?
I have a rfxmeter to measure power usage, and I'am looking forward for support for that.
If I can be of any help to get the rfxmeter implementet just let me know and I will help as best I can.

Honestly, it is not in my current TODO list.
My plans are to finish quickly few little things (Blyss support in particular) and then release a final v1.0.
Then I will correct reported bugs and follow new versions of RFXtrx firmware, but I will probably spend most of my free time to something else.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Catr on September 29, 2012, 01:55:10 pm
@lolodomo
When I chose the menu Device creation  from  RFXtrx controller device  the house code  À to P must be filled in. But there is no box to filll in. For Unit code there is  a box.
Add Impulse Switch  is not creating a device!
How to get an IMPULSE switch working?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 30, 2012, 05:40:36 am
@lolodomo
When I chose the menu Device creation  from  RFXtrx controller device  the house code  À to P must be filled in. But there is no box to filll in. For Unit code there is  a box.
Add Impulse Switch  is not creating a device!
How to get an IMPULSE switch working?

I have added a chapter "Known problems" in the wiki page: http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#
Here is the content of this chapter:

Quote
A bug in Vera firmware 1.5.408 has for consequence that fields in the Device creation tab of the RFXtrx Controller device are not what they should be; in particular the input field for the house code is not displayed, replaced by a label field from another tab...

This bug is not included in Vera firmware 1.5.346. So you have the choice between returning back to firmware version 1.5.346 or waiting for a new Micasaverde firmware (pray so that Micasaverde takes this problem into consideration).

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on September 30, 2012, 02:50:45 pm
@lolodomo
When I chose the menu Device creation  from  RFXtrx controller device  the house code  À to P must be filled in. But there is no box to filll in. For Unit code there is  a box.
Add Impulse Switch  is not creating a device!
How to get an IMPULSE switch working?

I have added a chapter "Known problems" in the wiki page: http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#
Here is the content of this chapter:

Quote
A bug in Vera firmware 1.5.408 has for consequence that fields in the Device creation tab of the RFXtrx Controller device are not what they should be; in particular the input field for the house code is not displayed, replaced by a label field from another tab...

This bug is not included in Vera firmware 1.5.346. So you have the choice between returning back to firmware version 1.5.346 or waiting for a new Micasaverde firmware (pray so that Micasaverde takes this problem into consideration).

One solution to avoid the firmware bug would be to put everything in one unique tab (settings), that means moving the content of the Device creation tab in the Settings tab.
Will think about that for the next version.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: mho on October 01, 2012, 02:41:23 pm
Can somebody please explain how to set AC/KAKU as dimmer (set level). My KAKU dimmer is recognised as ON/OFF device. Thanks in advance.

I have a similar problem: there is a dimmer instance, but it does not work, so I can only turn the light on or off.
Is there someone who has it working whit KUKA (ACM-300)?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Catr on October 01, 2012, 02:59:28 pm
@lolodomo,
Flashed back the 346 software to the vera, now 8 switches are working. :)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 02, 2012, 04:25:40 am
Can somebody please explain how to set AC/KAKU as dimmer (set level). My KAKU dimmer is recognised as ON/OFF device. Thanks in advance.

I have a similar problem: there is a dimmer instance, but it does not work, so I can only turn the light on or off.
Is there someone who has it working whit KUKA (ACM-300)?

Try with RFXmngr to check if you can dim your light.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: mho on October 02, 2012, 02:46:32 pm
Can somebody please explain how to set AC/KAKU as dimmer (set level). My KAKU dimmer is recognised as ON/OFF device. Thanks in advance.

I have a similar problem: there is a dimmer instance, but it does not work, so I can only turn the light on or off.
Is there someone who has it working whit KUKA (ACM-300)?

Try with RFXmngr to check if you can dim your light.

In RFXmngr it's working fine: I can dim the lights.

In Vera Lite: when I press Group Off and Group on I see the tranceivers leds blink. When I press dimm or bright, the tranceiver does not respond.
In the controls I changed D_X10ChaconRemote1.xml into D_DimmableLight1.xml and now I can dimm the lights. Only the status in the gui is not updated when the switch on the wall is used...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: kad77 on October 03, 2012, 07:23:47 am
Hello,

Can somebody help me to get temperature from RFXSensor -> RFXtrx USB into Vera?
It works fine with RFXMngr.exe so I guess I could add a device manually in Vera. Right?
Thnks
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 03, 2012, 07:28:09 am
Can somebody please explain how to set AC/KAKU as dimmer (set level). My KAKU dimmer is recognised as ON/OFF device. Thanks in advance.

I have a similar problem: there is a dimmer instance, but it does not work, so I can only turn the light on or off.
Is there someone who has it working whit KUKA (ACM-300)?

Try with RFXmngr to check if you can dim your light.

In RFXmngr it's working fine: I can dim the lights.

In Vera Lite: when I press Group Off and Group on I see the tranceivers leds blink. When I press dimm or bright, the tranceiver does not respond.
In the controls I changed D_X10ChaconRemote1.xml into D_DimmableLight1.xml and now I can dimm the lights. Only the status in the gui is not updated when the switch on the wall is used...

You must do it through the plugin UI ! You go in the device creation tab, you enter your device information and then you push the button "AC dimmer". It is the way to change from binary light type to dimmable light type.
Other solution is to send a dim command through your remote. In this case, the plugin will automatically change the type of the device.
It is definitively not the remote device that must be changed !
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 03, 2012, 07:30:52 am
Hello,

Can somebody help me to get temperature from RFXSensor -> RFXtrx USB into Vera?
It works fine with RFXMngr.exe so I guess I could add a device manually in Vera. Right?
Thnks

No. You must implement something new in the plugin to add support for RFXSensor.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: kad77 on October 03, 2012, 07:33:17 am
Ok. Is it planned in the future?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 03, 2012, 07:59:05 am
Ok. Is it planned in the future?

Probably not by myself. But everybody can contribute, I made the plugin as modular as possible.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 03, 2012, 08:03:35 am
@lolodomo,
Flashed back the 346 software to the vera, now 8 switches are working. :)

I am waiting for the next public firmware, hoping the bug will be fixed.
If not, I will put everything in a unique big tab !
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: kad77 on October 03, 2012, 08:10:22 am
Do you mean I should be able t modify it myself?
Where can I find info how to do it?

Thanks for your help
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: mho on October 04, 2012, 02:26:46 am
Can somebody please explain how to set AC/KAKU as dimmer (set level). My KAKU dimmer is recognised as ON/OFF device. Thanks in advance.

I have a similar problem: there is a dimmer instance, but it does not work, so I can only turn the light on or off.
Is there someone who has it working whit KUKA (ACM-300)?
Try with RFXmngr to check if you can dim your light.

In RFXmngr it's working fine: I can dim the lights.

In Vera Lite: when I press Group Off and Group on I see the tranceivers leds blink. When I press dimm or bright, the tranceiver does not respond.
In the controls I changed D_X10ChaconRemote1.xml into D_DimmableLight1.xml and now I can dimm the lights. Only the status in the gui is not updated when the switch on the wall is used...

You must do it through the plugin UI ! You go in the device creation tab, you enter your device information and then you push the button "AC dimmer". It is the way to change from binary light type to dimmable light type.
Other solution is to send a dim command through your remote. In this case, the plugin will automatically change the type of the device.
It is definitively not the remote device that must be changed !

Unfortunately, still no luck. I tried to add the ac dimmer in the device creation tab and to send the dim command through the remote. Both with no result.
When Vera Lite detects a new dimmer device, 2 RFX devices pop up:
1.   RFX Light, I can turn the light on or off. Works fine.
2.   RFX remote, 4 buttons called dim-bright-on-off. When I push on / off, the leds of the transceiver blink. When I push dim or bright, the leds do not blink.

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 04, 2012, 07:01:23 am
Do you mean I should be able t modify it myself?

If you already have minimum knowledge in Vera plugin development, it should be doable.

Quote
Where can I find info how to do it?

Thanks for your help

Just open the L_RFXtrx.lua file.
Of course, you will have to ask RFXCOM for the SDK, a PDF document describing what are the messages exchanged. The message for the RFXSensor is described.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 04, 2012, 07:18:39 am
Unfortunately, still no luck. I tried to add the ac dimmer in the device creation tab and to send the dim command through the remote. Both with no result.
When Vera Lite detects a new dimmer device, 2 RFX devices pop up:
1.   RFX Light, I can turn the light on or off. Works fine.
2.   RFX remote, 4 buttons called dim-bright-on-off. When I push on / off, the leds of the transceiver blink. When I push dim or bright, the leds do not blink.

On the RFX remote device, the buttons are named "group ON" and "group OFF". They allow to simulate the group buttons of your remote (if they exist). Of course, you must have previously added devices in your group. Please check the manual of your remote to understand how to do it. Maybe Kaku does not provide the group feature ?

Dim and Bright are for X10 lighting only, so it is normal that nothing happens for AC.

Regarding the dimming, did you succeed in using the device creation tab to change your BinaryLight device into a DimmableLight device ? In the advanced tab of this device, can you tell me what is the value of the "altid" variable ? Then, please check the logs, you should find in particular the message sent when you try to dim the light from this device. Please report the RFXtrx logs at this instant. You can then compare this message with the message produced by RFXmngr.

PS: you can use this command to filter RFXtrx logs: tail -f /var/log/cmh/Lua.....log | grep RFXtrx
Sorry, I don't remember the exact name of the log file.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Peter on October 04, 2012, 10:32:46 am
I have tried uninstalling alpha 5 en installing alpha 6 by following manual:

http://nodecentral.wordpress.com/2012/08/26/working-vera-on-a-different-frequency-rfxcoms-rfxrtx433/ (http://nodecentral.wordpress.com/2012/08/26/working-vera-on-a-different-frequency-rfxcoms-rfxrtx433/)

but I get always alpha 5 back. What i'am doing wrong?   

I found the problem, copy L_RFXtrx.lua with wincp and the problem is solved

Peter
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 04, 2012, 02:55:33 pm
I have tried uninstalling alpha 5 en installing alpha 6 by following manual:

http://nodecentral.wordpress.com/2012/08/26/working-vera-on-a-different-frequency-rfxcoms-rfxrtx433/ (http://nodecentral.wordpress.com/2012/08/26/working-vera-on-a-different-frequency-rfxcoms-rfxrtx433/)

but I get always alpha 5 back. What i'am doing wrong?   

I found the problem, copy L_RFXtrx.lua with wincp and the problem is solved

Peter

To upgrade, you have:
1) download the ZIP file corresponding to the new alpha 6 version: http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha6#
2) upload individually each file contained in the ZIP file
3) reload
That's all !
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: mho on October 04, 2012, 03:55:04 pm
Unfortunately, still no luck. I tried to add the ac dimmer in the device creation tab and to send the dim command through the remote. Both with no result.
When Vera Lite detects a new dimmer device, 2 RFX devices pop up:
1.   RFX Light, I can turn the light on or off. Works fine.
2.   RFX remote, 4 buttons called dim-bright-on-off. When I push on / off, the leds of the transceiver blink. When I push dim or bright, the leds do not blink.

On the RFX remote device, the buttons are named "group ON" and "group OFF". They allow to simulate the group buttons of your remote (if they exist). Of course, you must have previously added devices in your group. Please check the manual of your remote to understand how to do it. Maybe Kaku does not provide the group feature ?

Dim and Bright are for X10 lighting only, so it is normal that nothing happens for AC.

Regarding the dimming, did you succeed in using the device creation tab to change your BinaryLight device into a DimmableLight device ? In the advanced tab of this device, can you tell me what is the value of the "altid" variable ? Then, please check the logs, you should find in particular the message sent when you try to dim the light from this device. Please report the RFXtrx logs at this instant. You can then compare this message with the message produced by RFXmngr.

PS: you can use this command to filter RFXtrx logs: tail -f /var/log/cmh/Lua.....log | grep RFXtrx
Sorry, I don't remember the exact name of the log file.

I did not did succeed in using the device creation tab to change your BinaryLight device into a DimmableLight device.
These are my settings of the RFXtrx controller device:
Settings tab:
AC and X10 are enabled, the rest is disabled.
On the device creation tab I enter 11 in Unit code (the altid of the device I want to dim is RC/L2.0/03AB872/11 and in RFXmngr that's working). After that I press the button: Add AC dimmer. Nothing happens, I am not even prompted to save.
Advanced tab:
Controlled by: No Parent
Altid is empty. I also tried to fill this with RC/L2.0/03AB872/11 (and RC/L2.0/03AB872) and to add the AC dimmer after that, but no result.
I saved the log file onto USB, but I couldn’t read it yet on my Windows machine.
I’ll add log info asap.
Thanks for your help!!!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 04, 2012, 04:43:31 pm
I did not did succeed in using the device creation tab to change your BinaryLight device into a DimmableLight device.
These are my settings of the RFXtrx controller device:
Settings tab:
AC and X10 are enabled, the rest is disabled.
On the device creation tab I enter 11 in Unit code (the altid of the device I want to dim is RC/L2.0/03AB872/11 and in RFXmngr that's working). After that I press the button: Add AC dimmer. Nothing happens, I am not even prompted to save.

You just forgot to enter the remote id.
Enter 03AB872 in the remote id field, enter 11 in the unit code field; push the button "Add AC dimmer".
If you have taken a look in the logs, you would have discovered a message telling you that your remote id is not valid. Unfortunately, there is no way with the flash interface to popup a message window. So the user is not informed about errors ! Not very cool, I know.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: mho on October 05, 2012, 02:29:58 pm
I did not did succeed in using the device creation tab to change your BinaryLight device into a DimmableLight device.
These are my settings of the RFXtrx controller device:
Settings tab:
AC and X10 are enabled, the rest is disabled.
On the device creation tab I enter 11 in Unit code (the altid of the device I want to dim is RC/L2.0/03AB872/11 and in RFXmngr that's working). After that I press the button: Add AC dimmer. Nothing happens, I am not even prompted to save.

You just forgot to enter the remote id.
Enter 03AB872 in the remote id field, enter 11 in the unit code field; push the button "Add AC dimmer".
If you have taken a look in the logs, you would have discovered a message telling you that your remote id is not valid. Unfortunately, there is no way with the flash interface to popup a message window. So the user is not informed about errors ! Not very cool, I know.

That's it! The devil is in the details...
Thanks very much, it works perfect now!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: strangely on October 06, 2012, 03:06:59 am
Unfortunately, there is no way with the flash interface to popup a message window. So the user is not informed about errors !
Are you sure about that? There are other plugins that do pop up messages there!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 06, 2012, 05:13:12 am
Unfortunately, there is no way with the flash interface to popup a message window. So the user is not informed about errors !
Are you sure about that? There are other plugins that do pop up messages there!

Nothing mentioned here: http://wiki.micasaverde.com/index.php/Luup_Lua_extensions
And I believe I have already asked the question on the forum and got a negative answer.

Which plugins are doing that ? I could check how they do.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: oTi@ on October 06, 2012, 07:42:34 am
Alternatively, you could write messages to the status window (http://wiki.micasaverde.com/index.php/Luup_Lua_extensions#function:_task)?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: strangely on October 06, 2012, 01:20:55 pm
@oTi, that's exactly what I was talking about.

@Lolodomo, if you take a look at many of the plugins by @guessed, he has various error messages that use this.

(DSC, SQblaster, Weather Underground Plugin etc)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 07, 2012, 05:10:36 am
You mean the little blue zone at top and middle of the dashboard ?
I thought it was mainly for the start process.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: strangely on October 07, 2012, 11:25:29 am
Yep
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 07, 2012, 05:43:24 pm
Ok, I can add messages here, no problem.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: ajackson81 on October 12, 2012, 06:10:59 pm
Hoping someone here can help...

Setting up my vera3 with rfxcom transceiver and having a couple of issues.

I have tried th following:

I upload all the alpha 6 files (from code.mios.com/trac/mios_rfxtrx/browser/tags/alpha6#) using the upload files section on ui5 (tried through google chrome and ie)

Restart Luup

Create device and use rfxtrx.xml as the Upnp Device Filename.

Restart luup

But when I go into serial port configuration I try and select used by device as "rfxtrx controller device" but its not in the list, only new item is [].

Also when I go to the devices tab he controller has been added as a generic device..

Software version is 1.5.408

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 13, 2012, 04:43:51 am
I don't know, maybe download the ZIP archive from code.mios.com rather than file per file...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: thbodart on October 15, 2012, 12:15:51 pm
Yes download the zip archive, have the same problem and it solved
Thierry
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: nlrb on October 15, 2012, 04:26:11 pm
Hi lolodomo,

I've added initial support for Mertik (G6R-H4T1) / Heaters. Still working on finalizing the code though. Let me know if/how you want to merge the code changes.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 15, 2012, 04:49:08 pm
Hi lolodomo,

I've added initial support for Mertik (G6R-H4T1) / Heaters. Still working on finalizing the code though. Let me know if/how you want to merge the code changes.

 8)
Join the updated files here and I will merge them in code.mios.com.
I hope you start from the files currently in the trunk...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Intrepid on October 15, 2012, 06:35:45 pm
I'm about ready to order the rfxcom.  I looked through the wiki post of compatible devices and saw 'us x10 iighting' and 'us x10 security'.

'X10 security' means the ds10a and similar security system sensors, correct?

'x10 lighting' means all other RF devices like palmpad remotes, keychain remotes, etc?

Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 16, 2012, 04:21:24 am
I'm about ready to order the rfxcom.  I looked through the wiki post of compatible devices and saw 'us x10 iighting' and 'us x10 security'.

'X10 security' means the ds10a and similar security system sensors, correct?

'x10 lighting' means all other RF devices like palmpad remotes, keychain remotes, etc?

Be carefull, you will need the RFXtrx310/315 and not the RFXtrx433.

X10 security is relative to alarm, smoke detectors, ...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Intrepid on October 16, 2012, 05:13:18 am
I'm about ready to order the rfxcom.  I looked through the wiki post of compatible devices and saw 'us x10 iighting' and 'us x10 security'.

'X10 security' means the ds10a and similar security system sensors, correct?

'x10 lighting' means all other RF devices like palmpad remotes, keychain remotes, etc?

Be carefull, you will need the RFXtrx310/315 and not the RFXtrx433.

X10 security is relative to alarm, smoke detectors, ...

thanks for that.  US x10 is on 310/315mhz, and most of the other cool stuff (oregon scientific, etc) is 433?  there's not one transceiver for both?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 16, 2012, 01:30:05 pm
I'm about ready to order the rfxcom.  I looked through the wiki post of compatible devices and saw 'us x10 iighting' and 'us x10 security'.

'X10 security' means the ds10a and similar security system sensors, correct?

'x10 lighting' means all other RF devices like palmpad remotes, keychain remotes, etc?

Be carefull, you will need the RFXtrx310/315 and not the RFXtrx433.

X10 security is relative to alarm, smoke detectors, ...

thanks for that.  US x10 is on 310/315mhz, and most of the other cool stuff (oregon scientific, etc) is 433?  there's not one transceiver for both?

Maybe take a look to the RFXLAN.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: nlrb on October 16, 2012, 03:16:47 pm
Hi lolodomo,

I've branched of off @38 (Sep-30). The attached code is not final, will do some more updates to it. But you can merge this and review the code. I've tried to stick to your coding style as much as possible. CMD_HEATER_UP and CMD_HEATER_DOWN are not yet implemented (will need to figure out what works best in the UI for this, might use the temp. setting). switchPower is also not implemented yet.

Note that I've added ToggleState support, but only for limited nr. of devices (will need more work). I also had to change the string.find in actOnMessage and findChild to not use regex (should also be a bit quicker).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: nanotube on October 21, 2012, 01:47:58 pm
Does anyone know why when I switch out batteries of my Oregon Scientific temp sensors they show up in Vera as bunch of completely new device IDs? It's kind of annoying having to go and change sensor device# in scenes and other codes every time it happens. Is this how OS supposed to work? I have three OS sensors on each of the 3 OS channels. I am using RFXrec433. Thanks.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 21, 2012, 06:39:23 pm
Does anyone know why when I switch out batteries of my Oregon Scientific temp sensors they show up in Vera as bunch of completely new device IDs? It's kind of annoying having to go and change sensor device# in scenes and other codes every time it happens. Is this how OS supposed to work? I have three OS sensors on each of the 3 OS channels. I am using RFXrec433. Thanks.
yes, Oregon sensors change their id when you change the battery.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on October 21, 2012, 06:53:38 pm
yes, Oregon sensors change their id when you change the battery.

Hi Lolodomo 

As I have 4 x OS temp sensors running and all are being tracked via DataMine,  I'm now curious if there could be a way your plugin might be able to address this? E.g a potential idea could be to..

* Have a new option added, which allows you to flag a pending battery change, which then takes the resulting 'new' Oregon Scientific  ID and auto update/replaces the old/original one ? (Removing the risk of redundant devices)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: nanotube on October 21, 2012, 07:53:58 pm
yes, Oregon sensors change their id when you change the battery.
Thanks. I thought of a low-tech solution to cheat the system: what if I power off (unplug) veralite altogether, quickly change the battery in OS sensor, then re-power up the veralite with RFXrec433? This way the RFXcom device never knew a battery is changed and perhaps will keep my old device ID#?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on October 22, 2012, 02:35:13 am
There is no simple solution to detect the association between the old and the new ID.

If you want to keep the old sensors and delete the new sensors (for example because they are used in scenes), you can use the association mechanism I defined in the plugin using the variable Association.

The only thing I could add is an optional and automatic suppress for example one time per day all weather sensors that were not updated since few hours.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: nlrb on October 22, 2012, 08:35:18 am
@lolodomo: maybe you can add an option to ignore id1 for the OS sensors. id2 contains the channel number, id1 is a random number per reset. Normally, you will only have one (e.g. temp) sensor per channel. id1 is only needed if e.g. your neighbors also have an OS (temp) sensor on the same channel.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: eddiegonzales on October 31, 2012, 09:01:34 am

Hi

Quote
Alpha 6 - Support for TFA 30.3133 temperature sensor added

Anybody knows, how many channels the 30.3133 has?

Cheers
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on October 31, 2012, 02:56:51 pm
The TFA 30.3133 has 3 channels
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: eddiegonzales on October 31, 2012, 02:57:41 pm
Thanks!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 01, 2012, 10:59:44 am
You mean the little blue zone at top and middle of the dashboard ?
I thought it was mainly for the start process.

That's done, some of the plugin's errors are now shown to the user in that screen zone.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on November 01, 2012, 12:48:32 pm
There is no simple solution to detect the association between the old and the new ID.

If you want to keep the old sensors and delete the new sensors (for example because they are used in scenes), you can use the association mechanism I defined in the plugin using the variable Association.

The only thing I could add is an optional and automatic suppress for example one time per day all weather sensors that were not updated since few hours.

Hi Lolodomo, have you had any more thoughts on this, I have a unit that I think might need a change soon, so I was curious what the process could be?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 02, 2012, 02:21:55 pm
Hi lolodomo,

I've branched of off @38 (Sep-30). The attached code is not final, will do some more updates to it. But you can merge this and review the code. I've tried to stick to your coding style as much as possible. CMD_HEATER_UP and CMD_HEATER_DOWN are not yet implemented (will need to figure out what works best in the UI for this, might use the temp. setting). switchPower is also not implemented yet.

Note that I've added ToggleState support, but only for limited nr. of devices (will need more work). I also had to change the string.find in actOnMessage and findChild to not use regex (should also be a bit quicker).

nirb, I pushed your contrib but with several changes. Can you check please if it is still working ?

Edit: I just fixed a bug I introduced.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 02, 2012, 02:55:21 pm
There is no simple solution to detect the association between the old and the new ID.

If you want to keep the old sensors and delete the new sensors (for example because they are used in scenes), you can use the association mechanism I defined in the plugin using the variable Association.

The only thing I could add is an optional and automatic suppress for example one time per day all weather sensors that were not updated since few hours.

Hi Lolodomo, have you had any more thoughts on this, I have a unit that I think might need a change soon, so I was curious what the process could be?

No additional thought.
If your problem is that your old devices are referenced in scenes and you don't want to change your scenes, add the Association variable on the old temperature and humidity devices and reference the altid of the new devices. Then suppress the new devices.

new service: upnp-rfxcom-com:serviceId:rfxtrx1
new variable: Association
New Value : T2/29953  (in case the altid of the new temperature device is TS/T2/29953)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: nlrb on November 02, 2012, 03:57:18 pm
nirb, I pushed your contrib but with several changes. Can you check please if it is still working ?

Edit: I just fixed a bug I introduced.
Hi lolodomo,

Thanks for the merge. Unfortunately it doesn't completely work as expected. Looks like the RunUp and RunDown are not used anymore. So the device will always be switched off completely - which is not really desired behavior. Normally you switch it on once, and then only use the RunUp and RunDown. Only e.g. in summer you switch it off completely.

Hence it was implemented that the first 'Off' only does a RunDown and the second 'Off' will send and Off command.

To go back to the original behavior, I've uncommented line 1546 and changed line 1561 to "if (currentState == "Off")".
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 02, 2012, 07:26:47 pm
nirb, I pushed your contrib but with several changes. Can you check please if it is still working ?

Edit: I just fixed a bug I introduced.
Hi lolodomo,

Thanks for the merge. Unfortunately it doesn't completely work as expected. Looks like the RunUp and RunDown are not used anymore. So the device will always be switched off completely - which is not really desired behavior. Normally you switch it on once, and then only use the RunUp and RunDown. Only e.g. in summer you switch it off completely.

Hence it was implemented that the first 'Off' only does a RunDown and the second 'Off' will send and Off command.

To go back to the original behavior, I've uncommented line 1546 and changed line 1561 to "if (currentState == "Off")".

That's fixed.

Do you plan to use the + and - buttons of the device ? They are here to define the wished temperature ? If not used in our case, we could at least avoid the "No implementation" error message, no ? (probably the SetCurrentSetpoint callback)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: kevinvanlooy on November 03, 2012, 07:10:25 am
As the add device tab is still messed up, I want to go back to a working firmware,
but I can not find the url for the "old" firmware.

What are the consequences of reverting back the firmware? loss of devices..?

regards
kef
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: nlrb on November 03, 2012, 07:58:11 am
That's fixed.

Do you plan to use the + and - buttons of the device ? They are here to define the wished temperature ? If not used in our case, we could at least avoid the "No implementation" error message, no ? (probably the SetCurrentSetpoint callback)
Yes, we should indeed implement SetCurrentSetpoint. Not sure what to do with the desired temperature though. But the Up and Down command should be sent when pressing '+' / '-'.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 03, 2012, 08:15:54 am
That's fixed.

Do you plan to use the + and - buttons of the device ? They are here to define the wished temperature ? If not used in our case, we could at least avoid the "No implementation" error message, no ? (probably the SetCurrentSetpoint callback)
Yes, we should indeed implement SetCurrentSetpoint. Not sure what to do with the desired temperature though. But the Up and Down command should be sent when pressing '+' / '-'.

That makes sense.
There is no way to get the value of the temperature set in the thermostat ? Nothing I see in the RFX protocol...
A UP commmand increases the value of how much degrees ? 1°C ?
I let you propose the new changes ? It is just the function SetCurrentSetpoint to add...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: iscient on November 09, 2012, 10:25:26 am
Hi,
Does anyone know if this receiver and plugin will work with programmable RF remotes such as the Acoustic Research Xsight Touch (also known as One For All URC8603 Xsight Touch).

I would want to configure it so I can press a button on the remote to trigger a scene.

Thanks, Richard
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on November 09, 2012, 06:12:24 pm
Hi,
Does anyone know if this receiver and plugin will work with programmable RF remotes such as the Acoustic Research Xsight Touch (also known as One For All URC8603 Xsight Touch).

I would want to configure it so I can press a button on the remote to trigger a scene.

Thanks, Richard

I don't think so, the starting point for any items is that it runs on the 433mhz range but the best place to go is to the RFXCOM website itself and look at the list of supported products in the manual, keep in mind this plugin can only ever process the items/devices that are support by the Transcievers firmware.

Hope that helps.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 10, 2012, 09:53:01 am
New version 0.7 of the plugin has just been released.

To download the plugin files, use the Zip archive link at the bottom of this page (http://code.mios.com/trac/mios_rfxtrx/browser/tags/alpha7#).
Installation & Setup (http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#InstallationSetup)
Compatible products and limitations (http://code.mios.com/trac/mios_rfxtrx/wiki/WikiStart#Compatibleproductsandlimitations)

What's new in version alpha 7:
- Support for Blyss added
- Support for OWL CM180 added
- Manual creation of Hasta (old models) added
- Support for A-OK motors added
- Support for weighting scale (BWR101/102, GR101) added (Ap15e contrib)
- Support for Mertik-Maxitrol thermostats added (nirb contrib)
- New callback SendMessage added
- Last received message logged + stored in the variable "LastReceivedMsg" + displayed at the bottom of the Settings tab
- New variable "AdjustMultipler" added to let the user apply a multiplier coefficient on weather data
- Variable "Assocation" renamed "Association"
- Error messages shown to the user in the status zone of the dashboard (blue zone at the top middle of the screen)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: Aaron on November 13, 2012, 02:05:54 pm
Will this plugin work with the X10 CM19a (USB RF receiver)?

Is there any plan to make this plugin available on the MCV Apps site - so we can install from the APPS tab?

thx
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 13, 2012, 02:07:41 pm
Is there any plan to make this plugin available on the MCV Apps site - so we can install from the APPS tab?

Yes, there is a plan for that :)
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: parkerc on November 13, 2012, 02:40:42 pm
Hi Lolodomo

Now you have an child board dedicated to  the RFXtrx plugin, what do you think about breaking up the topics into focussed threads  - 40+ pages and growing might seem overwhelming to some of the newbies

Maybe something like  the following.

Welcome - Please Read First
   - Introduction and set the scene

Version 0.6 Released
   - show what you've added
   - host any discussions around the new release and new features
   - Known Issues

Version 0.7 Released
   - show what you've added
   - host any discussions around the new release and new features
   - Known Issues

Supported Products
   - Links to the wiki page and RFXCOM Site
   - Host any discussions around the supported products/protocols

New Feature Requests
   - A place where people can submit ideas for your feedback/consideration

The 0.6 release thread was  just to show how it can grow over time

These can be made 'stickies' so they always sit at the top?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: DRuw on November 17, 2012, 06:57:42 am
Great work guys!
Ive got a question: Ive got a fireplave with a Mertik Maxitrol G6R-H4T1 remote which I cannot get to work with 0.6 but I think its included in 0.7 right?
Is it required to remove an old file before uploading the 0.7 version (if yes: HOW??)
Regards!

Edit: I uploaded the files and the widget says its rev 7 but for some reason, I cant get the remote to work... no widgets are created when I press the remote and in the controller widget, mertik is activated (its the only one i use except KaKu).
Anyone have an idea how I can get it to work?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 17, 2012, 07:58:45 am
Great work guys!
Ive got a question: Ive got a fireplave with a Mertik Maxitrol G6R-H4T1 remote which I cannot get to work with 0.6 but I think its included in 0.7 right?

Yes

Quote
Is it required to remove an old file before uploading the 0.7 version (if yes: HOW??)

No

Quote
Edit: I uploaded the files and the widget says its rev 7 but for some reason, I cant get the remote to work... no widgets are created when I press the remote and in the controller widget, mertik is activated (its the only one i use except KaKu).
Anyone have an idea how I can get it to work?

Can you check at the bottom of the Settings tab (Last received message) if a new message is received when you push a button of your remote.
Please do a copy/paste of this message here. You should get a message starting by 08 42 00 ...
If no message is received, please try to reduce the distance between your remote and the RFXtrx to check if it changes something.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: DRuw on November 17, 2012, 08:12:28 am
Here's what I did,
I walked to the RFXCOM and held my remote 10 cm away from it when I pushed the two buttons that start my fireplace.
code: Last received message:04 02 01 07 00
When I press the off button: Last received message:04 02 01 07 00
So apparently the RFXCOM doesnt pick it up for some reason (my fireplace lit up and shutted down since he did receive the remote control signals...)
ps: ive got firmware version v49 of the rfxcom controller according to the settings tab... is that correct?
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: b_weijenberg on November 17, 2012, 08:37:12 am
The latest RFXtrx433 firmware is version 57.
Version 52 has an improvement for the Mertik Maxitrol G6R-H4T1

After the firmware update check with RFXmngr if the Mertik remote is received.

Disable the oregon protocol because this protocol will stop receiving of Mertik. See chapter 2.3 in the RFXtrx User Guide
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: DRuw on November 17, 2012, 09:59:40 am
TNX! Solved!
I had to remove the RFXcom controller widget and add it again (it kept v49) but now its v57 and it works with the fireplace (just in time for chrismas!)
I think its best when I give commands to the fireplace in a scene, Ill repeat the command after 2 and 4 seconds, just to be sure (its still not zwave:() but this is really nice!
Now to add the KaKu units again because I lost all things related to the RFXCOM...
Tnx again, you guys made my weekend!

Edit: got the Kaku also reinstalled (forgot I turned it off in the config..) The shutting off of the fireplace works every time but the surning on is a bit buggy... I need to hit the button to turn off first (sometimes several times) untill I hear a *beep* and then turn it on and then it works.
Can't seem to get the logic here since I've tried to put it in a scene where I turn it off first 2 times with 2 secs interval and then after 10 secs turn it on but doesn't seem to work either.. Is this something purely because its RF and do you guys have the same thing or am I overlooking something?
Btw: the *beep* is the end of the gas valve I think but it looks like when I give the "turn on" command without having heard the *beep*it opens the gas valve but doesn't ignite the thing (first step BEFORE opening the gas valve further than pilot mode) which seems a bit unsafe to say the least...
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 17, 2012, 10:45:16 am
Here's what I did,
I walked to the RFXCOM and held my remote 10 cm away from it when I pushed the two buttons that start my fireplace.
code: Last received message:04 02 01 07 00
When I press the off button: Last received message:04 02 01 07 00
So apparently the RFXCOM doesnt pick it up for some reason (my fireplace lit up and shutted down since he did receive the remote control signals...)
ps: ive got firmware version v49 of the rfxcom controller according to the settings tab... is that correct?

Yes, please update the firmware, if you check the history of versions for the RFXtrx firmware, you will see changes relative to the Digimax after v49.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: nlrb on November 18, 2012, 08:25:11 am
...The shutting off of the fireplace works every time but the surning on is a bit buggy... I need to hit the button to turn off first (sometimes several times) untill I hear a *beep* and then turn it on and then it works.
Can't seem to get the logic here since I've tried to put it in a scene where I turn it off first 2 times with 2 secs interval and then after 10 secs turn it on but doesn't seem to work either.. Is this something purely because its RF and do you guys have the same thing or am I overlooking something?
Btw: the *beep* is the end of the gas valve I think but it looks like when I give the "turn on" command without having heard the *beep*it opens the gas valve but doesn't ignite the thing (first step BEFORE opening the gas valve further than pilot mode) which seems a bit unsafe to say the least...
The way it has been implemented is as follows.
Once the fireplace is off, you won't be able to turn it on without waiting 5 minutes first (see the manual).
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: DRuw on November 18, 2012, 08:35:34 am
Once the fireplace is off, you won't be able to turn it on without waiting 5 minutes first (see the manual).
Wow, I think thats it... I dont have the manual.. it was in my house when I bought it and never looked for it actually.
Thanks for the info!
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: wrc55 on November 20, 2012, 04:37:04 am
Hi

This is my first post, so sorry if it's a stupid one

I have added the RFXtrx it sees devices such as Owl energy monitor and next doors rain sensor :-)

I am trying to add a LightwaveRF dimmer light switch (I disabled all functions apart from AD and Oregon and upgraded to v57 firmware on a PC) - want to test it as these look so much better than any z-wave switches I can find (and are cheaper)

But It doesn't see it

I saw that if no remote exists it needs to be added manually - but if I try and do anything in the master device it just says "invalid service" (hence the reason for changing the enabled protocols on a PC)

Can anyone help?

- Andrew
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: shapa on November 20, 2012, 01:41:07 pm
LWRD is disabled by default in the newest FW's
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 20, 2012, 02:13:51 pm
I saw that if no remote exists it needs to be added manually - but if I try and do anything in the master device it just says "invalid service" (hence the reason for changing the enabled protocols on a PC)

It looks like the plugin is not well installed. Either the files you donwloasded are corrupted or you fogot to upload few of them.
Title: Re: Plugin for the USB RFXtrx from RFXCOM
Post by: lolodomo on November 20, 2012, 03:26:29 pm
I lock this topic.
Please use the topic relative to a recent version of the plugin or create a new topic to explain your problem or ask your question.