I can not play with that anymore. I just need some switches to work 99,99% of the time.
After update stopped to work.
mqtt.fx did still connect to pi.
after my superior intervention does not anymore. I tryed to reformat sdcard all from scratch. but does not work
Do you have any configuration backups or have you cloned your SD card with entire content ? If you use SD cards it’s always good practice to have second card ready with the same system on it.
Still you seem to be able to connect to your system. Is there any hints in the openhab.log or system logs?
I mean, even if you are setting up the system from scratch, you should now what happened either to avoid it in the future or to find a quick way of getting the system up and running again.
Is your problem that only MQTT isn’t working anymore or OpenHab in general?
which broker are you using? which port?
is the broker running (use ps -A on the shell to check if it is)?
Do you get an error when starting the broker from the shell?
Did IP adress change on the PI?
Have you tried connecting to the broker by its IP adress?
Edit:
To which OpenHab version did you update your system?
login as: openhabian openhabian@192.168.1.20’s password:
Linux openhabian 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Dec 29 09:32:53 2018 from 192.168.1.2
Wi-Fi is disabled because the country is not set.
Use raspi-config to set the country before use.
2018-12-29 14:34:16,485: FireMotD: Info: No FireMotD ExportFile detected. Please generate with “sudo .\FireMotD -S”
No, we´re not a helpdesk - But we´re NOT stupid either…
This guy needs help as to where to look to provide the informations which are required. And he probably need help to explain himself.
He actually did give some information which could be usefull (perhaps)…
Update - (assume its openhab and probably to the latest 2.4)
and
mqtt…
Maybe this could help him:
Another possible help. Direct him to the log files, so we´re able to see whats going on.
Answer could be:
http://IP_OF_HIS_RPI:9001 is he´s running the tail log.
Or
/var/log/openhab2/ to look at the logfiles.
Took me just a few seconds. Hopefully, based on his very limited informations, (but obvious major frustrations), this can get him a bit futher… If not, then we´ll take it from there.
I know you think he should have search for this himself first. But if he doesn´t know how to, or even whats wrong, how the hell can a search be usefull in anyway
If you were using the mqtt 1.x binding then did the upgrade from 2.3 to 2.4 then you need to turn on legacy binding via paperUI and install the 1.x mqtt binding again.
After that I would clean the cache and reboot with these commands.