LightwaveRF Binding Updated

Hey @neil_renaud

Looks like its still broken for me on ALPHA10.

Yeah me too. On alpha10 too.

C

Hi,

Can you post some sample logs that are causing an issue?

Thanks,
Neil

Here you go, a typical bunch of errors. I get a batch like this roughly once an hour it seems:

> 2016-01-20 17:09:17.863 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Long], State[xx.xx]
> 2016-01-20 17:09:17.864 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Dawn], State[2016-01-20T07:55:10]
> 2016-01-20 17:09:17.865 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_IP], State[192.168.1.xx]
> 2016-01-20 17:09:17.865 [INFO ] [.l.internal.LightwaveRfBinding] - State was null for LW_WifiL_Ver type VERSION, message org.openhab.binding.lightwaverf.internal.command.LightwaveRfWifiLinkStatusMessage@cee09
> 2016-01-20 17:09:17.866 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Lat], State[xx.xx]
> 2016-01-20 17:09:17.866 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Dusk], State[2016-01-20T16:29:39]
> 2016-01-20 17:09:17.867 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Uptime], State[1062250]
> 2016-01-20 17:09:17.882 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Long], State[xx.xx]
> 2016-01-20 17:09:17.884 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Dawn], State[2016-01-20T07:55:10]
> 2016-01-20 17:09:17.885 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_IP], State[192.168.1.xx]
> 2016-01-20 17:09:17.886 [INFO ] [.l.internal.LightwaveRfBinding] - State was null for LW_WifiL_Ver type VERSION, message org.openhab.binding.lightwaverf.internal.command.LightwaveRfWifiLinkStatusMessage@3b19a7
> 2016-01-20 17:09:17.887 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Lat], State[xx.xx]
> 2016-01-20 17:09:17.888 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Dusk], State[2016-01-20T16:29:39]
> 2016-01-20 17:09:17.888 [INFO ] [.l.internal.LightwaveRfBinding] - Update from LightwaveRf ItemName[LW_WifiL_Uptime], State[1062250]

EDIT: Yeah you’re right, they’re not errors! Oops, sorry…

Hey,

That doesn’t look like any errors? What’s going wrong or not working as expected?

Neil

1 Like

Hey,

I’ve created a build with the energy monitor fix here: https://github.com/foxy82/openhab/releases/tag/1.8.0_alpha11

Neil

Hey @neil_renaud

I am testing Alpha11 build now, thanks.

Hi @neil_renaud,

The status messages are still broken with ALPHA11, here is the log output…

2016-02-02 12:35:47.268 [ERROR] [l.internal.LightwaveRfWifiLink:173 ]- Message not recognised: *!{"trans":666,"mac":"00:00:00","time":1454416620,"type":"hub","prod":"lwl","fw":"N2.91Z","uptime":2171250,"timeZ":0,"lat":00.00,"long":00.00,"duskT":1454432118,"dawnT":1454399231,"tmrs":0,"evns":0,"run":0,"macs":9,"ip":"0.0.0.0","devs":0}

2016-02-02 12:35:47.279 [DEBUG] [.l.i.LightwaveRFReceiverThread:118 ]- Message received from: /0.0.0.0 message:*!{"trans":666,"mac":"00:00:00","time":1454416620,"type":"hub","prod":"lwl","fw":"N2.91Z","uptime":2171250,"timeZ":0,"lat":00.00,"long":00.00,"duskT":1454432118,"dawnT":1454399231,"tmrs":0,"evns":0,"run":0,"macs":9,"ip":"0.0.0.0","devs":0}

Interesting the “prod” on your wifi link is different to mine. I’ve got a really old wifi link do you have a new one?

Fix is here: https://github.com/foxy82/openhab/releases/tag/1.8.0_alpha12

However note - I did a large refactor to split commands and messages better - whilst all the tests still pass I’ve yet to use this version in my own system.

Hey @neil_renaud,

I have just installed the update and am waiting for a status message, I will post up once one is received.

As for my WifiLink, yes its one of the newer models that doesn’t have a display and is much smaller.

Thanks

The way I forced a status message was to pull the power on the wifi link and then reconnect it after a minute. Then another few mins later it will update.

Hey @neil_renaud,

Great work, everything is now working except FW version, I had it as just VERSION, I have changed the item to the following :-

{lightwaverf="serial=wifilink,type=WIFILINK_VERSION"} 

