Tameion
November 26, 2018, 10:00am
1
Okay I is stuck…
I have had a working installation for months now but after a recent reboot in order to shift my server, and a routine update on the Linux install, the eventbus communication between OpenHAB2 and the MQTT broker ceased.
The OpenHAB2 broker itself works fine but NO action done within OpenHAB is passed out to the broker
The reason is obvious:
Which in turn leads to the following error:
Did permissions change on the MQTT subsystem?
Is it refusing to accept insecure connections now?
I have read, read and re-read all the helps I could find over the last 5 days
Anyone have any suggestions before I start posting config files and error logs?
@Tameion
Dim
November 26, 2018, 10:04am
2
can you post the contents of the following 7 files plz:
MQTT Binding related:
1) /etc/openhab2/services/mqtt.cfg
2) /var/lib/openhab2/config/org/openhab/mqtt.config
MQTT EventBus related:
3) /etc/openhab2/services/mqtt-eventbus.cfg
4) /var/lib/openhab2/config/org/mqtt-eventbus.config
MQTT Persistence related:
5) /etc/openhab2/persistence/mqtt.persist
6) /etc/openhab2/services/mqtt-persistence.cfg
Mosquitto related:
6) /etc/mosquitto/mosquitto.conf
(or stuff in your /etc/mosquitto/conf.d/)
Why MqttPersistenceService ? do you need it? that’s not the MQTT-EventBus integration.
Tameion
November 26, 2018, 10:14am
3
Okay - sorry for delay - manually typed but double checked for mistooks.
mqtt,cfg
tameion.url=tcp://10.1.1.180:1883
tameion.lwt=Offline
mqtt.config
service.pid="org.openhab.mqtt"
tameion.lwt="Offline"
tameion.url="tcp://10.1.1.180:1883"
mosquitto.conf
pid_file /var/run/mosquitto.pid
persistence true
persistence_location /var/lib/mosquitto/
log_dest file /var/log/mosquitto/mosquitto.log
include_dir /etc/mosquitto/conf.d
I don’t need persistence but I was planning on being able to query the store like a database for other not OpenHAB projects I have in the workshop that could access the broker.
I can disable while we troubleshoot ?
Tameion
November 26, 2018, 10:18am
4
This file may be of relevance here as I had to use MQTT1 to get the binding to work:
addons.cfg
remote = true
Dim
November 26, 2018, 10:19am
5
The error(s) that you are getting are because the MQTT Persistence cannot connect to the Broker to store the info based on your mqtt.persist settings.
Can you troubleshoot the OH2<->Broker connectivity by simply adding a demo Switch bound to a topic and publish a message?
Your mqtt.cfg & mosquitto.conf look goodlistener 1883 0.0.0.0 on my mosquitto.conf (but you say that the broker is working with other nodes)
If you want to use the MQTT-Event Bus integration, set your stuff in mqtt-eventbus.cfg
MQTT Persistence is used to store the state of selected Items (defined in mqtt.persist)
Dim
November 26, 2018, 10:19am
6
Tameion:
action = mqtt
take this guy out!an issue with him
Tameion
November 26, 2018, 10:26am
7
Yes… I understand the Persistence and Eventbus functionality. I was using this to ‘spy’ on events in the broker and perform actions that OpenHAB2 does not yet have the ability to do on other MQTT enabled applications… until I get around to writing my own plugins (if ever!)
FYI
mqtt-persistence.cfg
broker=tameion
mqtt.persist
Strategies {
// persist a;; items every hour and on every change
: strategy = everyChange, everyHour, restoreOnStartup
// additionally, persist all temperature and weather values every hour
home.items
Switch tv_manland “Manland Television” [ “Switchable” ] {mqtt=“<[tameion:stat/sonoff_07/POWER:state:default], >[tameion:cmnd/sonoff_05/POWER:command:*:default]” }
So I believe everything looks right — but I still can’t place my finger on the fault!
Dim
November 26, 2018, 10:28am
8
vzorglub
November 26, 2018, 10:29am
9
Tameion:
mosquitto.conf
pid_file /var/run/mosquitto.pid
persistence true
I don’t need persistence but I was planning on being able to query the store like a database for other not OpenHAB projects I have in the workshop that could access the broker.
Take it out. It will cause you more problems than it’s worth.
persistence false
1 Like
Dim
November 26, 2018, 10:33am
10
by the way: what use case can be solved using MQTT Persistence that cannot be solved using regular MQTT bound Items? (maybe an hourly update of a state of an Item?)
Tameion
November 26, 2018, 11:40am
11
Still no joy… calling it quits for tonight !
It’s 12:40 am here in NZ and I have to teach in the morning…
Thanks for the assist will try again tomorrow night.
1 Like
Tameion
November 27, 2018, 9:11am
12
Well I have come to an impasse… I have checked and compared every log file. Deleted cleared and reloaded broker, etc. No Joy.
Here’s a dump for those interested.
2018-11-27 21:58:05.802 [DEBUG] [.binding.mqtt.internal.MqttActivator] - MQTT binding has been started., component.name=org.openhab.binding.mqtt.MqttItemBinding, component.id=231} - org.openhab.binding.mqtt , service.pid=org.openhab.mqtt-eventbus, component.name=org.openhab.binding.mqtt.eventbus, component.id=233} - org.openhab.binding.mqtt
Dim
November 27, 2018, 9:39am
13
looks to me like… a classic “evil brother ” symptom: (/var/lib/openhab2/config/org/openhab/mqtt.config in your case… the evil brother of /etc/openhab2/services/mqtt.cfg
add the following line as the first line in your mqtt.cfg
pid:org.openhab.mqtt
Ref: Troubleshooting section of MQTT Binding (v1.11) Getting Started 101
Tameion
November 27, 2018, 10:55am
14
Got it - Thanks!!!
Dam that was a loooooong road to recovery. The evil twin issue sure took a lot of steps to identify, isolate and resolve. Clearing the cache after your last instruction and restarting OH did the job.
I think a big part of my problem was not being patient enough and allowing OH to do its thing before trying another fix.
I have renamed the thread to better identify it for those in similar situations. I think you did a robust job or support - clearer and more focused than most of the other threads I have read in trying to solve this situation.
Now… I’m off to repair the W.A.F. with a bit of grovelling and probably chocolate!
Again thanks heaps for your support.
1 Like
