openHAB 2.0 binding

gonzalonal

Hi @andreacioni . Thats a great feature.
But for the moment, I think I prefer doing it manually, by rules, because of the way in which I can show my offline nodes in my sitemap and configure custom notifications for them.

For each node, I have a datetime item showing the time of last heartbeat response received. If more than 25' have passed (5 heartbeats request, 1 heartbeat request each 5 mins) without response, I fire up a notification telling that that specific node has gone offline.

So, back to my original question. Is there any way to get Node Ids at the rules engine?

Do you believe we can customize this kind of behavior with the beta feature proposed?

Thanks, regards.

TimO

@gonzalonal I have no clue! Could be possible, but better ask at the OH2 community because the node Id is something that is specified in the thing description (xml) and maybe it is possible to access this information in rules.

Samuel235

Does this happen to support MQTT gateways? You mention serial or ethernet, but openhab doesn't support ethernet so i'm assuming you mean ethernet as the mqtt ethernet gateway?

andreacioni

Just few posts before

@TimO said in openHAB 2.0 binding:

@Nicklas-Starkel Well no, MQTT Gateway is not yet supported.
I got distracted by my current hardware project and need to catch up on the binding. First tests of the MQTT addition to the binding look very promising and I'll include it soon.

The current release is this one: http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.1.0-SNAPSHOT.jar

While preparing the code to be included in OpenHAB2 I'm currently changing some things that will break the current configuration / things files. But I will give some information about that with the release of the next version.

Samuel235

I'm sorry, I ran a ctrl+f search and it either didn't show or i completely missed it, thank you for the prompt reply though.

In this case then i will have to wait for this release then as i can't achieve what i need to do with rules. Do we have any idea when the release will be?

Igor Antolić

Hi, did anyone hit the problem when it seems that all works fine
and then mysensors plugin start to think that it failed connecting to bridge (even if it doesnt actually)

Should I find newer version (last jar I found is since 2017-01-18)

I put message from node every 1 second, and in log you will see "0;255;3;0;9;TSF:MSG:READ...." every second
but every 10 second it recconects saying "Failed connecting to bridge...next retry in 10 seconds (Retry No.:31).... Shutting down serial connection!...

17:40:21.656 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:468
17:40:21.657 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;468
17:40:22.421 [ERROR] [col.serial.MySensorsSerialConnection] - Can't connect to serial port. Wrong port?
17:40:22.424 [ERROR] [col.serial.MySensorsSerialConnection] - Failed connecting to bridge...next retry in 10 seconds (Retry No.:31)
17:40:22.425 [DEBUG] [col.serial.MySensorsSerialConnection] - Shutting down serial connection!
17:40:22.842 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:486
17:40:22.844 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;486
17:40:24.029 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:470
17:40:24.032 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;470
17:40:25.218 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:474
17:40:25.222 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;474
17:40:26.406 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:486
17:40:26.407 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;486
17:40:27.591 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:466
17:40:27.592 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;466
17:40:28.783 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:483
17:40:28.786 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;483
17:40:29.967 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:483
17:40:29.972 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;483
17:40:31.158 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:463
17:40:31.163 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;463
17:40:32.344 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:487
17:40:32.346 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;487
17:40:32.431 [DEBUG] [col.serial.MySensorsSerialConnection] - Connecting to /dev/ttyUSB0 [baudRate:115200]
17:40:32.435 [DEBUG] [col.serial.MySensorsSerialConnection] - Final port list: /dev/ttyUSB0
17:40:33.530 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:470
17:40:33.533 [DEBUG] [rs.internal.protocol.MySensorsReader] - 202;1;1;0;37;470
17:40:34.438 [ERROR] [col.serial.MySensorsSerialConnection] - Can't connect to serial port. Wrong port?
17:40:34.440 [ERROR] [col.serial.MySensorsSerialConnection] - Failed connecting to bridge...next retry in 10 seconds (Retry No.:32)
17:40:34.441 [DEBUG] [col.serial.MySensorsSerialConnection] - Shutting down serial connection!
17:40:34.720 [DEBUG] [rs.internal.protocol.MySensorsReader] - 0;255;3;0;9;TSF:MSG:READ,202-202-0,s=1,c=1,t=37,pt=2,l=2,sg=0:472

Igor Antolić

@Igor-Antolić huh,... my mistake, just installed 2.1.0 instead of 2.0.0. It seems it is from 2017-03-07.

I dont have a good way to find last version of lib. Any suggestion how to check if last stabile version of mysensors java lib?

TimO

@Igor-Antolić I'm glad it worked after the update!

It currently is not possible to automatically update (or check) for the most recent version. There are currently two sources for the binding:

the IoT Marketplace
The link in the wiki on github

The most convenient way is the integration in the official openhab2-plugins repository and I'm working on it, but I still have a lot of homework to do.

Maybe the IoT Marketplace will soon support such mechanisms, there are a few extensions planned.

TimO

@Samuel235 said in openHAB 2.0 binding:

In this case then i will have to wait for this release then as i can't achieve what i need to do with rules. Do we have any idea when the release will be?

What is it, what you want to achieve? I'm running MQTT too, as a connection between OpenHAB2 and nodered (50% of my rules are now nodered based). My gateways are serial or ethernet based.

serial / ethernet gateway
<->
OpenHAB2 binding
<->
MQTT Event bus
<->
nodered

@Samuel235 Are you willing and have the ability to test the MQTT implementation of the binding? Any help is really appreciated!

ben999

Guys,

I am getting this in Karaf :

16:20:33.171 [WARN ] [thome.io.rest.core.item.ItemResource] - Received HTTP PUT request at 'items/MySensorsDevice21_Lock' with an invalid item type 'Status'.

and this in PaperUI

 "ERROR : undefined - undefined"  "some error occured"

when trying to link "Lock status" of an rfid node to an item in PaperUI...

Is that anything to do with the binding ? Or shall i ask eslewhere ?

Thanks a lot for your help (in general as well )

Samuel235

@TimO - I have implemented a work-around for the issue that i was facing. OpenHAB just can't handle a empty MQTT message, so there is a fix for the pulse sensor to work with OpenHAB by changing the message that it send over to the MQTT server.

If you're interested in how this is done, please refer to: https://forum.mysensors.org/topic/3088/pulse-power-meter-with-openhab/4

I will be documenting this in possibly better to read steps for people when I get chance to finish the documentation to my new hardware node for the Pulse Sensor.

RVMRVM

@LastSamurai
Hello, i'am trying to connect a RGBW node by the serial gateway, is there already a solution for the hexstring format in the bindings or do we need to handle the rgbw items separatly ?
kind regards
Roger

TimO

@RVMRVM could you give this one a try?

https://github.com/tobof/openhab2-addons/issues/76

It is not yet integrated into the main branch. If you could test it and give me some feedback I would be very grateful.

LastSamurai

@RVMRVM Sorry I haven't had the time to test anything yet (was working on another project). Might take me a while to get to.

the trung

@patrick-schaerer
hi patrick
i follow your guide with command to install MPC23017 Binding on openhab2
sudo chmod openhab.openhab /usr/share/openhab2/addons/org.openhab.binding.mcp23017-1.9.0.jar
but it not work and has information" chmod: invalid mode: ‘openhab.openhab’
then i take ":" instead of "." into account like
sudo chmod openhab:openhab /usr/share/openhab2/addons/org.openhab.binding.mcp23017-1.9.0.jar
but it same error
0_1496478264776_upload-ff8c1fc1-81fa-4e92-9e2d-46d4d7ca3f33
can you help me, please.
thanks you

TimO

@the-trung This thread is OpenHAB and MySensors binding related. Better ask here: https://community.openhab.org

In your case I suppose you need to switch chmod with chown.

carlyler

I am trying to make use of the customSensor using org.openhab.binding.mysensors-2.1.0-SNAPSHOT.jar I see the node 12 var4 message arrive but it is not being assigned to my item; am I doing something wrong? I have tried both string and number item types.

10:37:37.879 [DEBUG] [rsAbstractConnection$MySensorsReader] - 12;0;1;0;27;1023
10:37:37.880 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 12 found in gateway
10:37:37.881 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 0 found in node 12
10:37:37.882 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: var4(27) value to: 1023
10:37:37.896 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 12/0 to 2017-06-03T10:37:37.000-0400
10:37:37.901 [DEBUG] [rsAbstractConnection$MySensorsReader] - 12;255;3;0;22;63464
10:37:37.912 [INFO ] [marthome.event.ItemStateChangedEvent] - Sensor12LastUpdate changed from 2017-06-03T10:37:26.000-0400 to 2017-06-03T10:37:37.000-0400
10:37:37.925 [INFO ] [marthome.event.ItemStateChangedEvent] - mySMsg01 changed from 1;4;1;0;1;64.2 to 12;0;1;0;27;1023
10:37:37.935 [INFO ] [marthome.event.ItemStateChangedEvent] - mySMsg01 changed from 12;0;1;0;27;1023 to 12;255;3;0;22;63464
10:37:41.974 [DEBUG] [rsAbstractConnection$MySensorsReader] - 2;0;1;0;17;544
10:37:41.975 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 2 found in gateway
10:37:41.976 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 0 found in node 2
10:37:41.976 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: watt(17) value to: 544
10:37:41.984 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 2/0 to 2017-06-03T10:37:41.000-0400
10:37:41.995 [INFO ] [marthome.event.ItemStateChangedEvent] - watt01 changed from 547 to 544
10:37:42.005 [DEBUG] [rsAbstractConnection$MySensorsReader] - 2;0;1;0;24;1138982
10:37:42.006 [INFO ] [marthome.event.ItemStateChangedEvent] - Sensor02LastUpdate changed from 2017-06-03T10:37:27.000-0400 to 2017-06-03

