OpenHAB

I think the problem was interaction from my Vera controller. I removed it and now all seems to be working correctly.

Hey @rozpruwacz there is no binding for mysensor in openhab 2.3 available at the moment (my 3. post). Or am I wrong? Sorry can you please give me a smal step by step introduction? Where do i have to install what?

Hi, the binding waits for a i_heartbeat message but since 2.2 the node sends a i_pre_sleep_notification. Thats because sending to a node doesn't work anymore. I've filled a bug report here.

I had exactly the same issue on Vera after upgrading my Gateway to 2.3.0. After upgrading the Gateway I had to add each node back individually. Four of my nodes had manual Node_IDs assigned and one had auto Node_ID. As it happened I added Nodes 1 and 2 first which were manual and then added the auto node. It automatically assigned node 3 as the next available node. I then added node 4 (manual) successfully but Node 3 would only add one of its child nodes. The problem was that the auto node had added Child ids of 1 to 4. When I added the manual node 3, it correctly added child id 0 but could not add the second child as child 1 had already been allocated by the auto node. I couldn't find any error messages to indicate the problem. I eventually found this LUA code which showed all the devices with the node and child ids that had been assigned. I deleted the auto node, changed the sketch to set the node manually and re-added it. Deleted node 3 and re-added and everything was fine. I realise this was for a Vera system, but the real problem was the order of adding nodes and probably more importantly mixing nodes with manual and auto node assignments in the same mesh. I will be using manual node assignment for all nodes going forward!

Yes you need to add code - see here.... https://forum.mysensors.org/topic/4942/solved-no-heartbeat As to what happens if a node is sleeping, I have no idea, sorry.

@silex Wow! Super! Thank you!:raised_hands:

@madelle-kamois this issue is already discussed in this thread. In 2.3 mqtt Implementation has basically changed. Develloper @TimO is working on it.

It turns out that V_UNIT_PREFIX is not supported by OpenHAB's MySensors binding.

Using a stepper it's a different story

@masmat No it's not necessary to put the "Contact" in a sitemap, your arduino shall send boolean (0/1).

@gohan thanks, however the issue i'm having is not in the HVAC implementation, but in the messaging..

https://forum.mysensors.org/topic/6694/openhab-2-2-mysensors-serial-gateway-how-to-install No need to have a 2nd arduino connected through usb. Just attach a nrf chip directly to your pi

I agree with @mfalkvidd. This is not due to the sensor code but this is the way OH handles the data. I'm using OH but the MQTT 1.x binding that does not support discovery. I manually define three logical devices, temp, hum and batt in the .items file. I think this is the expected behaviour of OH. If you want them presented as one device you could combine the measurements into one string by using a rule and do some string manipulation. I do this to combine wind speed and direction into one string.

@tommas It seems to work with the older mysensors binding: org.openhab.binding.mysensors-2.2.0-SNAPSHOT.jar . 3 of my 5 nodes updated the values in openhab2 (2.3.0~20180331153334-1)

@mbj I think I finally solved the GW problem (signing password too short!). Now I'm starting to deal with OH2. I'm seeing this in the log: 2018-04-03 00:10:59.717 [DEBUG] [rotocol.mqtt.MySensorsMqttConnection] - MQTT message received. Topic: mysensors-out/99/0/1/0/1, Message: 15.0 2018-04-03 00:10:59.747 [DEBUG] [rotocol.mqtt.MySensorsMqttConnection] - Message topic part: 99/0/1/0/1 2018-04-03 00:10:59.758 [DEBUG] [rotocol.mqtt.MySensorsMqttConnection] - Converted MQTT message to MySensors Serial format. Sending on to bridge: 99;0;1;0;1;15.0 2018-04-03 00:10:59.768 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 99;0;1;0;1;15.0 2018-04-03 00:10:59.777 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Node 99 found in gateway 2018-04-03 00:10:59.785 [DEBUG] [rs.internal.gateway.MySensorsGateway] - Child 0 not present in node 99 I have one node sending temp & hum data (DHT11: child 0 hum, child 1 temp). OH2 wont autodiscover. Does this mean it must be added manually? I hope there's an autodiscover if I'm going to build a network....

either what @gohan said or persist the values in OH