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[/quote]
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.[/quote]
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…
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]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)
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.
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.[/quote]
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.
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:
[quote=“Peter, post:455, topic:170604”]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[/quote]
[quote=“Peter, post:464, topic:170604”]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[/quote]
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.
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?
[quote=“jtmoore, post:466, topic:170604”]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[/quote]
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.
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…)
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 RFXtrx Gateway 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?
It is something hardcoded in the firmware. So the choice is done by RFXCOM. But then you can change and save your changes.
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 ?
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.
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).
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
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.
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.
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”.
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.
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) ?
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 - Working With Vera On a Different Frequency (RFXCOM’s RFXrtx433) | Node Central - 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)
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.
[quote=“parkerc, post:475, topic:170604”]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)
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
…
[quote=“lolodomo, post:476, topic:170604”][quote=“parkerc, post:475, topic:170604”]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)
Is this the sort of information Bert and RFXCOM needs to explore adding the functionality ?[/quote]
Yes[/quote]
@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 Downloads. - 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.
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.
[quote=“lolodomo, post:479, topic:170604”]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[/quote]
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.
) will be in the next alpha version.