OpenHAB Mysensors binding 2.4: cant get mqtt gateway online

[jimmy loyens]

@jimmy-loyens And everything logged for mysensors binding:

2019-01-22 15:39:45.027 [DEBUG] [org.openhab.binding.mysensors       ] - BundleEvent STARTING - org.openhab.binding.mysensors

2019-01-22 15:39:45.130 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=507, service.bundleid=263, service.scope=bundle, component.name=org.openhab.binding.mysensors.factory.MySensorsHandlerFactory, component.id=341} - org.openhab.binding.mysensors

2019-01-22 15:39:45.143 [DEBUG] [org.openhab.binding.mysensors       ] - BundleEvent STARTED - org.openhab.binding.mysensors

2019-01-22 15:40:38.064 [TRACE] [sors.factory.MySensorsHandlerFactory] - Creating handler for thing: mysensors:bridge-mqtt:gateway2

2019-01-22 15:40:38.090 [hingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:gateway2' changed from UNINITIALIZED to INITIALIZING

2019-01-22 15:40:38.106 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Initialization of the MySensors bridge

2019-01-22 15:40:38.158 [DEBUG] [ensors.factory.MySensorsCacheFactory] - Cache file: given_ids.cached exist.

2019-01-22 15:40:38.163 [DEBUG] [ensors.factory.MySensorsCacheFactory] - Cache (given_ids) content: [0, 11, 107]

2019-01-22 15:40:38.194 [DEBUG] [rotocol.mqtt.MySensorsMqttConnection] - Enabling connection watchdog

2019-01-22 15:40:38.197 [TRACE] [sensors.internal.event.EventRegister] - Adding listener org.openhab.binding.mysensors.internal.gateway.MySensorsGateway@16ae66 to org.openhab.binding.mysensors.internal.event.EventRegister@c0307f

2019-01-22 15:40:38.199 [TRACE] [sensors.internal.event.EventRegister] - Adding listener org.openhab.binding.mysensors.handler.MySensorsBridgeHandler@86c4a7 to org.openhab.binding.mysensors.internal.event.EventRegister@c0307f

2019-01-22 15:40:38.204 [TRACE] [nsors.handler.MySensorsBridgeHandler] - Registering MySensorsDiscoveryService for bridge 'gateway2'

2019-01-22 15:40:38.220 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=511, service.bundleid=263, service.scope=singleton} - org.openhab.binding.mysensors

2019-01-22 15:40:38.222 [ERROR] [rotocol.mqtt.MySensorsMqttConnection] - No connection to broker: mosquitto

2019-01-22 15:40:38.233 [DEBUG] [.discovery.MySensorsDiscoveryService] - Starting MySensors discovery scan

2019-01-22 15:40:38.245 [TRACE] [nternal.event.MySensorsEventRegister] - Broadcasting event org.openhab.binding.mysensors.internal.protocol.mqtt.MySensorsMqttConnection@c41f03 to: org.openhab.binding.mysensors.internal.gateway.MySensorsGateway@16ae66

2019-01-22 15:40:38.252 [TRACE] [nternal.event.MySensorsEventRegister] - Broadcasting event MySensorsNode [nodeId=0, childNumber=0, chidldList={}] to: org.openhab.binding.mysensors.internal.gateway.MySensorsGateway@16ae66

2019-01-22 15:40:38.254 [TRACE] [nternal.event.MySensorsEventRegister] - Broadcasting event MySensorsNode [nodeId=0, childNumber=0, chidldList={}] to: org.openhab.binding.mysensors.handler.MySensorsBridgeHandler@86c4a7

2019-01-22 15:40:38.256 [TRACE] [nternal.event.MySensorsEventRegister] - Broadcasting event MySensorsNode [nodeId=11, childNumber=0, chidldList={}] to: org.openhab.binding.mysensors.internal.gateway.MySensorsGateway@16ae66

2019-01-22 15:40:38.258 [TRACE] [nternal.event.MySensorsEventRegister] - Broadcasting event MySensorsNode [nodeId=11, childNumber=0, chidldList={}] to: org.openhab.binding.mysensors.handler.MySensorsBridgeHandler@86c4a7

2019-01-22 15:40:38.261 [TRACE] [nternal.event.MySensorsEventRegister] - Broadcasting event MySensorsNode [nodeId=107, childNumber=0, chidldList={}] to: org.openhab.binding.mysensors.internal.gateway.MySensorsGateway@16ae66

2019-01-22 15:40:38.263 [TRACE] [nternal.event.MySensorsEventRegister] - Broadcasting event MySensorsNode [nodeId=107, childNumber=0, chidldList={}] to: org.openhab.binding.mysensors.handler.MySensorsBridgeHandler@86c4a7

2019-01-22 15:40:38.266 [TRACE] [nternal.event.MySensorsEventRegister] - Broadcasting event org.openhab.binding.mysensors.internal.protocol.mqtt.MySensorsMqttConnection@c41f03 to: org.openhab.binding.mysensors.handler.MySensorsBridgeHandler@86c4a7

