RFXCOM / LightwaveRF (Lighting5) Examples

[John Harrison]

Hi All

Could anybody please post a working example of a LightwaveRF Mood switch?

I have the following (I am using binding version 1.5.1 from cloudbees build 702)

in items:

Number LivingRoomMood "LivingRoomMood" { rfxcom=">15903586.16:LIGHTING5.LIGHTWAVERF:Mood" }

and in SiteMap:

Switch item=LivingRoomMood icon="light-on" mappings=["Group Off"="All Off", "Group Mood 1"="Mood 1"]

but no matter how I fiddle, I cannot get this to work!

Thank you!

[Paul Hampson]

Have you got some debug log output from rfxcom with the mood switch?

[John Harrison]

Hi Paul

When I click "All Off" I get...

Received HTTP POST request at 'items/LivingRoomMood/' with an invalid status value 'GROUP_OFF', 

I guess this is because the item type is number, but that seems to be necessary.

[Paul Hampson]

Sorry I meant from the openhab debug logs.

You can add something like this <logger name="org.openhab.binding.rfxcom" level="DEBUG" /> to your configurations/logback.xml file. This will give output in the openhab.log file when RFXCom is receiving data. Try triggering the switch and posting the relevant output from the log.

Thanks,
Paul

[Mat Smith]

John

I still haven't got moods working. I started using a compiled version of Neil Renaud's amended binding (see here: https://groups.google.com/d/msg/openhab/VpKkxCimHFE/5GFsoddUm24J)

And also here for original thread: https://groups.google.com/d/msg/openhab/s9RyVgXTlFM/PVweykTNL0QJ

Please explain, what is the "cloudbees build"? I googled but couldn't find an answer to that!

Mat

[John Harrison]

Hi Mat

Cloudbees is a continuous delivery system - basically every night the latest version of the openhabsource gets built by cloudbees.

https://openhab.ci.cloudbees.com/job/openHAB/

[John Harrison]

Hi Paul

I have tried this, even logging rfxcom to its own file, and setting the debug level to Trace.

There is absolutely nothing appearing in the rfxcom log when I select the mood switch on the UI.

In the main log I see 

INFO  runtime.busevents[:22] - LivingRoomMood received command 1

(It's happier since I changed the entry in the sitemap to 

Switch item=LivingRoomMood label="Scene" mappings=[1="TV", 2="Dinner", 3="Reading"] 

)

However it just seems that the binding is entirely ignoring the command.

For reference, my item still looks like

Number LivingRoomMood "LivingRoomMood" { rfxcom=">15903586.16:LIGHTING5.LIGHTWAVERF:Mood" }

[Aitor Iturrioz Rodríguez]

Hi guys!

I'm trying to do something similar to what you are doing, but in my case I'm playing with the physical "Mood Remote" from LightWaveRF. As far as I can understand, what you are trying to accomplish is to be able to send mood commands to your switches, aren't you?

I'm using the latest RFXCom binding from CloudBees (1.6.0 snapshot) and I have defined the following Mode: 0D01000302533C00022501010000. It's supposed to support AC, Oregon Devices, CM160, X10 and LightwaveRF, just the devices that I need.

The problem is that I have enabled DEBUG log level to see the "Mood Remote" messages, but I don't see anything in the log file when I press the buttons :( AC, Temperature and Energy commands are correctly received and displayed in the openhab.log file.

I haven't tried to set any item binded to the "Mood Remote" before solving this problem, but I don't know what else can be done :( If I use the same configuration in the RFXmngr program everything works correctly, the "Mood Remote" messages are displayed as they should after pressing the buttons.

Can anyone give me any clue about what to do?

Many many thanks for your help and if you need any info or log file don't hesitate to ask.

Best regards,

Aitor

[Paul Hampson]

The first stage is to find out if the RFXCOM is receiving the transmission. If you have enabled the debug log output in logback.xml you should see the data string (hexadecimal string) being output from the binding. It will have either ' Data received:' or ' Unknown data received, data' before it. Once you've confirmed that then you can begin to add code to decode the data.

Cheers
Paul

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/busLdamqLNk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Aitor Iturrioz Rodríguez]

Hi Paul!

Many thanks for your message and your help, now I have it working!!! Hurrah!!

Just for future references, I have solved the problem using the RXFmngr for Windows in another PC. The problem was that, by default, my RFXCom device didn't have the LightWaveRF "class/category" activated, and although for testing purposes I was enabling it, I was not pressing the "save settings" button in the application to store the values in the physical device. I don't know if I'm explaining myself well enough, sorry :( What I finally did was: 

1. Open the application

2. Connect the program to the device (COM5)

3. Check the classes/categories in which I was interesed on (in my case: AD/LightWaveRF, AC, X10 and Oregon Scientific)

4. Press the "Set Mode" button

5. Press the "Save Settings" button!!

Not pressing the "Save Settings" button was doing that, in case of closing and launching again the app, the AD/LightWaveRF class remains uncheck. If I restart now the program, the checked boxes are the ones defined before pressing the "Save Settings" button.

I hope that now it's easier to follow what I have done :D Anyway, if someone feels that his problem is related to mines, don't hesitate to ask and I will try to explain it using different words.

Best regards to everyone,

Aitor

[Mat Smith]

Aitor

No, your words make total sense! You do have to enable the protocol using RFXMngr.

Interestingly, another open source program called Domoticz (you probably heard of it?) has the option to set the mode within the web interface.

Maybe that's something that could be built-in to the upcoming release of OpenHAB?

[Pauli Anttila]

Hi Aitor,

if I understand you problem correctly, you did introduced correct RFXCom device mode in rfxcom binding configuration (Mode: 0D01000302533C00022501010000), but still binding was not able to receive LightWaveRF messages (I did not check is your mode correct)? If so, it's  bug on the binding, because setMode configuration variable in rfxcom binding configuration is exactly intended for that (no need to handle RFXCom device configuration via RFXMngr at all). 

In fact, I never tested setMode functionality very well on binding, so there definitely could be problem. Could you provide openhab debug log, where RFXCom device mode setting is included?

I was also little bit lazy on setMode functionality implementation. Currently mode is long hex string which is not very user friendly, so some day it should be divided to individual message classes (at least when OH2 is ready).

Current situation:

# Set mode command for controller (optional)

# E.g. rfxcom:setMode=0D000000035300000C2F00000000 

#rfxcom:setMode=

Should be:

# Configure supported message classes to the controller (optional)

#rfxcom:Lighting4=True

#rfxcom:AC=True

#rfxcom:Rubicson=False

#rfxcom:La Crosse=False

#rfxcom:OregonScientific=True

...

-Pali 

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.

[ge...@ge-volution.eu]

I recently had the same problem as Aitor; however with Oregon Scientific temp/hydro sensors.  I was testing in RFXmgr and had selected the protocols that I wanted and was seeing all of the values coming in as desired.  However as I did not hit the SAVE button, the mode was not stored to the RFXCOM NVRAM.  So when I plugged it back into my RPi w/ OpenHAB there were no updates taking place and nothing in the events log.

How I was able to detect and resolve this was by enabling the DEBUG logging in OpenHAB which had the card status, mode, and supported protocols configured for the card come though in the log.  There is was evident that the Oregon Scientific=FALSE was showing that the RFXCOM card was not listening for the protocol I was most interested in!