I’m running the MQTT 2.4 binding from latest official version.
I coded a python script on raspberry pi that emulates a device via the homie 3.0 protocol. This worked fine when I have set up everything.
However, after a reboot of the openhabian system, the MQTT binding reports all Items as UNDEF.
Whatever I do, I can’t get these items out of that state. What I tried is:
I forced my raspberry to resend all messages in order to compensate some lost (not persisted values) in the MQTT broker
I dropped the MQTT broker Thing and re-added it
I forced an update on the Items by renaming them and re-assigning them to the channel
I re-added the raspberry Thing
The only mitigation that worked up to now was uninstalling the MQTT binding and re-installing it.
After I got it working again, the next reboot made this issue re-appear again. So it is consistently reproducible.
My environment:
Things created in PaperUI
Openhabian on raspberry pi, latest official release
I’m aware of the thread from rlkoshak (MQTT 2.5 Binding Strange Behavior: Item goes ON then immediately to UNDEF). I tried to create a rule that sets a valid value to the items via sendCommand, but to no avail. The read-only items are not refreshed in OH if the raspberry sends new values. The settable items lead to the following log lines:
2019-02-28 22:43:56.061 [ome.event.ItemCommandEvent] - Item 'I_KG_Heizraum_Zirkulationspumpe' received command ON
2019-02-28 22:43:56.083 [hingStatusInfoChangedEvent] - 'mqtt:homie300:embedded-mqtt-broker:heatingpi' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): No connection or readOnly channel!
2019-02-28 22:44:45.164 [hingStatusInfoChangedEvent] - 'mqtt:homie300:embedded-mqtt-broker:heatingpi' changed from OFFLINE (COMMUNICATION_ERROR): No connection or readOnly channel! to ONLINE
I sense, there must be a setting that is created by PaperUI when the binding is installed, which is not persisted to disk and then lost after reboot.
Can you tell me what I can do (automatedly) in order to get Items out from an UNDEF state?
I now switched to the latest testing version (should be 2.5m1), but the result is the same. After a reboot, messages regarding my items look like:
2019-03-02 17:42:15.892 [temChannelLinkRemovedEvent] - Link 'I_KG_Heizraum_LueftungTempAuslassluft => mqtt:homie300:embedded-mqtt-broker:heatingpi:ventilation#outlettemp' has been removed.
2019-03-02 17:44:14.825 [.ItemChannelLinkAddedEvent] - Link 'I_KG_Heizraum_LueftungTempAuslassluft-mqtt:homie300:embedded-mqtt-broker:heatingpi:ventilation#outlettemp' has been added.
2019-03-02 17:44:28.006 [hingStatusInfoChangedEvent] - 'mqtt:homie300:embedded-mqtt-broker:heatingpi' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2019-03-02 17:44:39.975 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '127.0.0.1' with clientid embedded-mqtt-broker and file store '/var/lib/openhab2/mqtt/127.0.0.1'
2019-03-02 17:44:40.177 [WARN ] [mqtt.internal.MqttPersistenceService] - mqtt-persistence:broker
2019-03-02 17:44:40.182 [WARN ] [mqtt.internal.MqttPersistenceService] - mqtt-persistence:topic
2019-03-02 17:44:40.188 [WARN ] [mqtt.internal.MqttPersistenceService] - mqtt-persistence:message
2019-03-02 17:44:40.500 [WARN ] [moquette.spi.impl.SessionsRepository] - Session does not exist. CId=embedded-mqtt-broker
2019-03-02 17:44:40.583 [WARN ] [moquette.spi.impl.SessionsRepository] - Session does not exist. CId=embedded-mqtt-broker
2019-03-02 17:44:42.599 [hingStatusInfoChangedEvent] - 'mqtt:systemBroker:embedded-mqtt-broker' changed from UNINITIALIZED to INITIALIZING
2019-03-02 17:44:42.630 [hingStatusInfoChangedEvent] - 'mqtt:systemBroker:embedded-mqtt-broker' changed from INITIALIZING to ONLINE
2019-03-02 17:44:42.728 [hingStatusInfoChangedEvent] - 'mqtt:homie300:embedded-mqtt-broker:heatingpi' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2019-03-02 17:44:43.262 [hingStatusInfoChangedEvent] - 'mqtt:homie300:embedded-mqtt-broker:heatingpi' changed from INITIALIZING to OFFLINE (COMMUNICATION_ERROR): java.lang.Exception: Did not receive mandatory topic value: homie/heatingpi/$homie
2019-03-02 17:44:43.373 [vent.ItemStateChangedEvent] - I_KG_Heizraum_LueftungTempAuslassluft changed from NULL to UNDEF
After this, I restarted my raspberrypi (heatingpi) in order to force an update of all homie messages on the MQTT broker, but the only reaction within OpenHAB is:
2019-03-02 17:46:06.856 [WARN ] [moquette.spi.impl.SessionsRepository] - Session does not exist. CId=Homie-heatingpi
2019-03-02 17:46:06.862 [WARN ] [moquette.spi.impl.SessionsRepository] - Session does not exist. CId=Homie-heatingpi
==> /var/log/openhab2/events.log <==
2019-03-02 17:46:07.022 [hingStatusInfoChangedEvent] - 'mqtt:homie300:embedded-mqtt-broker:heatingpi' changed from OFFLINE (COMMUNICATION_ERROR): java.lang.Exception: Did not receive mandatory topic value: homie/heatingpi/$homie to ONLINE (CONFIGURATION_PENDING)
2019-03-02 17:46:07.126 [hingStatusInfoChangedEvent] - 'mqtt:homie300:embedded-mqtt-broker:heatingpi' changed from ONLINE (CONFIGURATION_PENDING) to ONLINE
To me, it looks like the binding recognizes that the device is back again, but it does not “heal” the state of the items, although my device specifically reports some dummy state changes for each of the items at startup.
How can I workaround this issue? Do I have to use MQTT persistence, or is there any other way? Or is it a bug in the code in the end?
Thanks for your help!
Regards,
stedon81
P.S.: With OH2.5, there are some new errors in the startup sequence. I don’t think, that they are related to this issue, but I’d like to post them for the sake of completeness:
2019-03-02 17:43:50.764 [ERROR] [org.eclipse.smarthome.core ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(54)] : doFindMethod: Suitable but non-accessible method found in class org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl
2019-03-02 17:43:50.786 [ERROR] [org.eclipse.smarthome.core ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(54)] : findMethod: Suitable but non-accessible method setScheduler found in class org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl, subclass of org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl
2019-03-02 17:43:50.790 [ERROR] [org.eclipse.smarthome.core ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(54)] : bind method [setScheduler] not found; Component will fail
2019-03-02 17:43:50.793 [ERROR] [org.eclipse.smarthome.core ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(54)] : bind method [setScheduler] not found
2019-03-02 17:43:50.797 [ERROR] [org.eclipse.smarthome.core ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(54)] : doFindMethod: Suitable but non-accessible method found in class org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl
2019-03-02 17:43:50.800 [ERROR] [org.eclipse.smarthome.core ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(54)] : findMethod: Suitable but non-accessible method unsetScheduler found in class org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl, subclass of org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl
2019-03-02 17:43:50.802 [ERROR] [org.eclipse.smarthome.core ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(54)] : unbind method [unsetScheduler] not found; Component will fail
2019-03-02 17:43:50.805 [ERROR] [org.eclipse.smarthome.core ] - bundle org.eclipse.smarthome.core:0.11.0.oh250M1 (102)[org.eclipse.smarthome.core.internal.scheduler.PeriodicSchedulerImpl(54)] : unbind method [unsetScheduler] not found
good question - is it? If so, my issue would be somewhere in the embedded broker (i.e. the broker is not persisting retained messages).
From raspberry’s side, I’m using an own modification of a 3.0-branch of homie-python. From the source code, I know that the messages are sent with the retain flag set to true.
So, do I understand it right, that:
this behavior arises from an empty broker after reboot
the binding cannot recover from UNDEF state even if the broker has valid values at a later point in time?
For 1., I might be able to find solutions (thinking to install an independent mosqitto rather than the embedded broker, which I can control myself after boot and only startup openHAB, when there are valid values in the broker - but this one sounds like a very ugly workaround)
For 2., I sense that it might be either that my expectation is wrong, or there is a issue in code.
Hi,
I now tested a bit further by installing the mosquitto broker:
After a reboot of OpenHABian device, I could confirm that all messages are still retained in the mosquitto broker and are available well before OpenHAB starts up.
I found that my Broker connection Thing originally was configured for QoS 0 and retain=False. However, a change to QoS 1 and retain=True has changed nothing: Always, if I create the broker connection and the the home300 thing anew, the items are updated, until I reboot the OpenHAB.
What else do you think could I check? I assume I’m the only one with this issue up to now (not expecting that other people never restart their devices…)?
tried to get more log output to track down this issue. Would appreciate if you could give any hints which logging helps here.
I enabled TRACE logging for org.eclipse.io.transport.mqtt and now get this output:
2019-03-04 23:43:05.440 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex homie/heatingpi/\$name
2019-03-04 23:43:05.444 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex homeassistant/.*
2019-03-04 23:43:05.447 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex homie/heatingpi/\$nodes
2019-03-04 23:43:05.451 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex homie/heatingpi/\$homie
2019-03-04 23:43:05.455 [TRACE] [ansport.mqtt.internal.ClientCallback] - Topic match for 'homie/heatingpi/$state' using regex homie/heatingpi/\$state
2019-03-04 23:43:05.459 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex [^/]*/[^/]*/\$homie
2019-03-04 23:43:05.470 [TRACE] [ansport.mqtt.internal.ClientCallback] - Received message on topic 'homie/heatingpi/$name' : heatingpi
==> /var/log/openhab2/events.log <==
2019-03-04 23:43:05.474 [hingStatusInfoChangedEvent] - 'mqtt:homie300:mosquitto:heatingpi' changed from OFFLINE (COMMUNICATION_ERROR): No connection or readOnly channel! to ONLINE (CONFIGURATION_PENDING)
==> /var/log/openhab2/openhab.log <==
2019-03-04 23:43:05.476 [TRACE] [ansport.mqtt.internal.ClientCallback] - Topic match for 'homie/heatingpi/$name' using regex homie/heatingpi/\$name
2019-03-04 23:43:05.479 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex homeassistant/.*
2019-03-04 23:43:05.483 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex homie/heatingpi/\$nodes
2019-03-04 23:43:05.487 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex homie/heatingpi/\$homie
2019-03-04 23:43:05.491 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex homie/heatingpi/\$state
2019-03-04 23:43:05.494 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex [^/]*/[^/]*/\$homie
2019-03-04 23:43:05.499 [TRACE] [ansport.mqtt.internal.ClientCallback] - Received message on topic 'homie/heatingpi/$homie' : 3.0.1
2019-03-04 23:43:05.502 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$homie' using regex homie/heatingpi/\$name
2019-03-04 23:43:05.504 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$homie' using regex homeassistant/.*
2019-03-04 23:43:05.507 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$homie' using regex homie/heatingpi/\$nodes
2019-03-04 23:43:05.509 [TRACE] [ansport.mqtt.internal.ClientCallback] - Topic match for 'homie/heatingpi/$homie' using regex homie/heatingpi/\$homie
2019-03-04 23:43:05.511 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$homie' using regex homie/heatingpi/\$state
2019-03-04 23:43:05.513 [TRACE] [ansport.mqtt.internal.ClientCallback] - Topic match for 'homie/heatingpi/$homie' using regex [^/]*/[^/]*/\$homie
2019-03-04 23:43:05.518 [TRACE] [ansport.mqtt.internal.ClientCallback] - Received message on topic 'homie/heatingpi/$nodes' : buzzer,stovepump,ventilation,heatingdisable,circpump
2019-03-04 23:43:05.520 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$nodes' using regex homie/heatingpi/\$name
2019-03-04 23:43:05.522 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$nodes' using regex homeassistant/.*
2019-03-04 23:43:05.523 [TRACE] [ansport.mqtt.internal.ClientCallback] - Topic match for 'homie/heatingpi/$nodes' using regex homie/heatingpi/\$nodes
2019-03-04 23:43:05.525 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$nodes' using regex homie/heatingpi/\$homie
2019-03-04 23:43:05.527 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$nodes' using regex homie/heatingpi/\$state
2019-03-04 23:43:05.529 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$nodes' using regex [^/]*/[^/]*/\$homie
2019-03-04 23:43:05.532 [TRACE] [ansport.mqtt.internal.ClientCallback] - Received message on topic 'homie/heatingpi/$state' : ready
2019-03-04 23:43:05.534 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex homie/heatingpi/\$name
2019-03-04 23:43:05.536 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex homeassistant/.*
2019-03-04 23:43:05.538 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex homie/heatingpi/\$nodes
2019-03-04 23:43:05.540 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex homie/heatingpi/\$homie
2019-03-04 23:43:05.542 [TRACE] [ansport.mqtt.internal.ClientCallback] - Topic match for 'homie/heatingpi/$state' using regex homie/heatingpi/\$state
2019-03-04 23:43:05.544 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$state' using regex [^/]*/[^/]*/\$homie
==> /var/log/openhab2/events.log <==
2019-03-04 23:43:05.552 [hingStatusInfoChangedEvent] - 'mqtt:homie300:mosquitto:heatingpi' changed from ONLINE (CONFIGURATION_PENDING) to ONLINE
==> /var/log/openhab2/openhab.log <==
2019-03-04 23:43:05.551 [TRACE] [ansport.mqtt.internal.ClientCallback] - Received message on topic 'homie/heatingpi/$name' : heatingpi
2019-03-04 23:43:05.554 [TRACE] [ansport.mqtt.internal.ClientCallback] - Topic match for 'homie/heatingpi/$name' using regex homie/heatingpi/\$name
2019-03-04 23:43:05.556 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex homeassistant/.*
2019-03-04 23:43:05.558 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex homie/heatingpi/\$nodes
2019-03-04 23:43:05.560 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex homie/heatingpi/\$homie
2019-03-04 23:43:05.563 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex homie/heatingpi/\$state
2019-03-04 23:43:05.565 [TRACE] [ansport.mqtt.internal.ClientCallback] - No topic match for 'homie/heatingpi/$name' using regex [^/]*/[^/]*/\$homie
From those regex checks, I suspect that the MQTT binding has not even subscribed to the node topics anymore. As you can see, beside other standard homie topics, it parses the homie/heatingpi/$nodes topic and gets “buzzer,stovepump,ventilation,heatingdisable,circpump”, however it never looks for any of the node topics, like e.g. homie/heatingpi/ventilation…
Should I file a bug report for this? So why does this work for others and not for me?
I am having the same issue here! Every time openHab is restarted (for creating a backup, I stop and start openHab every night…), my MQTT Homie device is “lost”, so the links get removed and created again, but stop working afterwards.
If I try to manually create them, it also does not work correctly. I have to remove the Homie device from openHab and restart again, then I can re-add it…
I have a dedicated mosquitto server running (that is not restarted).
MQTT messages are sent with QOS=1 and retain=True
These should be the relevant log messages:
2019-03-06 04:10:22.616 [hingStatusInfoChangedEvent] - 'mqtt:homie300:0dbafdb2:raspberrypi' changed from ONLINE to UNINITIALIZED
2019-03-06 04:10:22.622 [hingStatusInfoChangedEvent] - 'mqtt:homie300:0dbafdb2:raspberrypi' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-03-06 04:10:22.639 [hingStatusInfoChangedEvent] - 'mqtt:broker:0dbafdb2' changed from ONLINE to UNINITIALIZED
2019-03-06 04:10:22.651 [hingStatusInfoChangedEvent] - 'mqtt:broker:0dbafdb2' changed from UNINITIALIZED to OFFLINE
2019-03-06 04:10:22.661 [hingStatusInfoChangedEvent] - 'mqtt:broker:0dbafdb2' changed from OFFLINE to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-03-06 04:10:23.002 [temChannelLinkRemovedEvent] - Link 'RaspberryPiSensor_Gputemp_Temperatur => mqtt:homie300:0dbafdb2:raspberrypi:gputemp#temperature' has been removed.
2019-03-06 04:10:23.003 [temChannelLinkRemovedEvent] - Link 'RaspberryPiSensor_GasMeter_Zaehlerstand => mqtt:homie300:0dbafdb2:raspberrypi:gas-meter#reading' has been removed.
2019-03-06 04:10:23.003 [temChannelLinkRemovedEvent] - Link 'GasMeterReadingMqttGeneric_Gaszaehlerstand => mqtt:topic:f1d633b5:reading' has been removed.
2019-03-06 04:10:23.004 [temChannelLinkRemovedEvent] - Link 'RaspberryPiSensor_Gasmeter_Zaehlerstand => mqtt:homie300:0dbafdb2:raspberrypi:gasmeter#reading' has been removed.
2019-03-06 04:10:23.004 [temChannelLinkRemovedEvent] - Link 'RaspberryPiSensor_Cputemp_Temperatur => mqtt:homie300:0dbafdb2:raspberrypi:cputemp#temperature' has been removed.
2019-03-06 04:10:23.008 [temChannelLinkRemovedEvent] - Link 'GenericMQTTThing_GasGenericThing => mqtt:topic:225bb0bf:gas_generic_thing' has been removed.
2019-03-06 04:10:56.440 [.ItemChannelLinkAddedEvent] - Link 'RaspberryPiSensor_Gputemp_Temperatur-mqtt:homie300:0dbafdb2:raspberrypi:gputemp#temperature' has been added.
2019-03-06 04:10:56.442 [.ItemChannelLinkAddedEvent] - Link 'RaspberryPiSensor_GasMeter_Zaehlerstand-mqtt:homie300:0dbafdb2:raspberrypi:gas-meter#reading' has been added.
2019-03-06 04:10:56.443 [.ItemChannelLinkAddedEvent] - Link 'GasMeterReadingMqttGeneric_Gaszaehlerstand-mqtt:topic:f1d633b5:reading' has been added.
2019-03-06 04:10:56.444 [.ItemChannelLinkAddedEvent] - Link 'RaspberryPiSensor_Gasmeter_Zaehlerstand-mqtt:homie300:0dbafdb2:raspberrypi:gasmeter#reading' has been added.
2019-03-06 04:10:56.446 [.ItemChannelLinkAddedEvent] - Link 'RaspberryPiSensor_Cputemp_Temperatur-mqtt:homie300:0dbafdb2:raspberrypi:cputemp#temperature' has been added.
2019-03-06 04:10:56.456 [.ItemChannelLinkAddedEvent] - Link 'GenericMQTTThing_GasGenericThing-mqtt:topic:225bb0bf:gas_generic_thing' has been added.
2019-03-06 04:10:56.660 [hingStatusInfoChangedEvent] - 'mqtt:homie300:0dbafdb2:raspberrypi' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2019-03-06 04:11:00.444 [vent.ItemStateChangedEvent] - RaspberryPiSensor_Gputemp_Temperatur changed from NULL to 36.9 °C
2019-03-06 04:11:00.448 [vent.ItemStateChangedEvent] - RaspberryPiSensor_Gasmeter_Zaehlerstand changed from NULL to 0.15
2019-03-06 04:11:00.471 [vent.ItemStateChangedEvent] - RaspberryPiSensor_Cputemp_Temperatur changed from NULL to 36.3 °C
2019-03-06 04:11:00.763 [hingStatusInfoChangedEvent] - 'mqtt:broker:0dbafdb2' changed from UNINITIALIZED to INITIALIZING
2019-03-06 04:11:00.785 [hingStatusInfoChangedEvent] - 'mqtt:broker:0dbafdb2' changed from INITIALIZING to OFFLINE
2019-03-06 04:11:00.833 [hingStatusInfoChangedEvent] - 'mqtt:homie300:0dbafdb2:raspberrypi' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2019-03-06 04:11:00.866 [hingStatusInfoChangedEvent] - 'mqtt:broker:0dbafdb2' changed from OFFLINE to ONLINE
2019-03-06 04:11:00.868 [me.event.ThingUpdatedEvent] - Thing 'mqtt:broker:0dbafdb2' has been updated.
2019-03-06 04:11:00.887 [hingStatusInfoChangedEvent] - 'mqtt:homie300:0dbafdb2:raspberrypi' changed from INITIALIZING to ONLINE
2019-03-06 04:11:00.888 [vent.ItemStateChangedEvent] - RaspberryPiSensor_Cputemp_Temperatur changed from 36.3 °C to UNDEF
2019-03-06 04:11:00.889 [vent.ItemStateChangedEvent] - RaspberryPiSensor_Gasmeter_Zaehlerstand changed from 0.15 to UNDEF
2019-03-06 04:11:00.889 [vent.ItemStateChangedEvent] - RaspberryPiSensor_Gputemp_Temperatur changed from 36.9 °C to UNDEF
2019-03-06 04:11:20.905 [hingStatusInfoChangedEvent] - 'mqtt:homie300:0dbafdb2:raspberrypi' changed from ONLINE to OFFLINE (GONE): Device did not send heartbeat in time
2019-03-06 04:11:28.804 [hingStatusInfoChangedEvent] - 'mqtt:homie300:0dbafdb2:raspberrypi' changed from OFFLINE (GONE): Device did not send heartbeat in time to ONLINE
From my gut feeling, this issue experienced here could be related to:
Can anyone tell me how I can get these changes on my OH installation to test?
Seems to be only in a forked GIT yet, or is this contained already in the most recent SNAPSHOT?
Hooray!
You’re right, the code was already merged, but later than the 2.5M1 was released.
I today switched to the SNAPSHOT version 2.5.0~S1549-1 (Build #1549), and there it works:
After a restart of OpenHab, the binding collects all topics for all items, and the items get valid states!
Also setting of items works now (except for a smaller issue that I reported here).