Things

Bridge mysensors:bridge-eth:ethGatewayPi [ ipAddress="127.0.0.1", tcpPort=5003, sendDelay=200 ]
{
   /** define things connected to that bridge here */
   humidity         hum01       [ nodeId="1", childId="0" ]
   temperature      temp01      [ nodeId="1", childId="1" ]
   humidity         hum02       [ nodeId="1", childId="2" ]
   temperature      temp02      [ nodeId="1", childId="3" ]
   humidity         hum03       [ nodeId="1", childId="4" ]
   temperature      temp03      [ nodeId="1", childId="5" ]
   power            power01     [ nodeId="2", childId="0" ]
   rgbLight         rgb02       [ nodeId="6", childId="0", requestAck=true ]
   light            relay01     [ nodeId="7", childId="0", requestAck=true ]
   motion           motion01    [ nodeId="8", childId="0", requestAck=true ]
   motion           motion02    [ nodeId="9", childId="0", requestAck=true ]
   light            relay02     [ nodeId="9", childId="1", requestAck=true ]
   cover            cover03     [ nodeId="10", childId="0", requestAck=true, smartSleep=true ]
   cover            cover02     [ nodeId="11", childId="0", requestAck=true, smartSleep=true ]
   customSensor     blind01     [ nodeId="12", childId="0", requestAck=true, smartSleep=true ]
   mySensorsMessage mySMsg01    [ nodeId="999", childId="999" ]
}

items:

String blind1BatReading	    "Blind#1 Battery A/D Reading"  	<battery>			{ channel="mysensors:customSensor:ethGatewayPi:blind01:var4" }										
DateTime Sensor12LastUpdate "Last seen Nd12 [%1$ta %1$tT]"       <clock>    	{ channel="mysensors:customSensor:ethGatewayPi:blind01:lastupdate" }

edit 6/7: I stand corrected, the variables are being updated. I was fooled by the log. For some reason the log does not show the change the way it did it binding 2.0.0. I placed debug messages in my rules and they're updating.

matt shepherd

@TimO is it possible to configure using paper ui?

cheers
Matt

the trung

@TimO
I follow your guid and it's ok, then i checks karaf and see there
is this mean i installed my binding?
and i have question
did you fix error : Unable to install bundle openhab-transport-serial
thanks you so much

TimO

@matt-shepherd yes!

TimO

@carlyler thank you for filing an issue, I'll look into it.

TimO

@the-trung yes, the binding seems to be installed. Serial transport is needed for MySensors. I'm not able to answer questions about mcp binding.

RVMRVM

@TimO Hey Tim, before i start test , i have installed OH2.1 build #925 on 2 new W8 pc's.
download the org.openhab.binding.mysensors-2.1.0-SNAPSHOT.jar file and put it in the addons folder.
result:
2017-06-10 15:01:27.812 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2017-06-10 15:01:27.922 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2017-06-10 15:01:28.031 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2017-06-10 15:01:28.250 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-06-10 15:01:28.281 [ERROR] [org.openhab.binding.mysensors ] - FrameworkEvent ERROR - org.openhab.binding.mysensors
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.mysensors [182]
Unresolved requirement: Import-Package: gnu.io

at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]

i cannot start the mysensors binding ...

i have installed it on 3 diff pc's, same result , can you help mee with this, i'am stucked ..

thanks in advance
kind regards

andreacioni

@RVMRVM

Did you run feature:install openhab-transport-serial, on OH console?

RVMRVM

Oh yes, i dit not, that was the problem, now i can start to test the RGB-RGBW , hope that i can run this
thanks for the quit reaction
Roger

RVMRVM

@TimO Hello, i tried the RGB & RGBW , it looks ok but there are no commands that been send to the node and this for every item, a'im new in the openHab world, so that will be the problem.
the result is the same for RGB & RGBW
my .things file:

Bridge mysensors:bridge-eth:gateway [ ipAddress="192.168.2.190", tcpPort=5003, sendDelay=200 ] {
/** define things connected to that bridge here */
light:RGBW_23_Status [ nodeId="23", childId="0", requestAck=false]
rgbwLight:RGBW_23_Color [ nodeId="23", childId="1", requestAck=false ]
dimmer:RGBW_23_Dimmer [ nodeId="23", childId="2", requestAck=false ]
}

my .items file:

Group GF_Living "Living Room" <video> (gGF)

/* Indoor Temperatures */
//Number Temperature_GF_Living "Temperature [%.1f °C]" <temperature> (Temperature, GF_Living)

Switch RGBW_23_Status "Living" (GF_Living, Lights) { channel="mysensors:bridge-eth:gateway:RGBW_23_Status"}
Dimmer RGBW_23_Dimmer "Living" <slider> (GF_Living, Lights) ["Lighting"] { channel="mysensors:bridge-eth:gateway:RGBW_23_Dimmer"}
Color RGBW_23_Color "RGBW Light" <colorwheel> {channel = "mysensors:bridge-eth:gateway:RGBW_23_Color"}

and my .sitemap file
sitemap rvms label="test rvms"
{
Frame label="RGBW Living" {
Switch item=RGBW_23_Status label="Button Switch" mappings=[ON="on",OFF="off"]
Slider item=RGBW_23_Dimmer switchSupport
Colorpicker item=RGBW_23_Color
}
}

