Dim
July 11, 2017, 2:51pm
8
(yet) another victim of:
opened 03:23PM - 19 Jan 17 UTC
closed 09:14AM - 12 Aug 17 UTC
bug
The relevant thread on the forums is here:
https://community.openhab.org/t/heā¦ lp-im-ready-to-give-up/20006/93
The issue particularly impacts 1.9 bindings like Weather, MQTT, and HTTP where there can be repeated copies of one or more setting type (e.g. more than one broker config for MQTT, more than one weather location in Weather, more than one URL to cache in HTTP).
If, for example, a user decided they no longer need to poll a certain URL with the HTTP binding and remove it from their conf/services/http.cfg file, that parameter does not get removed from the corresponding userdata/config/org/openhab/http.config.
Even upon a reboot, the removed parameters persist in the userdata/config version.
As a user I expect updates to the services/binding.cfg file to apply, including additions, modifications, and removals.
If this is the wrong repo (e.g. this is really an ESH problem) let me know and I'll repost it there.
Thanks
stop OH2, delete /var/lib/openhab2/config/org/openhab/mqtt.config and start OH2 again/etc/openhab2/services/mqtt.cfg corrected and in place)
Root cause: You configured in the past a connection with the name broker. This has been kept as a ghost config in OH2 and it is preventing your MQTT binding from working properly.
It happened to me also
@Rob_Pope I had a similar problem in the pastā¦ It was due to OpenHab 2 loading up the default mqtt.cfg config file (with the sample <broker> name)ā¦ it was my mistake since I removed the comments from the lines without adjusting the broker nameā¦ After I fixed the mistake, the <broker> info still remained (as a second broker) in OH2 āinternal databaseā (I donāt know how to call it :)) and was causing errors because all other parameters for <broker> were null.
Try to check with the Karaf Console ā¦
2 Likes