Is that correct?

WIFILINK_FIRMWARE

Regards,
Neil

Updated, thanks Neil.

Hi,
Im a total newbie to most of this digging around in openhab so please bear with me if this is covered above and I just need help to interpret what to do…
I’ve had a stable openhab / lightwaveRF setup working for a while on a Pi for over a month now and at the weekend purchased the lightwaveRF energy monitor, it seemed to bind and gave an ok to the bind request and is registered fine on my phone and tablet but in the openhab log is throwing up the following.

2016-02-08 23:10:03.884 [WARN ] [.l.internal.LightwaveRfBinding] - No item for incoming message[*!{“trans”:3511,“mac”:“ff:ff:ff”,“tim"pwrMtr”,“serial”:“FFFFFF”,“router”:FFFFFF,“type”:"energy,“cUse”:"549,“todUse”:"7226,“yesUse”:"0}]

Just a couple of questions if anyone can help ,

  1. Have I done something wrong or missed a step out ?
  2. Is this an error I can fix ? (I have tried the upgrade to Release Lightwave RF Alpha12 · foxy82/openhab · GitHub github.com )
  3. If the above is ok and working how do I read/display the data ?

Any help or pointers gratefully received

Dave

Hey,

That is a warning to say openhab received a message but you’ve not got any items configured for openhab to set the values.

Look at the wiki and it will show you how to configure items for the energy monitor (https://github.com/openhab/openhab/wiki/LightwaveRF-Binding)

It will say available from 1.9.0 but if you are on the latest alpha then it will work.

Neil

Hi

Newbie here looking for some help.
Trying to get openHAB to display readings from my Lightwaverf energy meter.
I’m using the 1.8.2 release of openHAB and the Lightwaverf binding.
The run.log file is showing an error:-

2016-04-27 20:51:13.212 [DEBUG] [.l.i.LightwaveRFReceiverThread] - Message received from: /192.168.XX.XX message:*!{“trans”:38,“mac”:“wifilink”,“time”:1461790273,“prod”:“pwrMtr”,“serial”:“energymeter”,“router”:“000500”,“type”:“energy”,“cUse”:2645,“todUse”:304,“yesUse”:0}
2016-04-27 20:51:13.212 [ERROR] [l.internal.LightwaveRfWifiLink] - Error converting message: *!{“trans”:38,“mac”:“wifilink”,“time”:1461790273,“prod”:“pwrMtr”,“serial”:“energymeter”,“router”:“000500”,“type”:“energy”,“cUse”:2645,“todUse”:304,“yesUse”:0}

Any help would be appreciated.

Thanks

Ian

Hi Neil

I’m setting up my new lw energy monitor, i’ve managed to get most of the readings to come up with a few exceptions.
ENERGY_YESTERDAY_USAGE only ever comes back with 0, ENERGY_MAX_USAGE returns -, SIGNAL throws the following message in the log

2016-06-14 21:27:48.309 [INFO ] [.l.internal.LightwaveRfBinding] - State was null for lw_energy_signal type SIGNAL, message org.openhab.binding.lightwaverf.internal.message.response.LightwaveRfEnergyMonitorResponse@a4a8a2

Also is there a way to get the battery condition to report back.

I think i’m running the latest version “org.openhab.binding.lightwaverf-1.8.0-SNAPSHOT”

Thanks in advance

Anthony

Hi @infrared

I had the same issues - recently (last week) purchased the Energy monitor. It seems the messages have changed format.

I had to modify the latest source and build my own jar. Now working perfectly.

the messages have changed from :

*!{"trans":215955,"mac":"03:41:C4","time":1435620183,"prod":"pwrMtr","serial":"9470FE","signal":79,"type":"energy","cUse":271,"maxUse":2812,"todUse":8414,"yesUse":8377}

to

*!{"trans":9920,"mac":"20:04:9E","time":1473247897,"prod":"pwrMtr","serial":"7D91FE","router":"4F0500","type":"energy","cUse":791,"todUse":8312,"yesUse":0}

@neil_renaud Was the original plugin built by referencing the API docs from Lightwaverf or was it from monitoring the network, and reverse engineering. Just wondering how to treat the changes in API as there doesn’t seem to be a version anywhere in the message.

Thanks
Jon

Hi,

for energy monitoring this was built from people sending in their own network sniffs as I don’t have a working Lightwave energy monitor.