openHAB 2.0 binding
-
I think i need some help. I am not shure, if my problem lies on the openHab2 side or if there is a problem with the mysensors addon.
This is what i I have:
A working mysensors addon. I receive updates in OpenHab:2016-06-06 07:12:08.483 [DEBUG] [org.openhab.binding.mysensors ] - BundleEvent STARTING - org.openhab.binding.mysensors 2016-06-06 07:12:08.550 [DEBUG] [org.openhab.binding.mysensors ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.mysensors.internal.MySensorsHandlerFactory, component.id=7, service.id=102, service.bundleid=11, service.scope=bundle} - org.openhab.binding.mysensors 2016-06-06 07:12:09.070 [DEBUG] [org.openhab.binding.mysensors ] - BundleEvent STARTED - org.openhab.binding.mysensors 2016-06-06 07:12:12.062 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin 2016-06-06 07:12:18.694 [ERROR] [org.openhab.ui.habmin ] - [org.openhab.ui.habmin.designer(3)] bind method [setItemRegistry] not found; Component will fail 2016-06-06 07:12:18.702 [ERROR] [org.openhab.ui.habmin ] - [org.openhab.ui.habmin.designer(3)] bind method [setItemRegistry] not found 2016-06-06 07:12:25.252 [ERROR] [org.eclipse.smarthome.core.transform] - [org.eclipse.smarthome.action.transformation.action(51)] Circular reference detected, getService returning null 2016-06-06 07:12:39.288 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_light_gateway_Light_1_0-mysensors:light:gateway:Light_1_0' has been added. 2016-06-06 07:12:39.315 [INFO ] [smarthome.event.ItemAddedEvent ] - Item 'home_group_88a3d2a1' has been added. 2016-06-06 07:12:42.030 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /ui 2016-06-06 07:12:42.261 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start 2016-06-06 07:12:42.825 [WARN ] [sql.internal.MysqlPersistenceService] - The SQL user is missing - please configure the sql:user parameter in openhab.cfg 2016-06-06 07:12:43.071 [INFO ] [assic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app 2016-06-06 07:12:43.114 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app 2016-06-06 07:12:43.470 [INFO ] [.openhab.core.internal.CoreActivator] - openHAB runtime has been started (v2.0.0, build b2). 2016-06-06 07:12:43.479 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.sitemap' 2016-06-06 07:12:44.159 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.things' 2016-06-06 07:12:44.397 [INFO ] [smarthome.event.ThingAddedEvent ] - Thing 'mysensors:bridge-eth:gateway' has been added. 2016-06-06 07:12:44.468 [INFO ] [nsors.handler.MySensorsBridgeHandler] - Using Metric measure unit 2016-06-06 07:12:44.470 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Set skip check on startup to: false 2016-06-06 07:12:44.489 [DEBUG] [org.openhab.binding.mysensors ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=278, service.bundleid=11, service.scope=singleton} - org.openhab.binding.mysensors 2016-06-06 07:12:44.527 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Initialization of the MySensors Bridge 2016-06-06 07:12:44.531 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-eth:gateway' changed from UNINITIALIZED to INITIALIZING 2016-06-06 07:12:44.540 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - Connecting to bridge ... 2016-06-06 07:12:44.762 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 0;0;3;0;2; 2016-06-06 07:12:44.770 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;14;Gateway startup complete. 2016-06-06 07:12:44.776 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;11;EthernetGateway 2016-06-06 07:12:44.778 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;12;1.0 2016-06-06 07:12:44.849 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;2;2.0.0-beta 2016-06-06 07:12:44.852 [DEBUG] [s.internal.MySensorsBridgeConnection] - Good,Gateway is up and running! (Ver:2.0.0-beta) 2016-06-06 07:12:44.858 [DEBUG] [org.openhab.binding.mysensors ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:bridge-eth, thing.id=mysensors:bridge-eth:gateway, service.id=279, service.bundleid=11, service.scope=singleton} - org.openhab.binding.mysensors 2016-06-06 07:12:44.859 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-eth:gateway' changed from INITIALIZING to ONLINE 2016-06-06 07:12:44.900 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'logging.persist' 2016-06-06 07:12:44.990 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rrd4j.persist' 2016-06-06 07:12:45.047 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.items' 2016-06-06 07:12:45.168 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c0-mysensors:light:gateway:n1c0:status' has been added. 2016-06-06 07:12:45.171 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c1-mysensors:light:gateway:n1c1:status' has been added. 2016-06-06 07:12:45.174 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c2-mysensors:humidity:gateway:n1c2:hum' has been added. 2016-06-06 07:12:45.178 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c3-mysensors:humidity:gateway:n1c3:hum' has been added. 2016-06-06 07:12:45.182 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c4-mysensors:humidity:gateway:n1c4:hum' has been added. 2016-06-06 07:14:50.818 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;1 2016-06-06 07:14:50.820 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received! 2016-06-06 07:14:55.831 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;0 2016-06-06 07:14:55.832 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received! 2016-06-06 07:28:01.373 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;1 2016-06-06 07:28:01.375 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received! 2016-06-06 07:28:06.385 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;0 2016-06-06 07:28:06.387 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received! 2016-06-06 07:32:21.567 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;1 2016-06-06 07:32:21.568 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received! 2016-06-06 07:32:26.578 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;0 2016-06-06 07:32:26.582 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received!Seems ok.
But I am not able to see the result in Openhab
my.thing:
mysensors:bridge-eth:gateway [ ipAddress="192.168.100.10", tcpPort=5003, sendDelay=200 ] { /** define things connected to that bridge here */ light n1c0 [ nodeId="1", childId="0", requestAck=true ] light n1c1 [ nodeId="1", childId="1", requestAck=true ] humidity n1c2 [ nodeId="1", childId="2" ] humidity n1c3 [ nodeId="1", childId="3" ] humidity n1c4 [ nodeId="1", childId="4" ] }my.item:
Switch n1c0 "PFLANZENNAME1 Pumpe" <water> (gGF_irrigation01) { channel="mysensors:light:gateway:n1c0:status" } Switch n1c1 "PFLANZENNAME1 Pumpe Automatikmodus" <water> (gGF_irrigation01) { channel="mysensors:light:gateway:n1c1:status" } Number n1c2 "PFLANZENNAME1 Bodenfeuchtigkeit max" <water> (gGF_irrigation01) { channel="mysensors:humidity:gateway:n1c2:hum" } Number n1c3 "PFLANZENNAME1 Bodenfeuchtigkeit min" <water> (gGF_irrigation01) { channel="mysensors:humidity:gateway:n1c3:hum" } Number n1c4 "PFLANZENNAME1 Bodenfeuchtigkeit" <water> (gGF_irrigation01,gGF_eating) { channel="mysensors:humidity:gateway:n1c4:hum" }There are simply no values in openhab although I see the debug messages in the openhab log.
Any idea how to fix it? I did not use the autodicovery of openhab paper UI. what confuses me is the name of the link used by openhab:2016-06-06 07:12:45.168 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c0-mysensors:light:gateway:n1c0:status' has been added.That does not match the channel. is that ok?
Thank
DakkyEDIT: updated openhab log to complete startup process and added question
@dakky said:
I think i need some help. I am not shure, if my problem lies on the openHab2 side or if there is a problem with the mysensors addon.
No idea anyone? i'm stucked here and I'd really like to continue :(
EDIT: MAybe this helps debugging: it seem there is no "link" between things and items. The rest endpoints reveals, that the thing has no item:
[ { "statusInfo": { "status": "ONLINE", "statusDetail": "NONE" }, "link": "http://autohome:8080/rest/things/mysensors:bridge-eth:gateway", "configuration": { "tcpPort": 5003, "ipAddress": "192.168.100.10", "skipStartupCheck": false, "imperial": false, "sendDelay": 200 }, "properties": {}, "UID": "mysensors:bridge-eth:gateway", "channels": [ { "linkedItems": [], "id": "n1c0", "itemType": "light", "properties": {} }, { "linkedItems": [], "id": "n1c1", "itemType": "light", "properties": {} }, { "linkedItems": [], "id": "n1c2", "itemType": "humidity", "properties": {} }, { "linkedItems": [], "id": "n1c3", "itemType": "humidity", "properties": {} }, { "linkedItems": [], "id": "n1c4", "itemType": "humidity", "properties": {} } ] } ]Greetings
-
Dammit ... found the error ;)
created a pull request: https://github.com/tobof/openhab2-addons/pull/18
Greetings
Dakky -
Glad you found it! :+1:
I'm a little low in time at the moment, I will look at the PRs next weekend. Thank you for the contributions! :)
-
-
Thanks @TimO , seems is working fine. I updated my installation with the new jar and now CPU is around 4-6%. Thanks a lot. By the way, I did not see a commit in the code repository.
-
Hi all
Implemented a barometric sensor "pressure meter" that i sample in the sensor. Then i send the value Through "BARO". I can see in both the sensor output and the openhab debug that i receive a value for example "1.2".
I try to display this in the openhab and i dont get the Text item to update.
Anyone know how this can be as i have other values that i am able to display.
line in .items
String Pool_Pressure "Pressure (bar) [%s]" <pressure> (gPool)line in .sitemap
Text item=Pool_Pressureany help is appriciated as i have tried different options with Number and so on
-
Merging sensor to one
Hi
I have been thinking and i think it would be nice if there is a way to merge sensor data to one in the mysensors binding.Background
I am trying to build a pool control based on mysensors and i have a lot of options that i wan it to handle. For example:- on/off of my pool pumps (S_LIGHT)
- on/off of lights around the pool (S_LIGHT)
- thermostat function for heaters (S_HVAC)
- measuring pressure on pump (S_BARO)
- measuring consumed power on pump (S_POWER)
All this are using the same sensor ID and getting own child IDs. When they now are brought in to openhab they appear as single sensors
Is there a possibility to get an automatic merge for thes combined sensors?
And what do you think about the idea.
Or is there already a solution that exist that I am not aware aboutexample from paper UI
with openhab poolcontrol view
-
Merging sensor to one
Hi
I have been thinking and i think it would be nice if there is a way to merge sensor data to one in the mysensors binding.Background
I am trying to build a pool control based on mysensors and i have a lot of options that i wan it to handle. For example:- on/off of my pool pumps (S_LIGHT)
- on/off of lights around the pool (S_LIGHT)
- thermostat function for heaters (S_HVAC)
- measuring pressure on pump (S_BARO)
- measuring consumed power on pump (S_POWER)
All this are using the same sensor ID and getting own child IDs. When they now are brought in to openhab they appear as single sensors
Is there a possibility to get an automatic merge for thes combined sensors?
And what do you think about the idea.
Or is there already a solution that exist that I am not aware aboutexample from paper UI
with openhab poolcontrol view
@Denke
If I understand correctly, you are suggesting to combine different sensor types in one thing.
IMHO this would jeopardize the concept of the binding. The binding provides one thing per message type (see https://www.mysensors.org/download/serial_api_15). the thing has one channel per supported sub type.
I also do not see the advantage of combining different sensor/message types in one thing as you need one item per channel anyhow.
=> this would not reduce the number of items needed.Grouping the items in the site map - as you already did - is the best way here.
Does anybody see this differently?
-
@Denke
If I understand correctly, you are suggesting to combine different sensor types in one thing.
IMHO this would jeopardize the concept of the binding. The binding provides one thing per message type (see https://www.mysensors.org/download/serial_api_15). the thing has one channel per supported sub type.
I also do not see the advantage of combining different sensor/message types in one thing as you need one item per channel anyhow.
=> this would not reduce the number of items needed.Grouping the items in the site map - as you already did - is the best way here.
Does anybody see this differently?
@meju25 I saw this from a management perspective.
I have one device, my pool controller, that has multiple sensors and also channels per sensor just as HVAC that has a sum of channels. In my case i implemented a number of sensors in different types of channels "S_HVAC, S_LIGHT,...." what i see that it gets messy when you try to see if the channels are active or the pool control is active it has multiple sensors.So maybe a suggestion is to maybe implement this in the mysensors instead of in the openhab binding.
In that case i would like to add something that allows me to tell what channels are in a "sensor" by combining differnt channels and sensor types.I don't know if i got my message through.
But all this is mainly for management of my devices so that this gets less messy
-
-
Hi
Is there anybody that have had a problem with the S_BARO and the V_PRESSURE channel?I try to send a value on this channel as 1.2 I can see that the serial gateway receives it
23:10:51.808 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;0;3;0;9;read: 163-163-0 s=10,c=1,t=4,pt=7,l=5,sg=0:1.2
I set up the channel as i have done for alot of other channels through the paper ui. where i link the channel to an item.
The item file looks like this
String Pool_Pressure "Pressure [%s]" <pressure> (gPool)the sitemap file looks like this
Text item=Pool_Pressureresult is this
The field never gets updated.
any suggestions? -
Hi
Is there anybody that have had a problem with the S_BARO and the V_PRESSURE channel?I try to send a value on this channel as 1.2 I can see that the serial gateway receives it
23:10:51.808 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;0;3;0;9;read: 163-163-0 s=10,c=1,t=4,pt=7,l=5,sg=0:1.2
I set up the channel as i have done for alot of other channels through the paper ui. where i link the channel to an item.
The item file looks like this
String Pool_Pressure "Pressure [%s]" <pressure> (gPool)the sitemap file looks like this
Text item=Pool_Pressureresult is this
The field never gets updated.
any suggestions? -
@Denke : You're right, the pressure channel was missing in the thing definition. This is fixed in the current version!
@dakky : Which gateway type keeps disconnecting and why? I've a serial and ethernet gateway running side by side in OH2 and both didn't get disconnected so far. The hardest part is to recognize if the connection gets down.
-
@Denke : You're right, the pressure channel was missing in the thing definition. This is fixed in the current version!
@dakky : Which gateway type keeps disconnecting and why? I've a serial and ethernet gateway running side by side in OH2 and both didn't get disconnected so far. The hardest part is to recognize if the connection gets down.
Hi @TimO . Are you having both gateways connected to same the OH simultaneously?
Any troubles with that? I imagine you should have different radio channels for each gateway, right? like two separate sensors networks. -
Hi @TimO . Are you having both gateways connected to same the OH simultaneously?
Any troubles with that? I imagine you should have different radio channels for each gateway, right? like two separate sensors networks.Hi @gonzalonal !
Only the ethernet gateway has an attached radio.
Here is my current (MySensors) setup:
Bridge mysensors:bridge-eth:MySGW [ ipAddress="192.168.2.99", tcpPort=5003, sendDelay=100, skipStartupCheck=true ] { humidity bathHum01 [ nodeId="101", childId="0" ] temperature bathTemp01 [ nodeId="101", childId="1" ] humidity bathBat01 [ nodeId="101", childId="255" ] humidity bedHum01 [ nodeId="103", childId="2" ] temperature bedTemp01 [ nodeId="103", childId="1" ] humidity bedBat01 [ nodeId="103", childId="255" ] humidity workHum01 [ nodeId="104", childId="2" ] temperature workTemp01 [ nodeId="104", childId="1" ] humidity workBat01 [ nodeId="104", childId="255" ] humidity kitchenHum01 [ nodeId="105", childId="2" ] temperature kitchenTemp01 [ nodeId="105", childId="1" ] humidity kitchenBat01 [ nodeId="105", childId="255" ] humidity childHum01 [ nodeId="107", childId="3" ] temperature childTemp01 [ nodeId="107", childId="4" ] light childLight01 [ nodeId="107", childId="0" ] light childLight02 [ nodeId="107", childId="1" ] light childLight03 [ nodeId="107", childId="2" ] humidity guestHum01 [ nodeId="106", childId="0" ] temperature guestTemp01 [ nodeId="106", childId="1" ] light guestPresence01 [ nodeId="106", childId="3" ] light livingLight01 [ nodeId="106", childId="4" ] light livingLight02 [ nodeId="106", childId="5" ] light livingLight03 [ nodeId="106", childId="6" ] light livingLight04 [ nodeId="106", childId="7" ] light corridorLight03 [ nodeId="106", childId="8" ] light livingLight06 [ nodeId="106", childId="9" ] humidity livingHum01 [ nodeId="108", childId="2" ] temperature livingTemp01 [ nodeId="108", childId="1" ] humidity livingBat01 [ nodeId="108", childId="255" ] humidity gardenHum01 [ nodeId="110", childId="2" ] temperature gardenTemp01 [ nodeId="110", childId="1" ] humidity gardenBat01 [ nodeId="110", childId="255" ] motion gardenMotion01 [ nodeId="110", childId="3" ] } Bridge mysensors:bridge-ser:MySGWKeller [ serialPort="/dev/ttyUSB0", sendDelay=100, skipStartupCheck=true ] { cover kitchenShutter02 [ nodeId="0", childId="0" ] cover kitchenShutter03 [ nodeId="0", childId="1" ] cover livingShutter01 [ nodeId="0", childId="2" ] cover livingShutter02 [ nodeId="0", childId="3" ] cover kitchenShutter01 [ nodeId="0", childId="4" ] light corridorLight01 [ nodeId="0", childId="5" ] light corridorLight02 [ nodeId="0", childId="6" ] power corridorLight01watt [ nodeId="0", childId="7" ] } -
@Denke : You're right, the pressure channel was missing in the thing definition. This is fixed in the current version!
@dakky : Which gateway type keeps disconnecting and why? I've a serial and ethernet gateway running side by side in OH2 and both didn't get disconnected so far. The hardest part is to recognize if the connection gets down.
I'm using a ethernet gateway.
the problem is: if the sensors gateway gets restarted/disconnected/updated/whatever the binding does not reconnect. The only way to fix that, is to restart openhab in order to force the binding to connect again.
Detecting an disconnect is really that hard? in the worst case, what about simply reconnecting timebased? not as cute as only reconnect when nessecary but a dirty quickfix. -
Hi @gonzalonal !
Only the ethernet gateway has an attached radio.
Here is my current (MySensors) setup:
Bridge mysensors:bridge-eth:MySGW [ ipAddress="192.168.2.99", tcpPort=5003, sendDelay=100, skipStartupCheck=true ] { humidity bathHum01 [ nodeId="101", childId="0" ] temperature bathTemp01 [ nodeId="101", childId="1" ] humidity bathBat01 [ nodeId="101", childId="255" ] humidity bedHum01 [ nodeId="103", childId="2" ] temperature bedTemp01 [ nodeId="103", childId="1" ] humidity bedBat01 [ nodeId="103", childId="255" ] humidity workHum01 [ nodeId="104", childId="2" ] temperature workTemp01 [ nodeId="104", childId="1" ] humidity workBat01 [ nodeId="104", childId="255" ] humidity kitchenHum01 [ nodeId="105", childId="2" ] temperature kitchenTemp01 [ nodeId="105", childId="1" ] humidity kitchenBat01 [ nodeId="105", childId="255" ] humidity childHum01 [ nodeId="107", childId="3" ] temperature childTemp01 [ nodeId="107", childId="4" ] light childLight01 [ nodeId="107", childId="0" ] light childLight02 [ nodeId="107", childId="1" ] light childLight03 [ nodeId="107", childId="2" ] humidity guestHum01 [ nodeId="106", childId="0" ] temperature guestTemp01 [ nodeId="106", childId="1" ] light guestPresence01 [ nodeId="106", childId="3" ] light livingLight01 [ nodeId="106", childId="4" ] light livingLight02 [ nodeId="106", childId="5" ] light livingLight03 [ nodeId="106", childId="6" ] light livingLight04 [ nodeId="106", childId="7" ] light corridorLight03 [ nodeId="106", childId="8" ] light livingLight06 [ nodeId="106", childId="9" ] humidity livingHum01 [ nodeId="108", childId="2" ] temperature livingTemp01 [ nodeId="108", childId="1" ] humidity livingBat01 [ nodeId="108", childId="255" ] humidity gardenHum01 [ nodeId="110", childId="2" ] temperature gardenTemp01 [ nodeId="110", childId="1" ] humidity gardenBat01 [ nodeId="110", childId="255" ] motion gardenMotion01 [ nodeId="110", childId="3" ] } Bridge mysensors:bridge-ser:MySGWKeller [ serialPort="/dev/ttyUSB0", sendDelay=100, skipStartupCheck=true ] { cover kitchenShutter02 [ nodeId="0", childId="0" ] cover kitchenShutter03 [ nodeId="0", childId="1" ] cover livingShutter01 [ nodeId="0", childId="2" ] cover livingShutter02 [ nodeId="0", childId="3" ] cover kitchenShutter01 [ nodeId="0", childId="4" ] light corridorLight01 [ nodeId="0", childId="5" ] light corridorLight02 [ nodeId="0", childId="6" ] power corridorLight01watt [ nodeId="0", childId="7" ] }Thanks @TimO. Now I get it.
What do you think about having two gateways, one with NRF radio and the other one with RFM69 radio?Will the binding support both gateways simultaneusly with no issues?
Another question..Will you support HearbeatRequest for the development branch?
Thanks, regards.
-
Hello againg.
I have updated my OH2 to latest nightbuild from cloudbees, and also updated to lastest realease of OH2 MyS Binding.
Now, I am facing an issue, that everytime that OH2 starts, it sends out all the items status to its respective node. This is causing, for example, to open my gates, or lowering my rollershutters, even disabling/enabling my alarm system. So I have shutdown OH2 for time being.
Have anyone faced this behavior before?
This is some of the log:
15:41:40.241 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing 'mysensors:bridge-ser:gateway' takes more than 5000ms. 15:41:40.272 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.295 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.322 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.335 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.348 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.362 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.375 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.388 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.402 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.545 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'Home.items' 15:41:40.671 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.685 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.697 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.710 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.724 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.738 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.755 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.768 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.783 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.806 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;14;Gateway startup complete. 15:41:40.811 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.856 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.871 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.885 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.898 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.914 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.928 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.941 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:41.029 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 2;3;1;0;0; 15:41:41.110 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:41.288 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;253;1;0;2; 15:41:41.546 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;6;1;0;2; 15:41:41.799 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;252;1;0;24;REFRESH 15:41:42.052 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;254;1;0;2; 15:41:42.307 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;254;1;0;2; 15:41:42.562 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;3;1;0;2; 15:41:42.817 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;253;1;0;2; 15:41:43.073 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 2;252;1;0;24;REFRESHI would really appreciate your help.
-
Hello againg.
I have updated my OH2 to latest nightbuild from cloudbees, and also updated to lastest realease of OH2 MyS Binding.
Now, I am facing an issue, that everytime that OH2 starts, it sends out all the items status to its respective node. This is causing, for example, to open my gates, or lowering my rollershutters, even disabling/enabling my alarm system. So I have shutdown OH2 for time being.
Have anyone faced this behavior before?
This is some of the log:
15:41:40.241 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing 'mysensors:bridge-ser:gateway' takes more than 5000ms. 15:41:40.272 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.295 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.322 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.335 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.348 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.362 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.375 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.388 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.402 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.545 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'Home.items' 15:41:40.671 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.685 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.697 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.710 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.724 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.738 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.755 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.768 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.783 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.806 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;14;Gateway startup complete. 15:41:40.811 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.856 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.871 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.885 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.898 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.914 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.928 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:40.941 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:41.029 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 2;3;1;0;0; 15:41:41.110 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleCommand called 15:41:41.288 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;253;1;0;2; 15:41:41.546 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;6;1;0;2; 15:41:41.799 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;252;1;0;24;REFRESH 15:41:42.052 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;254;1;0;2; 15:41:42.307 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;254;1;0;2; 15:41:42.562 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 3;3;1;0;2; 15:41:42.817 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 1;253;1;0;2; 15:41:43.073 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 2;252;1;0;24;REFRESHI would really appreciate your help.
@gonzalonal I have no idea why this should happen. The binding isn't that smart to do something like that. I've done a complete fresh installation on 21.06. with the nightly build from cloudbees and don't see this issue.
@dakky Do you see disconnection messages in the log? The binding already tries to detect a disconnect and tries to reestablish the connection when an ethernet gateway is used. Currently the time within a reconnect would be successful is very small due to sleep limitations of threads in OH2 bindings.