openHAB 2.0 binding

[avinaz]

Thanks @TimO , seems is working fine. I updated my installation with the new jar and now CPU is around 4-6%. Thanks a lot. By the way, I did not see a commit in the code repository.

[TimO]

@avinaz: I'm glad, thanks for testing!
Did you look into the right branch? I've committed all changes to github.

[Denke]

Hi all

Implemented a barometric sensor "pressure meter" that i sample in the sensor. Then i send the value Through "BARO". I can see in both the sensor output and the openhab debug that i receive a value for example "1.2".

I try to display this in the openhab and i dont get the Text item to update.

Anyone know how this can be as i have other values that i am able to display.

line in .items
String Pool_Pressure "Pressure (bar) [%s]" <pressure> (gPool)

line in .sitemap
Text item=Pool_Pressure

any help is appriciated as i have tried different options with Number and so on

[Denke]

Merging sensor to one

Hi
I have been thinking and i think it would be nice if there is a way to merge sensor data to one in the mysensors binding.

Background
I am trying to build a pool control based on mysensors and i have a lot of options that i wan it to handle. For example:

• on/off of my pool pumps (S_LIGHT)
• on/off of lights around the pool (S_LIGHT)
• thermostat function for heaters (S_HVAC)
• measuring pressure on pump (S_BARO)
• measuring consumed power on pump (S_POWER)

All this are using the same sensor ID and getting own child IDs. When they now are brought in to openhab they appear as single sensors

Is there a possibility to get an automatic merge for thes combined sensors?

And what do you think about the idea.
Or is there already a solution that exist that I am not aware about

example from paper UI

with openhab poolcontrol view

[meju25]