as result we have:
0_1497172964239_upload-df31d06d-cc9b-47df-9583-831a701cdeed
and in the paperUI:
0_1497173108301_upload-088cd943-2a85-4ad4-9197-b76b075f4ffe
this is what the log-file shows:
2017-06-11 09:50:48.187 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2017-06-11 09:50:51.161 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rvms.items'
2017-06-11 09:50:52.088 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rvms.sitemap'
2017-06-11 09:50:52.187 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rvms.things'
2017-06-11 09:50:52.978 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2017-06-11 09:50:53.006 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2017-06-11 09:50:53.073 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-06-11 09:50:53.404 [INFO ] [assic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app
2017-06-11 09:50:53.555 [WARN ] [.discovery.MySensorsDiscoveryService] - Cannot automatic discover thing node: 0, child: 255 please insert it manually
2017-06-11 09:50:53.558 [INFO ] [al.protocol.ip.MySensorsIpConnection] - Successfully connected to MySensors Bridge.
2017-06-11 09:55:56.976 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'rvms.things'
2017-06-11 09:55:56.988 [WARN ] [rsAbstractConnection$MySensorsWriter] - Interrupted MySensorsWriter
2017-06-11 09:55:56.989 [WARN ] [rsAbstractConnection$MySensorsReader] - Interrupted MySensorsReader
2017-06-11 09:55:58.010 [WARN ] [.discovery.MySensorsDiscoveryService] - Cannot automatic discover thing node: 0, child: 255 please insert it manually
2017-06-11 09:55:58.020 [INFO ] [al.protocol.ip.MySensorsIpConnection] - Successfully connected to MySensors Bridge.
2017-06-11 10:08:57.483 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'rvms.sitemap'

so what is wrong here ?
thanks in advance
Roger

FusedHe3

Hi @TimO,

I also tried the RGB Light and it seems to be working! (I am using Maghac's RGB LED strip sketch)
Auto discovery worked instantly. I did have to work with the .items file to get the color picker instead of a text input. I also get these two errors every time I send a command:

16:57:36.770 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'rgbLight01' received command 124,89,100
16:57:36.809 [INFO ] [marthome.event.ItemStateChangedEvent] - rgbLight01 changed from 359,91,100 to 124,89,100
16:57:37.117 [WARN ] [rs.internal.gateway.MySensorsGateway] - Variable 2 not present
16:57:37.222 [WARN ] [rs.internal.gateway.MySensorsGateway] - Variable 3 not present

As I'm relatively new to MySensors, I was wondering if it is normal that the RGB Light Sensor channel is used for this. Or is this just temporary until an actual RGB channel is made?

matt shepherd

I've been trying to figure this out for a while. For me openhab discovers 4 things Red, Green, Blue and Status. These are all dimmers and I can't get them all to work together as 1 colour wheel? They all work really well independently but that's as far as I got. I've also tried the .items file but with no luck.

doctor64

Hello!
I just started to play with OpenHab2 and new binding? thank you for great work.
But, i discover some strange behavior:
Openhab2, ethernet gateway, 3 mysensor nodes, all nodes sucessfully detected and configured in PaperUI, but some data looks like not updated. Looking to log i note some suspicious lines like:

00:28:47.077 [DEBUG] [rsAbstractConnection$MySensorsReader] - 3;1;1;0;0;24.6
00:28:47.078 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 3 found in gateway
00:28:47.078 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 3
00:28:47.078 [WARN ] [rs.internal.gateway.MySensorsGateway] - Variable 0 not present

Sorry, i don't know how to dump OpenHab configuration, but item configured.
Any suggestions?

carlyler

@matt-shepherd What works for me :
items - just used 1 channel, V_VAR1, but you could keep them separate

String neoPixelRgb           "RGB LED string"                           (grpLighting)  { channel="mysensors:rgbLight:ethGateway:rgb01:var1" }
Color neoPixelColor         "RGB LED string"            <colorwheel>    (grpLighting)

rule

rule "Set RGB value NeoPixelStrip"
when
    Item neoPixelColor changed
then
    val hsbValue = neoPixelColor.state as HSBType

    val brightness = hsbValue.brightness.intValue
    val redValue = ((((hsbValue.red.intValue * 255) / 100) * brightness) / 100)
    val grnValue = ((((hsbValue.green.intValue * 255) / 100) * brightness) / 100)
    val bluValue = ((((hsbValue.blue.intValue * 255) / 100) * brightness) / 100)

    val rgbHexString = String::format("%02X%02X%02X", redValue, grnValue, bluValue)
    sendCommand(neoPixelRgb, rgbHexString)
end

parsed in node

  if (message.type == V_VAR1)
  {
    // Write some debug info
    Serial.print(", New status, V_RGB: ");
    Serial.println(message.getString());

    // starting to process the hex code
    String hexstring = message.getString(); //here goes the hex color code coming from through MySensors (like FF9A00)
    long number = (long) strtol( &hexstring[0], NULL, 16);
    RGB_values[0] = number >> 16;
    RGB_values[1] = number >> 8 & 0xFF;
    RGB_values[2] = number & 0xFF;

    colorWipe(strip.Color(RGB_values[0], RGB_values[1], RGB_values[2]), 50);
  }

RVMRVM

@TimO Hey all, looks everything seems to work now, but now i have defined the bindings by the paper UI, and work with the rule definition as show by 'doctor64' ....
thanks for the help
Roger

TimO

@FusedHe3 Thank you for testing and your input!

The sketch you are using is representing itself as a RGB sensor and the log you've posted looks good.

About the fiddling with the .items file and the color picker: Thank you! That should'nt be needed anymore, I've changed it here: RGB-Test-Binding

TimO

@RVMRVM The definitions carlyler posted looks fine and I've tried to implement this logic into the binding so you won't need the rule anymore. Feel free to test my binding or stay with the rule. Hopefully both would lead to the same result.

TimO

Hey @doctor64 !

Please open a new topic. This one is getting really huge.

Please check if the temperature channel is linked. In PaperUI you may do this by moving to "Configuration" -> "Things" and click on the sensor data.

FusedHe3

@TimO No problem, glad to help!

I'll try to alter the sketch and use the new version of the binding as soon as I have my LED strip running again.

RVMRVM

@TimO Perfect, is OK for RGB & RGBW... but now the datastring you send is a decimal string, not a HEX-string as they used normal, it is not a big problem to change this feature in the node script, if you want to have a decimal string.
How do you handle the white color, becaus this is not included in the datastring info. maybe by a switch and a other variable .
something like this:

0_1497272329084_upload-bc139de4-29ff-4760-ac5e-7746249546fc

Roger

TimO

@RVMRVM Interesting. Do you have a corresponding log for me?

Here's my test:

[INFO ] [arthome.event.ItemCommandEvent:43   ] - Item 'mysensors_rgbLight_8a7ca179_rgblight_199_0_rgb' received command 71,46,91
[DEBUG] [.c.thing.internal.ThingManager:366  ] - Delegating command '71,46,91' for item 'mysensors_rgbLight_8a7ca179_rgblight_199_0_rgb' to handler for channel 'mysensors:rgbLight:8a7ca179:rgblight_199_0:rgb'
[DEBUG] [.m.c.MySensorsRGBTypeConverter:63   ] - Converting RGB Int to Hex: R d4, G e8, B 7d
[DEBUG] [b.m.i.gateway.MySensorsGateway:563  ] - Node 199 found in gateway
[DEBUG] [b.m.i.gateway.MySensorsGateway:567  ] - Child 0 found in node 199
[DEBUG] [ractConnection$MySensorsWriter:524  ] - Sending to MySensors: 199;0;1;0;40;d4e87d

RVMRVM

@TimO this is the log of the node:
15:33:19.326> 15054 TSF:MSG:READ,0-0-23,s=1,c=1,t=26,pt=0,l=10,sg=0:231,81,100
this is the result from the rule routine:
15:39:17.479> 10919 TSF:MSG:READ,0-0-23,s=1,c=1,t=26,pt=0,l=6,sg=0:FF5E28

doctor64

Hello @TimO !
I delete all things and items (btw, seems like items not deleted completely, and re-apperas after item re-create), create things again and not see error anymore. Some black magic in action, looks like.
I will create separate topic if this issue appears again. Thank you!

FusedHe3

@TimO Just tried the changes you made. Color picker now worked straight away!

I also checked the sketch and it seems to be declaring itself as an RGB Light, not as a sensor. But could it be that what I see in the PaperUI are just the labels that still need to be changed?

void presentation()
{
  // Send the Sketch Version Information to the Gateway
  sendSketchInfo(SN, SV);
  present(CHILD_ID_LIGHT, S_RGB_LIGHT);
}

One last question: the Variable 2 not present error I get everytime a command is send, is that because those two variables aren't set in the sketch I'm using?

Thanks!

edsteve

Hi,

just a quick question:
OpenHab2 can be used without touching any code right?
I use mysensors serial gateway. Tried to set it up all day yesterday from skratch. Also with OpenHabian. But no success.
So it seems i still have to edit files and folders manually in order to get it running right?

I got Domoticz working after short time. Was expecting OpenHab2 makes it even more easy

TimO

@FusedHe3 Please enable DEBUG mode in the karaf console and paste the output around Variable 2 not present here.

TimO

@edsteve Yes, that's one goal of the binding. For the serial gateway the hardest part is to determine the path of the serial port. Something like: /dev/ttyUSB0 or /dev/ttyACM0 if you're using Linux.

What exactly does not work? Please attach a log from the karaf console.

edsteve

@TimO
I use Nano Neo as Hardware with Armbian Linux and OpenHabian on top. The bundle:list showed me mysensors.
I don't find any Things. Where do i have to put this info: /dev/ttyUSB0 or /dev/ttyACM0?? In which config file?
Now i get an error with karaf saying "connection refused" when i try:

ssh -p 8101 openhab@localhost

Yesterday it worked... the karaf thing make it even more difficult.

EDIT: I just found out that i have to make a demo.things file with the code for the serial gateway.... And for sure that was not the last file which needs manual editing. I go back to Domoticz. Till OpenHab becomes same easy.

FusedHe3

@TimO Thanks for investigating!
Here's the log, but I don't know if it's of any more help.

18:36:25.233 [DEBUG] [.converter.MySensorsRGBTypeConverter] - Converting RGB Int to Hex: R 05, G 71, B ff
18:36:25.295 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 10 found in gateway
18:36:25.321 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 10
18:36:25.408 [INFO ] [marthome.event.ItemStateChangedEvent] - RGBLEDStrip_Color changed from 15,100,100 to 214,98,100
18:36:25.346 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 10;1;1;0;40;0571ff
18:36:25.365 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'RGBLEDStrip_Color' received command 214,98,100
18:36:25.840 [DEBUG] [rsAbstractConnection$MySensorsReader] - 10;1;1;0;2;1
18:36:25.863 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 10 found in gateway
18:36:25.895 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 10
18:36:25.919 [WARN ] [rs.internal.gateway.MySensorsGateway] - Variable 2 not present
18:36:26.209 [DEBUG] [rsAbstractConnection$MySensorsReader] - 10;1;1;0;3;100
18:36:26.232 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 10 found in gateway
18:36:26.254 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 10
18:36:26.276 [WARN ] [rs.internal.gateway.MySensorsGateway] - Variable 3 not present

I guess it may have something to do with a V_light and V_dimmer answer that is being send by the node. (As a reminder: I'm using this this one.)

LastSamurai

@TimO So I finally got around to testing the RGBW version of the plugin. I tested it with one sensor (light and the battery voltage) and an RGBW node.
0_1497559852937_upload-304efabd-cb8d-431a-8287-a6203833c303

Results:

RGBW color settings works well. Its a message of lengths 8 (e.g. 00ff5100) instead of the 9 from domoticz (#00ff5100). So I had to change my node's code. But your solution looks cleaner, so I guess thats fine What didn't work are all the other values beside "color". As you can see I changed the variable 1-4 and it gets send to the node as message type 24-27, which are custom variables... why did you use these?
RGBW on/off did not work. The "status" button does nothing. Log below. Would be nice to have a button to send on/off commands to the nodes.
Light and Voltage sensors seem to work just fine

By the way, short question about openhab 2: what is the difference between things and items? Seems like items/sitemaps are used in the "old" frontends to display sensors/actors. Are things the same for the new paperUI? I have just used that one yet. And why do I have to declare the gateway in a file while the rest is auto discovered (also it seems like some of you also added their sensors to the file with the gateway definition)?
Seems to be hard to find up-to-date easy information on these things, so thanks in advance for an explanation.

Log from the status button:

22:55:02.378 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'mysensors_rgbwLight_gateway_rgbwlight_10_1_status' received command OFF
22:55:02.402 [WARN ] [ensors.handler.MySensorsThingHandler] - Variable not found, cannot handle command for thing mysensors:rgbwLight:gateway:rgbwlight_10_1 of type status
22:55:02.440 [INFO ] [marthome.event.ItemStateChangedEvent] - mysensors_rgbwLight_gateway_rgbwlight_10_1_status changed from ON to OFF

LastSamurai

By the way has someone running openhab together with an echo (alexa)? I am currently trying to use that combination and at least with the RGBW nodes there seems to be no reaction (yet) to the commands.

0_1497733545612_upload-12d1dea2-7f4f-4571-9891-5ca9c8864170
Hello,
With 2 nodes, first has 1 child with id 0 , second has 2 children, id 0 and id 1, I get the following in the logs. Second node is not picked up.
Used the openhab2 zip and the jar from here http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.1.0-SNAPSHOT.jar for the installation.
All the configuration was done from the paperui.
Any thoughts ?
Best regards,
Romeo

TimO

@frg Please enter log:set DEBUG org.openhab.binding.mysensors in the karaf console and post the debug log of the binding here.

TimO

@LastSamurai Thank you for the feedback!!

I'm glad RGBW seems to work.
RGBW status indeed wasn't working, that definately was a bug and is fixed now (for RGB too).

About your general questions:

You don't have to define the gateway in the things file. It is not discovered automatically, as this is something that is not very easy to implement (i.e. search for serial connections on windows / linux, search for network devices, is it a gateway or not?)
You may just use PaperUI: Configurations -> Things and hit the white plus sign in the blue circle and select serial or ethernet gateway.

When it comes to things and items: for me, a thing is a sensor. For example the RGBW sensor is a thing in the OpenHab world. There are a few channels (children) that are frequently found, when this sensor is used: one channel for RGBW, one for status and occasionally var1-var4 and battery. The thing is defined by its channels. The thing is a representation of the hardware in this case.
The items are the representation for the UI and the user. The user uses the Color picker and the thing/hardware needs a string (#aabbccdd). There may be "hardware" behind an item but there is no need to. An example is the lastUpdate channel/item. The information is not send by the sensor, it is generated by the controller/binding.

This post is deleted!

@Timo
I attached the file.
https://notebin.cc/1jhks38r3sw
If there is something else you need me to do let me know.

TimO

@frg Okay, this is interesting.
After reviewing your log, I have no idea why this message still appears. There are 7 incoming presentation messages, all handled before. After about four minutes after the last presentation message was received there are 7 warnings about already presented childs. I don't see that behaviour in my log.
It's nothing serious we need to worry about, maybe the category "WARN" is exaggerated for this message. I'll look for that behaviour in my system, so that I may be able to reproduce it, but at the moment I don't see anything I am able to do here.

RVMRVM

This post is deleted!

Nicklas Starkel

@TimO , did you ever get MQTT to work or do you need someone to test?

TimO

Hey @Nicklas-Starkel !

Actually there is a PR for MQTT support which is a huge leap forward and needs testing: https://github.com/tobof/openhab2-addons/pull/75

I'm 90% done on fulfilling the OH2 development compliance: https://github.com/openhab/openhab2-addons/pull/2066 which I'm working on since weeks (months).

My road map is:

Finish the work on the compliance. (Maybe this week, for sure next week)
Move repository to 2.2.0 snapshot
Integrate RGB(W)
Integrate MQTT

RGB(W) needs some more attention, because there is a bug in the conversion and it needs some more testing.

The current work is a second refactoring with many changes. Also a few options (names) have changed which need some attention by the users because configurations need to be adjusted. Hopefully the names now speak more for itself.
I've also extended the JUnit Testing of the binding (which I'll need to quickly fix the RGB(W) bug).

I need to catch up with the development of the openhab2-addons base. This is done after the OH2 compliance is done. At the moment I can't compile a MQTT testversion of the binding because the repository needs to be moved to 2.2.0 Snapshot.

Sadly the process for OH2 compliance is at the moment blocking the enhancements of the binding. I had no idea this would take so long.

APL2017

Hello forum! I am very new with mySensors and OpenHAB (you've heard it before). I have OpenHab 2.1 running on Raspberri Pi2. I configured Z-wave binding, things and a few items, and it works fine. Now I am trying to bind OpenHab to a serial gateway build with Arduino Nano. The default example sketch is loaded to Arduino. The latest v2.1.0 mySensors .jar is placed in \openhab2-addons. I configured serial port as /dev/pts/2 but Gateway is offline. I tried to reboot Raspberry, Arduino but mySensors gateway is always offline, while Z-wave is online and operational. What am I doing wrong?

TimO

@APL2017 The device is definitely wrong. It should be something like /dev/ttyUSB1. Execute dmesg in the console and look for usb, ch340, ch341 or ft232.

APL2017

@TimO said in openHAB 2.0 binding:

dmesg

Thank you! When I entered serial ports as /dev/ttyUSB0, as reported by dmesg, the mySensors serial gateway binding came alive in OpenHAB. Initially, I got confused by instructions how to setup gateway in https://github.com/tobof/openhab2-addons/wiki/Configuration where I spotted serialPort="/dev/pts/2"

rob

Hello i installed openhab 2.1 and the openhab jar 2.1 file in addons directory the gateway (serial) is up and running, in the log i see the senors !! but the autodiscovery stops the second i start it and wont show anny sensors but i do see them in the log if i replace the 2.1 jar with the 2.0 jar the autodiscovery runs but doesnt show anny sensors. i had it all working but decided to start from scratch again.

Im doing something wrong but cant figure it out.

TimO

Hello @rob!

The autodiscovery is always active since version 2.1 of the binding, so there is no need to start it manually. A click on start will actually restart the scanning.
Have you checked the inbox folder? What's the debug output?

rob

@TimO Thank you for your quick reaction (and good work !!) inbox folder is empty. and here is a copy paste of the log file

2017-07-05 12:55:28.504 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;159680 TSF:MSG:FPAR REQ,ID=40
2017-07-05 12:55:28.507 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;159684 TSF:CKU:OK,FCTRL
2017-07-05 12:55:28.509 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;159687 TSF:MSG:GWL OK
2017-07-05 12:55:29.520 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;160696 !TSF:MSG:SEND,0-0-40-40,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
2017-07-05 12:55:29.878 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161053 TSF:MSG:READ,110-110-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2017-07-05 12:55:29.881 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161059 TSF:MSG:BC
2017-07-05 12:55:29.884 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161062 TSF:MSG:FPAR REQ,ID=110
2017-07-05 12:55:29.886 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161067 TSF:CKU:OK,FCTRL
2017-07-05 12:55:29.889 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161070 TSF:MSG:GWL OK
2017-07-05 12:55:30.227 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161414 !TSF:MSG:SEND,0-0-110-110,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
2017-07-05 12:55:30.546 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161715 TSF:MSG:READ,40-40-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2017-07-05 12:55:30.551 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161721 TSF:MSG:BC
2017-07-05 12:55:30.556 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161724 TSF:MSG:FPAR REQ,ID=40
2017-07-05 12:55:30.561 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161727 TSF:CKU:OK,FCTRL
2017-07-05 12:55:30.566 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;161730 TSF:MSG:GWL OK
2017-07-05 12:55:31.547 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;162736 !TSF:MSG:SEND,0-0-40-40,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
2017-07-05 12:55:31.937 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;163112 TSF:MSG:READ,110-110-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2017-07-05 12:55:31.943 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;163119 TSF:MSG:BC
2017-07-05 12:55:31.948 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;163122 TSF:MSG:FPAR REQ,ID=110
2017-07-05 12:55:31.953 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;163126 TSF:CKU:OK,FCTRL
2017-07-05 12:55:31.958 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;163129 TSF:MSG:GWL OK
2017-07-05 12:55:32.300 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;163484 !TSF:MSG:SEND,0-0-110-110,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
2017-07-05 12:55:33.999 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;165172 TSF:MSG:READ,110-110-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2017-07-05 12:55:34.002 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;165178 TSF:MSG:BC
2017-07-05 12:55:34.005 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;165181 TSF:MSG:FPAR REQ,ID=110
2017-07-05 12:55:34.008 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;165185 TSF:CKU:OK,FCTRL
2017-07-05 12:55:34.011 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;165188 TSF:MSG:GWL OK
2017-07-05 12:55:34.369 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;165554 !TSF:MSG:SEND,0-0-110-110,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
2017-07-05 12:56:07.259 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;198430 TSF:MSG:READ,5-5-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2017-07-05 12:56:07.265 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;198436 TSF:MSG:BC
2017-07-05 12:56:07.279 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;198439 TSF:MSG:FPAR REQ,ID=5
2017-07-05 12:56:07.285 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;198443 TSF:PNG:SEND,TO=0
2017-07-05 12:56:07.289 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;198447 TSF:CKU:OK
2017-07-05 12:56:07.295 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;198449 TSF:MSG:GWL OK
2017-07-05 12:56:08.130 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;199309 !TSF:MSG:SEND,0-0-5-5,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
2017-07-05 12:56:09.301 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;200465 TSF:MSG:READ,5-5-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2017-07-05 12:56:09.306 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;200471 TSF:MSG:BC
2017-07-05 12:56:09.311 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;200474 TSF:MSG:FPAR REQ,ID=5
2017-07-05 12:56:09.317 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;200478 TSF:CKU:OK,FCTRL
2017-07-05 12:56:09.320 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;200481 TSF:MSG:GWL OK
2017-07-05 12:56:10.144 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;201324 !TSF:MSG:SEND,0-0-5-5,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
2017-07-05 12:56:11.332 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;202501 TSF:MSG:READ,5-5-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2017-07-05 12:56:11.335 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;202507 TSF:MSG:BC
2017-07-05 12:56:11.338 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;202510 TSF:MSG:FPAR REQ,ID=5
2017-07-05 12:56:11.341 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;202514 TSF:CKU:OK,FCTRL
2017-07-05 12:56:11.344 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;202517 TSF:MSG:GWL OK
2017-07-05 12:56:12.162 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;203347 !TSF:MSG:SEND,0-0-5-5,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
2017-07-05 12:56:13.363 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;204536 TSF:MSG:READ,5-5-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2017-07-05 12:56:13.366 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;204542 TSF:MSG:BC
2017-07-05 12:56:13.369 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;204546 TSF:MSG:FPAR REQ,ID=5
2017-07-05 12:56:13.371 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;204549 TSF:CKU:OK,FCTRL
2017-07-05 12:56:13.374 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;204553 TSF:MSG:GWL OK
2017-07-05 12:56:14.193 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;205371 !TSF:MSG:SEND,0-0-5-5,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0

doctor64

@rob
As I see from log, gateway unable to send to sensor 5 response to find parent
2017-07-05 12:56:14.193 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3;0;9;205371 !TSF:MSG:SEND,0-0-5-5,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0

I recommend to debug your radio link, may be using MYSController

rob

@doctor64 the node 5 i manually added to openhab its a relay but isnt found with discovery (i have like 30 nodes a bunch of hue lights etc etc) everthing worked ok but my pi/openhab was taken down by the wife so had to rebuild from scratch and now the log shows the sensors but openhab wil not show me them

doctor64

@rob I have similar problems caused by unstable radio link. Long debug and playing with position of gateway and sensors in apartment, radio channel, etc resolved it, but it can be very frustrating. I recommend from my experience try to reduce distance between gateway and sensor and use MYScontroller as debug tool. Once you have stable sensor network openhab plugin start working like a charm.

As far as I understand, mysensor and openhab plugin works like this (timo, correct me if I wrong)
1: sensor establish link to gateway.
2: sensor request node ID from gateway.
3: plugin generate node ID and send it via gateway to sensor
4: if sensor with nodeID not defined aready in plugin config, sensor added to detected inbox

Looks like your setup stopped somewhere on step 3, but as check I recommend use myscontroller as independent verification

rob

@doctor64 thank you for your response !! i have my node id coded in the sensors and everything worked perfect im still thinking i made a misstake somewhere in installing openhab and mysensors the other bindings work perfect, i have it all setup in a 19inch cabinet and thats still in the same place.

rob

i just build a ethernet gateway and tried that its connected but doesnt show me the sensors like the serial gateway did in the logs it gives a different warning and i noticed that the cache only shows the node 5 i added manually not the other sensors the log showed...

==> /var/log/openhab2/openhab.log <==
2017-07-05 14:09:00.473 [DEBUG] [ensors.factory.MySensorsCacheFactory] - Cache f ile: given_ids.cached exist.
2017-07-05 14:09:00.479 [DEBUG] [ensors.factory.MySensorsCacheFactory] - Cache ( given_ids) content: [0, 5]
2017-07-05 14:09:00.585 [DEBUG] [al.protocol.ip.MySensorsIpConnection] - Set ski p check on startup to: false
2017-07-05 14:09:00.588 [DEBUG] [al.protocol.ip.MySensorsIpConnection] - Enablin g connection watchdog
2017-07-05 14:09:00.607 [DEBUG] [al.protocol.ip.MySensorsIpConnection] - Connect ing to IP bridge [192.168.178.216:5003]
2017-07-05 14:09:00.641 [DEBUG] [org.openhab.binding.mysensors ] - Service Event REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={se rvice.id=283, service.bundleid=184, service.scope=singleton} - org.openhab.bindi ng.mysensors
2017-07-05 14:09:00.659 [DEBUG] [.discovery.MySensorsDiscoveryService] - Startin g MySensors discovery scan
2017-07-05 14:09:00.683 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Initial ization of the MySensors bridge DONE!
2017-07-05 14:09:00.723 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2;
2017-07-05 14:09:00.737 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3 ;0;14;Gateway startup complete.
2017-07-05 14:09:01.131 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;0 ;0;18;2.2.0-beta
2017-07-05 14:09:01.154 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Present ation Message received
2017-07-05 14:09:01.173 [DEBUG] [ensors.factory.MySensorsCacheFactory] - Writing on cache given_ids, content: [0,5]
2017-07-05 14:09:01.178 [WARN ] [.discovery.MySensorsDiscoveryService] - Cannot automatic discover thing node: 0, child: 255 please insert it manually
2017-07-05 14:09:01.181 [DEBUG] [rsAbstractConnection$MySensorsReader] - 0;255;3 ;0;2;2.2.0-beta
2017-07-05 14:09:01.185 [DEBUG] [rsAbstractConnection$MySensorsReader] - Good,Ga teway is up and running! (Ver:2.2.0-beta)

TimO

@rob There definitely is a problem with the link between node(s) and the gateway. This is not related to the binding / controller.
Often this is related to a weak power supply.
Do you have MySensors nodes already working with one of the gateways you've build?

rob

@TimO Yeah it worked for months with a bunch of sensors like 10 temp/hum sensors relays weatherstation etc with the 2.0 binding and the hue binding etc bunch of rules had the whole house automated with alarm and whatnot and stable but then the misses managed to destroy the pi/openhab server (im still making her pay tho :D) i got the capicitators on the nrf etc all by the book made them all myself and programmed them all myself. got a new pi installed openhab 2.1 and the 2.1 binding but i just cant get them to talk to openhab again (was running 2.0 before) i reinstalled raspbian and openhab like a gazillion times now made al the opgrades incl java and the feature binding install etc.. im cleuless now

rob

@TimO i powerd the gateway with a NAS server its usb port the pi its usb port more then enough power and with a wall socket adapter used for phones and a powered usb hub i also use for external hds and all gave me the same result nojoy

stoffej

Any progress? Since I also can not see the sensors after updating to openhab 2.1.

stoffej

@stoffej ...fixed it ... I realised that the code in the sensors is waiting for the openhab to send a message to the sensor during startup of the sensor. So I had to add that into openhab..and now it works...

TimO

@TimO said in openHAB 2.0 binding:

My road map is:

Finish the work on the compliance. (Maybe this week, for sure next week)
Move repository to 2.2.0 snapshot
Integrate RGB(W)
Integrate MQTT

Timo Engelgeer

I'm trying to make a energy/Watt meter based on a ATM90E26 to send Watt, VAR, VA etc to OpenHab. But I'm running into two problems.

First, not all channels show up in OpenHab. Only Watt, KWH (which should be named kWh), Battery level and Last Update show up from my S_POWER sensor. VAR, VA and PowerFactor are missing. Also V_VAR1 (the custom values) are not showing.

Second problem is with decimal places. From my sensor I send a value with a decimal place. The log shows me:
11074 TSF:MSG:SEND,2-2-0-0,s=1,c=1,t=38,pt=0,l=6,sg=0,ft=0,st=OK:236.16
for a voltage of 236.16V. Only OpenHab ignores the decimal place most of the time. It just shows 236.0V. Somethings for a fraction of a second a non-zero decimal is shown.

Both is with OpenHAB 2.0.0 and MySensors Binding 2.1.0

TimO

Hi @Timo-Engelgeer !

KWH -> kWH.
VAR, VA & Power Factor added.
Decimal place: Did you check your item definition? kWH should be shown with two decimal places.
Is it possible for you to use the CustomSensor with var1-var5 (with a separate childId)?

Looks like this now in PaperUI:

I'll push these changes with the next release I'm working on.

Fabien

Since last update, I have to reinstall mysensors binding from IOT marketplace. But lot of warning when I'm starting :

14:21:30.964 [WARN ] [.smarthome.config.core.Configuration] - Could not set field value for field 'nodeId': Can not set int field org.openhab.binding.mysensors.config.MySensorsSensorConfiguration.nodeId to java.lang.String
java.lang.IllegalArgumentException: Can not set int field org.openhab.binding.mysensors.config.MySensorsSensorConfiguration.nodeId to java.lang.String
	at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)[:1.8.0_131]
	at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)[:1.8.0_131]
	at sun.reflect.UnsafeIntegerFieldAccessorImpl.set(UnsafeIntegerFieldAccessorImpl.java:98)[:1.8.0_131]
	at java.lang.reflect.Field.set(Field.java:764)[:1.8.0_131]
	at org.apache.commons.lang.reflect.FieldUtils.writeField(FieldUtils.java:523)[30:org.apache.commons.lang:2.6.0]
	at org.apache.commons.lang.reflect.FieldUtils.writeField(FieldUtils.java:500)[30:org.apache.commons.lang:2.6.0]
	at org.apache.commons.lang.reflect.FieldUtils.writeField(FieldUtils.java:560)[30:org.apache.commons.lang:2.6.0]
	at org.eclipse.smarthome.config.core.Configuration.as(Configuration.java:96)[94:org.eclipse.smarthome.config.core:0.9.0.201706270841]
	at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.getConfigAs(BaseThingHandler.java:248)[105:org.eclipse.smarthome.core.thing:0.9.0.201706270841]
...

And now I can't control my shutters :

14:22:11.672 [WARN ] [ensors.handler.MySensorsThingHandler] - Variable not found, cannot handle command for thing mysensors:cover:ESPgw:VoletBureau of type cover
14:22:11.674 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'VoletBureau' received command UP
14:22:11.682 [INFO ] [marthome.event.ItemStateChangedEvent] - VoletBureau changed from NULL to 0
14:22:13.198 [WARN ] [ensors.handler.MySensorsThingHandler] - Variable not found, cannot handle command for thing mysensors:cover:ESPgw:VoletBureau of type cover
14:22:13.200 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'VoletBureau' received command STOP
14:22:14.063 [WARN ] [ensors.handler.MySensorsThingHandler] - Variable not found, cannot handle command for thing mysensors:cover:ESPgw:VoletBureau of type cover
14:22:14.064 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'VoletBureau' received command UP
14:22:17.362 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 211;0;1;0;52;464.1

bundle info :

223 | Active   |  80 | 2.2.0.201707181152     | MySensors Binding

TimO

Hey @Fabien !

I've switched to a new release please look here for further information: https://forum.mysensors.org/topic/7176/openhab-2-2-binding

I've added a download link to the old version too in case you won't have time to change your configuration.

Fabien

Thann you @TimO. I will try it.

Timo Engelgeer

@TimO Thanks for your answers!

The symbol for hour really is a small h https://en.wikipedia.org/wiki/Kilowatt_hour
Great! And you'r right, it's indeed var, not VAR (weirdly enough...) Right on time for the demo
I've lost where I can check that But weird thing is, OpenHAB does show it with decimals, they're just zero most of the time...
Could do, I just used it with S_POWER because the MySensors doc said they should work with any device. Which I think does make sense in order not to cluther things with S_CUSTOMS. But then again, S_POWER having a V_VOLTAGE also makes sense

TimO

@Timo-Engelgeer

Yes, of course! It's changed by now.
Did you define something in the *.items file? "%d" instead of "%.2f" ?
It is very easy for me to add all var1-var5 channels to all things. It's just a litte copy & paste. The reason I've not done this so far is, that all channels are displayed and configured in the control section of the PaperUI (in simple mode). So if you've a temperature sensor, you additionally get: battery, lastUpdate, var1, var2, var3, var4 and var5. All of them can be disabled easily though.

Timo Engelgeer

Heyy @TimO (are you really called the same as me?) Thanks for getting back to me!

Thanks!
Nope, for now I just used the simple mode so no .items file.
Yeah, I agree it can make it feel a bit more cluttered. But then again, battery is also not used in every device (and useless in wall powered sensors). Also other channels you might not use them all as well. For example, I use S_MULTIMETER for voltage and current (because weirdly S_POWER lacks that) but impedance is an useless/meaningless channel here.

Feji

This post is deleted!

seeers

Hi, I use OpenHAB 2.1 with the OpenHAB 2.0 Binding on a Raspberry Pi with a serial RS485 gateway connected with a FTDI to USB. Sometimes the gateway freezes (at the moment i don´t know why). After pushing the reset button everything works for the next hours/days.
I´d like to reset the gateway automatically from openhab. Is it possible to reset the Gateway with this binding ? (Send DTR to the FTDI)

TimO

Hi @seeers !

Interesting idea. I suppose the arduino IDE is doing this via avrdude and we won't be able to call avrdude from within the binding. If someone has an idea on how to reset an arduino via serial/usb from within java I could look into it.

gonzalonal

@TimO you just need to toggle the DTR line.

Try:
serialPort.setDTR(true);
Thread.sleep(500);
serialPort.open();
serialPort.setDTR(false);

TimO

@gonzalonal Thanks for the hint!
For that a switch of NRSerial library to SerialPort is neccessary. A first try looks promising, but I'm not able to test it against hardware yet. Maybe @seeers might give it a try:

JAR-File

I've tested with the following bridge configuration:

Bridge mysensors:bridge-ser:gateway [ serialPort="/dev/pts/20", hardReset=false, sendDelay=200, startupCheckEnabled=true, networkSanCheckEnabled=true, networkSanCheckInterval=1, networkSanCheckConnectionFailAttempts=1 ] {
  }

The sanity check needs to fail two times. After that it will try to disconnect (and do the hardReset via DTR) and reconnect.

Log (in debug) should look like:

[DEBUG] [.p.s.MySensorsSerialConnection:138  ] - Trying to reset of attached gateway with DTR
[DEBUG] [.p.s.MySensorsSerialConnection:146  ] - Finished reset of attached gateway with DTR

I suppose only FTDI based gateways will react on that? What about sensebender gateway?

seeers

Thanks for the suggestions and the change. Maybe it`s not necessary. Today I could observe how the gateway was rebooted by openhab by Shutting down the serial connection.
I have added a "heartbeat" to my gateway, every minute a Serial.writeline "State:OK". Of course an exception appears in the openhab binding... I do not understand why the binding was down: ...Shutting down serial connection!...

11:29:43.176 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: State:OK
11:29:43.177 [WARN ] [rsAbstractConnection$MySensorsReader] - Exception on reading from connection
java.text.ParseException: class java.text.ParseException : Message length is not > 4   .....

11:29:43.181 [DEBUG] [col.serial.MySensorsSerialConnection] - Request disconnection flag setted to: true
11:29:44.873 [INFO ] [col.serial.MySensorsSerialConnection] - Connection request disconnection...
11:29:44.874 [DEBUG] [col.serial.MySensorsSerialConnection] - Request disconnection flag setted to: false
11:29:44.874 [DEBUG] [col.serial.MySensorsSerialConnection] - Shutting down serial connection!
11:29:44.875 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Stopping Writer thread
11:29:44.876 [WARN ] [rsAbstractConnection$MySensorsWriter] - Interrupted MySensorsWriter
11:29:44.877 [DEBUG] [rsAbstractConnection$MySensorsReader] - Stopping Reader thread
11:29:44.882 [WARN ] [rsAbstractConnection$MySensorsReader] - Interrupted MySensorsReader
.....
11:29:44.901 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:temperature:gateway:Temp_OG_KSued_2' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
11:29:44.905 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:humidity:gateway:Hum__OG_KSued' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
.....
11:29:48.132 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;14;Gateway startup complete.
11:29:48.132 [INFO ] [rs.internal.gateway.MySensorsGateway] - Node 0 available again!
11:29:48.133 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;0;0;18;2.1.1
11:29:48.133 [WARN ] [col.serial.MySensorsSerialConnection] - Skipping I_VERSION connection test, not recommended...
11:29:48.137 [DEBUG] [ensors.factory.MySensorsCacheFactory] - Writing on cache given_ids, content: [0,32,1,33,34,35,11,12,13,14,21,22,23,24,26,27,31]
11:29:48.138 [INFO ] [col.serial.MySensorsSerialConnection] - Successfully connected to MySensors Bridge.
11:29:48.138 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Presentation Message received
11:29:48.138 [DEBUG] [ensors.handler.MySensorsThingHandler] - MySensors Bridge Status updated to ONLINE for device: mysensors:temperature:gateway:Temp_KG_Flur_1
....
11:29:48.140 [DEBUG] [ensors.handler.MySensorsThingHandler] - MySensors Bridge Status updated to ONLINE for device: mysensors:humidity:gateway:Hum__KG_Wasch
11:29:48.142 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-ser:gateway' changed from OFFLINE to ONLINE
....

stolly82

This post is deleted!

stolly82

Dear together,

I can´t find out, why one things are not working if I save another thing with the same NodeID but different ChildID.

Example:
I have two things, one button and one door sensor.

The button is working until I add a new thing with the same nodeID (Relay).

If I save the button again, it´s working again but the Relay isn´t working again.

21:07:58.514 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'mysensors:light:Relais_Wohnzimmer_hinten_1' has been updated.
21:07:58.518 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Adding device MySensorsNode [nodeId=16, childNumber=1, chidldList={1=MySensorsChild [childId=1, nodeValue={V_WATT=MySensorsVariableVWatt [value=null], V_STATUS=MySensorsVariableVStatus [value=null], V_VAR2=MySensorsVariableVVar2 [value=null], V_VAR1=MySensorsVariableVVar1 [value=null], V_VAR3=MySensorsVariableVVar3 [value=null], V_VAR4=MySensorsVariableVVar4 [value=null], V_VAR5=MySensorsVariableVVar5 [value=null]}]}]
21:07:58.520 [DEBUG] [ensors.handler.MySensorsThingHandler] - Event listener for node 16-1 not registered yet, registering...
21:08:00.332 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:08:00.337 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:08:00.347 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:08:00.352 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:08:00.370 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:08:00.000+0200
21:08:10.860 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;0
21:08:10.865 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:10.869 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 16
21:08:10.944 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;1
21:08:10.949 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:10.952 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 16
21:08:11.012 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:08:11.016 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:08:11.019 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:08:11.022 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:08:11.050 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:08:11.000+0200
21:08:11.241 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;1;1;0;2;1
21:08:11.247 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:11.251 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 16
21:08:11.254 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: status(V_STATUS) value to: ON
21:08:11.271 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/1 to 2017-09-09T21:08:11.000+0200
21:08:11.275 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: status(V_STATUS) value to: ON
21:08:11.292 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Wohnzimmer_hinten_1 changed from OFF to ON
21:08:11.295 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/1 to 2017-09-09T21:08:11.000+0200
21:08:12.196 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;1;1;0;2;0
21:08:12.199 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:12.201 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 16
21:08:12.204 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: status(V_STATUS) value to: OFF
21:08:12.219 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/1 to 2017-09-09T21:08:12.000+0200
21:08:12.222 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: status(V_STATUS) value to: OFF
21:08:12.239 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Wohnzimmer_hinten_1 changed from ON to OFF
21:08:12.242 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/1 to 2017-09-09T21:08:12.000+0200
21:08:14.093 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;1;1;0;2;1
21:08:14.097 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:14.099 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 16
21:08:14.101 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: status(V_STATUS) value to: ON
21:08:14.118 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/1 to 2017-09-09T21:08:14.000+0200
21:08:14.121 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: status(V_STATUS) value to: ON
21:08:14.137 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Wohnzimmer_hinten_1 changed from OFF to ON
21:08:14.147 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/1 to 2017-09-09T21:08:14.000+0200
21:08:14.574 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;1;1;0;2;0
21:08:14.578 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:14.581 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 16
21:08:14.584 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: status(V_STATUS) value to: OFF
21:08:14.603 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/1 to 2017-09-09T21:08:14.000+0200
21:08:14.607 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: status(V_STATUS) value to: OFF
21:08:14.628 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Wohnzimmer_hinten_1 changed from ON to OFF
21:08:14.632 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/1 to 2017-09-09T21:08:14.000+0200
21:08:15.823 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;2;2.1.1
21:08:20.282 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:08:20.286 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:08:20.290 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:08:20.293 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:08:20.319 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:08:20.000+0200
21:08:21.117 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;0
21:08:21.122 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:21.126 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 16
21:08:21.232 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;1
21:08:21.237 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:21.243 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 16
21:08:22.162 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;0
21:08:22.168 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:22.174 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 16
21:08:22.592 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;1
21:08:22.596 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:22.599 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 16
21:08:23.331 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;0
21:08:23.334 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:23.337 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 16
21:08:23.491 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;1
21:08:23.495 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:08:23.506 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 16
21:08:30.411 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:08:30.414 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:08:30.417 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:08:30.421 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:08:30.447 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:08:30.000+0200
21:08:40.313 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:08:40.317 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:08:40.326 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:08:40.330 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:08:40.352 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:08:40.000+0200
21:08:50.328 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:08:50.332 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:08:50.337 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:08:50.342 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:08:50.367 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:08:50.000+0200
21:08:55.944 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 1;5;1;0;18;4653.2749
21:08:55.950 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 1 found in gateway
21:08:55.954 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 5 found in node 1
21:08:55.959 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: kwh(V_KWH) value to: 4653.2749
21:08:55.978 [INFO ] [marthome.event.ItemStateChangedEvent] - Stromzaeler_K changed from 4653.1982 to 4653.2749
21:08:55.983 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 1/5 to 2017-09-09T21:08:55.000+0200
21:09:00.403 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:09:00.409 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:09:00.413 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:09:00.418 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:09:00.449 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:09:00.000+0200
21:09:10.370 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:09:10.375 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:09:10.378 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:09:10.382 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:09:10.411 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:09:10.000+0200
21:09:15.971 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 1;5;1;0;24;6979929
21:09:15.974 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 1 found in gateway
21:09:15.977 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 5 found in node 1
21:09:15.980 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: var1(V_VAR1) value to: 6979929
21:09:15.998 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 1/5 to 2017-09-09T21:09:15.000+0200
21:09:16.193 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 1;5;1;0;18;4653.2866
21:09:16.196 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 1 found in gateway
21:09:16.198 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 5 found in node 1
21:09:16.203 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: kwh(V_KWH) value to: 4653.2866
21:09:16.221 [INFO ] [marthome.event.ItemStateChangedEvent] - Stromzaeler_K changed from 4653.2749 to 4653.2866
21:09:16.233 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 1/5 to 2017-09-09T21:09:16.000+0200
21:09:16.296 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;2;2.1.1
21:09:20.390 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:09:20.394 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:09:20.398 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:09:20.402 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:09:20.424 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:09:20.000+0200
21:09:30.464 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:09:30.470 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:09:30.475 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:09:30.481 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:09:30.510 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:09:30.000+0200
21:09:40.469 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:09:40.473 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:09:40.477 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:09:40.482 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:09:40.505 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:09:40.000+0200
21:10:00.627 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:10:00.629 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:10:00.634 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:10:00.640 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:10:00.666 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:10:00.000+0200
21:10:10.690 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:10:10.696 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:10:10.701 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:10:10.707 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:10:10.749 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:10:10.000+0200
21:10:15.893 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;2;2.1.1
21:10:17.669 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 1;5;1;0;18;4653.3081
21:10:17.673 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 1 found in gateway
21:10:17.675 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 5 found in node 1
21:10:17.678 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: kwh(V_KWH) value to: 4653.3081
21:10:17.702 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 1/5 to 2017-09-09T21:10:17.000+0200
21:10:17.703 [INFO ] [marthome.event.ItemStateChangedEvent] - Stromzaeler_K changed from 4653.2866 to 4653.3081
21:10:20.537 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:10:20.541 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:10:20.546 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:10:20.551 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:10:20.590 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:10:20.000+0200
21:10:30.566 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:10:30.569 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:10:30.576 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:10:30.582 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:10:30.602 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:10:30.000+0200
21:10:34.691 [DEBUG] [ensors.handler.MySensorsThingHandler] - Configuation update for thing 16-2: {nodeUpdateTimeout=-1, smartSleep=false, requestHeartbeatResponse=false, childUpdateTimeout=-1, childId=2, nodeId=16, revertState=true, requestAck=false}
21:10:34.727 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'mysensors:door:Button_Wohnzimmer_1' has been updated.
21:10:34.726 [DEBUG] [ensors.handler.MySensorsThingHandler] - Configuration: MySensorsSensorConfiguration [nodeId=16, childId=2, requestAck=false, revertState=true, smartSleep=false, childUpdateTimeout=-1, nodeUpdateTimeout=-1, requestHeartbeatResponse=false]
21:10:34.740 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Adding device MySensorsNode [nodeId=16, childNumber=1, chidldList={2=MySensorsChild [childId=2, nodeValue={V_VAR2=MySensorsVariableVVar2 [value=null], V_VAR1=MySensorsVariableVVar1 [value=null], V_TRIPPED=MySensorsVariableVTripped [value=null], V_VAR3=MySensorsVariableVVar3 [value=null], V_VAR4=MySensorsVariableVVar4 [value=null], V_VAR5=MySensorsVariableVVar5 [value=null], V_ARMED=MySensorsVariableVArmed [value=null]}]}]
21:10:34.752 [DEBUG] [ensors.handler.MySensorsThingHandler] - Event listener for node 16-2 not registered yet, registering...
21:10:37.699 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 1;5;1;0;24;6979975
21:10:37.704 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 1 found in gateway
21:10:37.709 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 5 found in node 1
21:10:37.714 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: var1(V_VAR1) value to: 6979975
21:10:37.734 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 1/5 to 2017-09-09T21:10:37.000+0200
21:10:37.821 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 1;5;1;0;18;4653.3169
21:10:37.827 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 1 found in gateway
21:10:37.833 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 5 found in node 1
21:10:37.839 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: kwh(V_KWH) value to: 4653.3169
21:10:37.859 [INFO ] [marthome.event.ItemStateChangedEvent] - Stromzaeler_K changed from 4653.3081 to 4653.3169
21:10:37.875 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 1/5 to 2017-09-09T21:10:37.000+0200
21:10:40.611 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:10:40.616 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:10:40.621 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:10:40.626 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:10:40.647 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:10:40.000+0200
21:10:46.592 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;1;1;0;2;1
21:10:46.598 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:10:46.602 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 not present in node 16
21:10:48.047 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;1;1;0;2;0
21:10:48.052 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:10:48.056 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 not present in node 16
21:10:50.179 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;0
21:10:50.184 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:10:50.186 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 16
21:10:50.188 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: CLOSED
21:10:50.200 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Wohnzimmer_hinten_2 changed from OPEN to CLOSED
21:10:50.204 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/2 to 2017-09-09T21:10:50.000+0200
21:10:50.387 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 16;2;1;0;16;1
21:10:50.389 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 16 found in gateway
21:10:50.391 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 16
21:10:50.393 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:10:50.413 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Wohnzimmer_hinten_2 changed from CLOSED to OPEN
21:10:50.422 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 16/2 to 2017-09-09T21:10:50.000+0200
21:10:50.616 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:10:50.619 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:10:50.621 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:10:50.623 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:10:50.665 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:10:50.000+0200
21:11:00.858 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:11:00.865 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:11:00.869 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 found in node 14
21:11:00.871 [DEBUG] [ensors.handler.MySensorsThingHandler] - Updating channel: tripped(V_TRIPPED) value to: OPEN
21:11:00.889 [DEBUG] [ensors.handler.MySensorsThingHandler] - Setting last update for node/child 14/2 to 2017-09-09T21:11:00.000+0200

And it´s really with any type of things like that. All nodes are working perfect in OH2 if I have only one childID as a thing. If I add the second the first is not longer working.

21:37:34.353 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:37:34.358 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:37:34.363 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 14
21:37:44.381 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:37:44.386 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:37:44.390 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 14
21:37:54.400 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:37:54.405 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:37:54.409 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 14
21:38:04.417 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:38:04.419 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:38:04.425 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 14
21:38:10.730 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:38:10.738 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 14
21:38:10.738 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Aussenstrahler_hinten changed from OFF to ON
21:38:10.742 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 14;1;1;0;2;1
21:38:10.744 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'Switch_Aussenstrahler_hinten' received command ON
21:38:13.428 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:38:13.430 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 1 found in node 14
21:38:13.432 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'Switch_Aussenstrahler_hinten' received command OFF
21:38:13.437 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Aussenstrahler_hinten changed from ON to OFF
21:38:13.437 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 14;1;1;0;2;0
21:38:14.454 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 14;2;1;0;16;1
21:38:14.457 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 14 found in gateway
21:38:14.459 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 2 not present in node 14

matt shepherd

Have you tried using Mqtt? I've recently set up a motion sensor with a mqtt gateway and it seems to be more reliable. The motion just sends a 1 for motion or 0 for no motion (obvs). I have a rule that says turn lights on if motion state =1 .You don't have to worry about connecting 'things' with openhab as you use the mqtt binding.

stolly82

@matt-shepherd
for now not.
The problem is more, that openhab 2 accepts only one device per Node with the 2.0 binding. It doesn´t matter if it it a motion sensor or if it is a second relay.

Alway´s if I setup a second thing with a existing ChildID,... the first Thing is not working anymore (LOG = Child x not present in Node x ).

I tried to install on a second Raspberry with OpenHab2 and MySensors2.0 binding (Openhabian) and there is the same issue.

That´s really really strange.

mick

I would like to attempt the irrigation controller with this binding, I believe the "light" thing is used. This only has channels: Status, Battery, LastUpdate. Is it possible to add more channels to the light thing ?, ie: V_VAR1 ... V_VAR3, regards.

andreacioni

@mick you aren't the first asking that . I opened a new issue on GitHub (https://github.com/tobof/openhab2-addons/issues/95) to discuss about adding it to the binding.

mick

Cheers @andreacioni - fingers crossed

doctor64

@TimO just updated to version 2.2.0.201708090807 of binding and get exception in network check

22:41:33.015 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2;
22:41:33.029 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;2;2.1.1
22:41:36.015 [DEBUG] [ateway.MySensorsNetworkSanityChecker] - Network sanity check: PASSED
22:41:36.015 [DEBUG] [ateway.MySensorsNetworkSanityChecker] - Sending I_HEARTBEAT_REQUESTs
22:41:36.016 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;255;3;0;18;
22:41:36.032 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;22;436674305
22:41:36.116 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 1;255;3;0;18;
22:41:36.217 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 2;255;3;0;18;
22:41:36.317 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 3;255;3;0;18;
22:41:36.398 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 3;255;3;0;22;717683
22:41:36.418 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 4;255;3;0;18;
22:41:36.518 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 5;255;3;0;18;
22:41:36.619 [DEBUG] [rsAbstractConnection$MySensorsWriter] - Sending to MySensors: 6;255;3;0;18;
22:41:36.652 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 5;255;3;0;22;9428217
22:41:36.683 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 6;255;3;0;22;3111897
22:41:39.016 [DEBUG] [ateway.MySensorsNetworkSanityChecker] - Node 1 request heartbreat answer, missing null of 10
22:41:39.016 [ERROR] [ateway.MySensorsNetworkSanityChecker] - Exception in network sanity thread checker
java.lang.NullPointerException
	at org.openhab.binding.mysensors.internal.gateway.MySensorsNetworkSanityChecker.checkHeartbeatsResponse(MySensorsNetworkSanityChecker.java:178)[195:org.openhab.binding.mysensors:2.2.0.201708090807]
	at org.openhab.binding.mysensors.internal.gateway.MySensorsNetworkSanityChecker.run(MySensorsNetworkSanityChecker.java:122)[195:org.openhab.binding.mysensors:2.2.0.201708090807]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_144]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_144]
	at java.lang.Thread.run(Thread.java:748)[:1.8.0_144]

andreacioni

Hi @doctor64, could you please post your things configuration file?

doctor64

@andreacioni All mySensors item defined using auto-discovery, so no things file in configuration. I'm think you mean this file? 0_1506175698221_org.eclipse.smarthome.core.thing.Thing.json

andreacioni

@doctor64 it is enough, I can replicate it. Thanks for reporting this issue . You can keep track of it here: https://github.com/tobof/openhab2-addons/issues/97

gonzalonal

Today brand new setup with fail results.

I have installed a brand new OH2 snapshot build #1047 and the latest relese of the binding available.

I am using just a single node as ethernet gateway. After a couple of minutes the binding stops sending the messages to the node. It logs as it would send them but nothing is really sent out. I have sniffed the connection with wireshark.

Sometimes, while looking the binding debug logs at OH2 console, it hangs and I have to restablish the connection. This last issue seems more related to OH2 itself but maybe something wrong in the binding is causing it. Again, the is not a single clue in the logs about this.

I have just installed the OH2.1 stable release with the latest release of the binding and everything runs great yet.

Anyone with a similar experience?

AndrewZ

@gonzalonal I've observed something similar on my system, as I recall the binding wasn't even able to establish the initial connection to a gateway. Have OH upgraded today from an earlier build (~3 weeks old).

openHAB 2.0 binding

Suggested Topics

Boxes and Enclosures
Enclosures / 3D Printing • • PITP2

openHAB 2.2 binding
OpenHAB • • TimO

OH3 - MySensors Binding
OpenHAB • • Peter Loeffler

OH3 Serial Gateway Problem
OpenHAB • • seppi9

voltage sensor via esp and mqtt
OpenHAB • • muhammed

OH2.5.9 / ethernet gateway / autodiscovery?
OpenHAB • • Stefferd

0
Online

11.4k
Users

11.1k
Topics

112.7k
Posts

openHAB 2.0 binding

Suggested Topics

Boxes and Enclosures Enclosures / 3D Printing • • PITP2

openHAB 2.2 binding OpenHAB • • TimO

OH3 - MySensors Binding OpenHAB • • Peter Loeffler

OH3 Serial Gateway Problem OpenHAB • • seppi9

voltage sensor via esp and mqtt OpenHAB • • muhammed

OH2.5.9 / ethernet gateway / autodiscovery? OpenHAB • • Stefferd

0Online

11.4kUsers

11.1kTopics

112.7kPosts

Boxes and Enclosures
Enclosures / 3D Printing • • PITP2

openHAB 2.2 binding
OpenHAB • • TimO

OH3 - MySensors Binding
OpenHAB • • Peter Loeffler

OH3 Serial Gateway Problem
OpenHAB • • seppi9

voltage sensor via esp and mqtt
OpenHAB • • muhammed

OH2.5.9 / ethernet gateway / autodiscovery?
OpenHAB • • Stefferd

0
Online

11.4k
Users

11.1k
Topics

112.7k
Posts