2019-01-22 15:40:38.274 [hingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:gateway2' changed from INITIALIZING to OFFLINE

2019-01-22 15:40:38.277 [DEBUG] [ensors.factory.MySensorsCacheFactory] - Writing on cache given_ids, content: [0,11,107]

2019-01-22 15:40:38.280 [TRACE] [sensors.internal.event.EventRegister] - Adding listener org.openhab.binding.mysensors.discovery.MySensorsDiscoveryService@10bffbb to org.openhab.binding.mysensors.internal.event.EventRegister@c0307f

2019-01-22 15:40:38.281 [ERROR] [rotocol.mqtt.MySensorsMqttConnection] - Failed connecting to bridge...next retry in 10 seconds (Retry No.:0)

2019-01-22 15:40:38.282 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Initialization of the MySensors bridge DONE!

It says "Failed connecting to bridge...next retry in 10 seconds (Retry No.:0)" but no retry is ever done to reconnect.

[jimmy loyens]

@jimmy-loyens I allso have no problem publishing messages to the broker from MQTT.fx.

I currently have no actuator nodes, only sensor nodes so i cant see if gateway sends message on to nodes.

If i just send message: "mygateway1-in/170/4/1/0/16 0" to a node that has a door contact on child 4, should this message show up in the serial monitor?

otherwise i can reflash the node with a relay sketch

[Guillermo Schimmel]

@jimmy-loyens Sorry man. I'm lost. we should try to contact the author of mysensors-binding.

The only advice that I have right now. What I would do: Delete all mysensors-mqtt config. Delete openhab caches (a very big json file).

Start again very simple.

[jimmy loyens]

@guillermo-schimmel Dont worry about it you tried! Do you know who that is?

Where can i find "openhab caches"

[Guillermo Schimmel]

@jimmy-loyens https://forum.mysensors.org/topic/7176/openhab-2-2-binding

he is usually at that thread. very nice guy.

Lots of info on that thread also.

[Guillermo Schimmel]

Is this ok in your installation?

openhab> bundle:list|grep My
191 │ Active   │  80 │ 2.4.0.201812040738     │ MySensors Binding

[jimmy loyens]

@guillermo-schimmel I will give it a try, thank you very much for all your efford. I think i will be needing a little brake right now so since its snowing over here i'll go sleeing with my doughter then start over fresh.:sweat_smile: :snowflake:

Thanks again

[jimmy loyens]

@guillermo-schimmel said in OpenHAB Mysensors binding 2.4: cant get mqtt gateway online:

bundle:list|grep My

openhab>  bundle:list|grep My
263 x Active   x  80 x 2.4.0.201812040738     x MySensors Binding
openhab>

yes, its active. but for some reason it looks different

[TimO]

Hey @jimmy-loyens !

I needed some time to investigate the problem and after looking into it, I've no clue why this is working for you @Guillermo-Schimmel . :flushed:

With version 2.4.0 and the changes to the mqtt binding I'm not able to connect the MySensors binding to the MQTT broker connection configured in OpenHAB. The MySensors binding uses the MQTT implementation and connection of OpenHAB, it does not connect to the broker itself.

And now the funny part: my development system works fine, so I need to find a way to debug this problem.

@Guillermo-Schimmel Did you configure broker and things in PaperUI or in textual files?

[Guillermo Schimmel]

@timo said in OpenHAB Mysensors binding 2.4: cant get mqtt gateway online:

Hey @jimmy-loyens !

I needed some time to investigate the problem and after looking into it, I've no clue why this is working for you @Guillermo-Schimmel . :flushed:

With version 2.4.0 and the changes to the mqtt binding I'm not able to connect the MySensors binding to the MQTT broker connection configured in OpenHAB. The MySensors binding uses the MQTT implementation and connection of OpenHAB, it does not connect to the broker itself.

And now the funny part: my development system works fine, so I need to find a way to debug this problem.

@Guillermo-Schimmel Did you configure broker and things in PaperUI or in textual files?

Some in files, some in Paper UI.

I think I have a mess, but don't want to touch it because it's working so nicely...

[Guillermo Schimmel]

@guillermo-schimmel @TimO

have a look

Bridge mqtt:broker:mosquittotexto [ host="localhost",
                                    port="8884",
                                    secure=false,
                                    brokername="mosquitto", 
                                    topicPublish="mysensors1-in",
                                    topicSuscribe="mysensors1-out",
                                    startupCheckEnabled=false ]
    {
    Thing mqtt:topic:miscosas {
        Channels:
            Type number : ecovacs_1_battery_level     "Ecovacs 01 Battery Level"         [ stateTopic="ecovacs/E0000693817701104736/battery_level" ]
            Type string : ecovacs_1_charge_status     "Ecovacs 01 Charge Status"         [ stateTopic="ecovacs/E0000693817701104736/charge_status" ]
            Type string : ecovacs_1_clean_status      "Ecovacs 01 Clean Status"          [ stateTopic="ecovacs/E0000693817701104736/clean_status" ]
            Type string : ecovacs_1_vacuum_status     "Ecovacs 01 Vacuum Status"         [ stateTopic="ecovacs/E0000693817701104736/vacuum_status" ]
            Type string : ecovacs_1_fan_speed         "Ecovacs 01 Fan Speed"             [ stateTopic="ecovacs/E0000693817701104736/fan_speed" ]
            Type number : ecovacs_1_main_brush        "Ecovacs 01 Main Brush"            [ stateTopic="ecovacs/E0000693817701104736/components/main_brush" ]
            Type number : ecovacs_1_side_brush        "Ecovacs 01 Side Brush"            [ stateTopic="ecovacs/E0000693817701104736/components/side_brush" ]
            Type number : ecovacs_1_filter            "Ecovacs 01 Filter"                [    stateTopic="ecovacs/E0000693817701104736/components/filter" ]
            Type number : ecovacs_1_ncommand          "Ecovacs 01 Number Command"        [ commandTopic="ecovacs/E0000693817701104736/command" ]
            Type string : porton_a_mano               "Garage Porton a Mano"             [ stateTopic="mygateway1-out/11/3/1/0/16" ]
            Type number : server_nextcloud_disk_root  "Server Nextloud Root Partition"   [ stateTopic="servers/nextcloud/disk/root" ]
            Type number : server_bluecherry_disk_root "Server Bluecherry Root Partition" [ stateTopic="servers/bluecherry/disk/root" ]
       }
}

[TimO]

@guillermo-schimmel You've mixed up attributes from the MySensors binding and the MQTT binding in the bridge definition. brokerName, topicSubscribe and so on are attributes from the MySensors binding. But this won't do any harm.

How is the MySensors gateway defined?

[Guillermo Schimmel]

@timo Mysensors gateway is defined via Paper UI:

[Guillermo Schimmel]

@timo said in OpenHAB Mysensors binding 2.4: cant get mqtt gateway online:

@guillermo-schimmel You've mixed up attributes from the MySensors binding and the MQTT binding in the bridge definition. brokerName, topicSubscribe and so on are attributes from the MySensors binding. But this won't do any harm.

Thanks, cleaned up config file:

Bridge mqtt:broker:mosquittotexto [ host="localhost",
                                    port="8884",
                                    secure=false,
                                    startupCheckEnabled=false ]
    {
    Thing mqtt:topic:miscosas {
        Channels:
            Type number : ecovacs_1_battery_level     "Ecovacs 01 Battery Level"         [ stateTopic="ecovacs/E0000693817701104736/battery_level" ]
            Type string : ecovacs_1_charge_status     "Ecovacs 01 Charge Status"         [ stateTopic="ecovacs/E0000693817701104736/charge_status" ]
            Type string : ecovacs_1_clean_status      "Ecovacs 01 Clean Status"          [ stateTopic="ecovacs/E0000693817701104736/clean_status" ]
            Type string : ecovacs_1_vacuum_status     "Ecovacs 01 Vacuum Status"         [ stateTopic="ecovacs/E0000693817701104736/vacuum_status" ]
            Type string : ecovacs_1_fan_speed         "Ecovacs 01 Fan Speed"             [ stateTopic="ecovacs/E0000693817701104736/fan_speed" ]
            Type number : ecovacs_1_main_brush        "Ecovacs 01 Main Brush"            [ stateTopic="ecovacs/E0000693817701104736/components/main_brush" ]
            Type number : ecovacs_1_side_brush        "Ecovacs 01 Side Brush"            [ stateTopic="ecovacs/E0000693817701104736/components/side_brush" ]
            Type number : ecovacs_1_filter            "Ecovacs 01 Filter"                [    stateTopic="ecovacs/E0000693817701104736/components/filter" ]
        
            Type number : server_bluecherry_disk_root "Server Bluecherry Root Partition" [ stateTopic="servers/bluecherry/disk/root" ]
       }
}

Restarted all, still all working fine.

[TimO]

@guillermo-schimmel OK, next question: how did you define the system broker named mosquitto? Because that's the one the MySensors binding seems to use. In a service (cfg) file? I've had no success defining one and maybe that's the key.

[Guillermo Schimmel]

@timo Via files. It was the old broker I was using with the 1.x mqtt binding.

[jimmy loyens]

If I can do anything to help please let me know

[MasMat]

I had a working mqtt-gw but the lastest update (using openhabian so updates every time with system) screwed up my system. I have reloaded the binding and also rebuilt the gw (Rpi) to get newest MySensors version.
Haven't had time to troubleshoot yet.
Binding behind after latest update?

[jimmy loyens]

@masmat Hi, I think @TimO is looking into it. Ethernet and serial gateway work as expected with mysensors binding. My guess it has something to do with new MQTT-binding.

[waspie]

@masmat said in OpenHAB Mysensors binding 2.4: cant get mqtt gateway online:

I had a working mqtt-gw but the lastest update (using openhabian so updates every time with system) screwed up my system. I have reloaded the binding and also rebuilt the gw (Rpi) to get newest MySensors version.
Haven't had time to troubleshoot yet.
Binding behind after latest update?

same here, updated from 2.4.0 to 2.5.0 snapshot and it died.

I was using an MQTT broker solely configured via paperui and it worked like a dream. 2.5.0 - not so much.