@Denke
If I understand correctly, you are suggesting to combine different sensor types in one thing.
IMHO this would jeopardize the concept of the binding. The binding provides one thing per message type (see https://www.mysensors.org/download/serial_api_15). the thing has one channel per supported sub type.
I also do not see the advantage of combining different sensor/message types in one thing as you need one item per channel anyhow.
=> this would not reduce the number of items needed.

Grouping the items in the site map - as you already did - is the best way here.

Does anybody see this differently?

[Denke]

@meju25 I saw this from a management perspective.
I have one device, my pool controller, that has multiple sensors and also channels per sensor just as HVAC that has a sum of channels. In my case i implemented a number of sensors in different types of channels "S_HVAC, S_LIGHT,...." what i see that it gets messy when you try to see if the channels are active or the pool control is active it has multiple sensors.

So maybe a suggestion is to maybe implement this in the mysensors instead of in the openhab binding.
In that case i would like to add something that allows me to tell what channels are in a "sensor" by combining differnt channels and sensor types.

I don't know if i got my message through.

But all this is mainly for management of my devices so that this gets less messy

[dakky]

@TimO do you plan to implement the reconnect thing? I often have to struggle with that and the only solution is the restart the openhab service :S Is there a problem with the reconnect or is it just "another task on the todo list"?

Greetings
Dakky

[Denke]

Hi
Is there anybody that have had a problem with the S_BARO and the V_PRESSURE channel?

I try to send a value on this channel as 1.2 I can see that the serial gateway receives it

23:10:51.808 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;0;3;0;9;read: 163-163-0 s=10,c=1,t=4,pt=7,l=5,sg=0:1.2

I set up the channel as i have done for alot of other channels through the paper ui. where i link the channel to an item.

The item file looks like this
String Pool_Pressure "Pressure [%s]" <pressure> (gPool)

the sitemap file looks like this
Text item=Pool_Pressure

result is this

The field never gets updated.
any suggestions?

[Denke]

@Denke
I cant find V_PRESSURE connected to CHANNEL_BARO below, can that be the reason?

[TimO]

@Denke : You're right, the pressure channel was missing in the thing definition. This is fixed in the current version!

@dakky : Which gateway type keeps disconnecting and why? I've a serial and ethernet gateway running side by side in OH2 and both didn't get disconnected so far. The hardest part is to recognize if the connection gets down.

[gonzalonal]

Hi @TimO . Are you having both gateways connected to same the OH simultaneously?
Any troubles with that? I imagine you should have different radio channels for each gateway, right? like two separate sensors networks.

[TimO]

Hi @gonzalonal !

Only the ethernet gateway has an attached radio.

Here is my current (MySensors) setup:

Bridge mysensors:bridge-eth:MySGW [ ipAddress="192.168.2.99", tcpPort=5003, sendDelay=100, skipStartupCheck=true  ] {
	humidity        bathHum01   			[ nodeId="101", childId="0" ]
    temperature     bathTemp01  			[ nodeId="101", childId="1" ]
    humidity		bathBat01				[ nodeId="101", childId="255" ]
    
    
    humidity        bedHum01   				[ nodeId="103", childId="2" ]
    temperature     bedTemp01  				[ nodeId="103", childId="1" ]
    humidity		bedBat01				[ nodeId="103", childId="255" ]
    
    humidity        workHum01  				[ nodeId="104", childId="2" ]
    temperature     workTemp01 				[ nodeId="104", childId="1" ]
    humidity		workBat01				[ nodeId="104", childId="255" ]
    
    humidity        kitchenHum01			[ nodeId="105", childId="2" ]
    temperature     kitchenTemp01			[ nodeId="105", childId="1" ]
	humidity		kitchenBat01			[ nodeId="105", childId="255" ]
    
    humidity        childHum01 				[ nodeId="107", childId="3" ]
    temperature     childTemp01				[ nodeId="107", childId="4" ]
    light			childLight01			[ nodeId="107", childId="0" ]
    light			childLight02			[ nodeId="107", childId="1" ]
    light			childLight03			[ nodeId="107", childId="2" ]
    
    humidity        guestHum01				[ nodeId="106", childId="0" ]
    temperature     guestTemp01				[ nodeId="106", childId="1" ]
	light			guestPresence01			[ nodeId="106", childId="3" ]
    light			livingLight01			[ nodeId="106", childId="4" ]
    light			livingLight02			[ nodeId="106", childId="5" ]
    light			livingLight03			[ nodeId="106", childId="6" ]
    light			livingLight04			[ nodeId="106", childId="7" ]
    light			corridorLight03			[ nodeId="106", childId="8" ]
    light			livingLight06			[ nodeId="106", childId="9" ]
    
    humidity        livingHum01				[ nodeId="108", childId="2" ]
    temperature     livingTemp01			[ nodeId="108", childId="1" ]
	humidity		livingBat01				[ nodeId="108", childId="255" ]
	
	humidity        gardenHum01				[ nodeId="110", childId="2" ]
    temperature     gardenTemp01			[ nodeId="110", childId="1" ]
	humidity		gardenBat01				[ nodeId="110", childId="255" ]
	motion			gardenMotion01			[ nodeId="110", childId="3" ]
    
}

Bridge mysensors:bridge-ser:MySGWKeller [ serialPort="/dev/ttyUSB0", sendDelay=100, skipStartupCheck=true ] {
    cover			kitchenShutter02 	[ nodeId="0", childId="0" ]
    cover			kitchenShutter03	[ nodeId="0", childId="1" ]
    cover			livingShutter01 	[ nodeId="0", childId="2" ]
    cover			livingShutter02 	[ nodeId="0", childId="3" ]
    cover			kitchenShutter01 	[ nodeId="0", childId="4" ]
    light			corridorLight01		[ nodeId="0", childId="5" ]
    light			corridorLight02		[ nodeId="0", childId="6" ]
    power			corridorLight01watt	[ nodeId="0", childId="7" ]
}

[dakky]

@TimO

I'm using a ethernet gateway.
the problem is: if the sensors gateway gets restarted/disconnected/updated/whatever the binding does not reconnect. The only way to fix that, is to restart openhab in order to force the binding to connect again.
Detecting an disconnect is really that hard? in the worst case, what about simply reconnecting timebased? not as cute as only reconnect when nessecary but a dirty quickfix.

[gonzalonal]

Thanks @TimO. Now I get it.
What do you think about having two gateways, one with NRF radio and the other one with RFM69 radio?

Will the binding support both gateways simultaneusly with no issues?

Another question..Will you support HearbeatRequest for the development branch?

Thanks, regards.

[gonzalonal]

Hello againg.

I have updated my OH2 to latest nightbuild from cloudbees, and also updated to lastest realease of OH2 MyS Binding.

Now, I am facing an issue, that everytime that OH2 starts, it sends out all the items status to its respective node. This is causing, for example, to open my gates, or lowering my rollershutters, even disabling/enabling my alarm system. So I have shutdown OH2 for time being.

Have anyone faced this behavior before?

This is some of the log:

15:41:40.241 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing 'mysensors:bridge-ser:gateway' takes more than 5000ms.
15:41:40.272 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.295 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.322 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.335 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.348 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.362 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.375 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.388 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.402 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.545 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'Home.items'
15:41:40.671 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.685 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.697 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.710 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.724 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.738 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.755 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.768 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.783 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.806 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;14;Gateway startup complete.
15:41:40.811 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.856 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.871 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.885 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.898 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.914 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.928 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:40.941 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:41.029 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 2;3;1;0;0;
15:41:41.110 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called
15:41:41.288 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;253;1;0;2;
15:41:41.546 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;6;1;0;2;
15:41:41.799 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;252;1;0;24;REFRESH
15:41:42.052 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;254;1;0;2;
15:41:42.307 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;254;1;0;2;
15:41:42.562 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;3;1;0;2;
15:41:42.817 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;253;1;0;2;
15:41:43.073 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 2;252;1;0;24;REFRESH

I would really appreciate your help.

[TimO]

@gonzalonal I have no idea why this should happen. The binding isn't that smart to do something like that. I've done a complete fresh installation on 21.06. with the nightly build from cloudbees and don't see this issue.

@dakky Do you see disconnection messages in the log? The binding already tries to detect a disconnect and tries to reestablish the connection when an ethernet gateway is used. Currently the time within a reconnect would be successful is very small due to sleep limitations of threads in OH2 bindings.

[gonzalonal]

Thanks @TimO . I will try to make a progressive installation and try to figure out what is causing this behavior.

I'll let you know if I find out.
Have you read my previous message?
Regards

@gonzalonal said:

Thanks @TimO. Now I get it.
What do you think about having two gateways, one with NRF radio and the other one with RFM69 radio?

Will the binding support both gateways simultaneusly with no issues?

Another question..Will you support HearbeatRequest for the development branch?

Thanks, regards.

[TimO]

@gonzalonal : I just downloaded the recent version of the binding again and I don't see this behaviour.

I hope both gateways will work together! This is was the idea. I've not tested it in combination with RFM69 but I don't see a reason why this should not work! :-)

[gonzalonal]

@TimO I have solved my probles using OH2 Beta3 and the last release of the MyS binding.

It seems that the problem is only reproduced with the last release of OH2 from Cloudbees. At least withe the release 372.

Have you tryed it?

[kolaf]

After a full computer crash (overheated CPU, CPU fan stopped working) I'm trying to set everything up on a new computer. Using the latest openhab2 beta 3 I'm having issues with using this binding. Specifically, whenever I add my standard thing configuration I get a buffer overflow in openhab which results in a core dump.

I have downloaded latest binding from the link at github, but that did not affect it. In addition to this binding I am using the zwave binding and rfxcom binding. All three connect to devices through serial ports, although I I'm not sure if they do it in the same way.

You may recall that I have had trouble using these three bindings together earlier, but for some reason things worked out and it has worked quite reliably since then.

I'm not sure which information from the system crash is useful, but if there is anything I can send you to help you figure out what happens, let me know. Also, I realise that this problem might not be related directly with mysensors, but maybe with the serial library used (I saw a reference to NVJavaSeria in the stack trace after the crash.