Describe the bug
Hi, im currently on raspberry pi and using OpenHab.
I have setup the tuya-mqtt in my folder /opt/tuya-mqtt.
The Pi creates a hotspot with Hostapd via WiFi.
He only gets internet access when I connect him to the Ethernet (it’s all supposed to be like that, so it’s correct).
My Tuya Bulb then connects to the hotspot and can also be pinged.
The MQTT-Broker and my LED are already setup and working. → See config file
I have downloaded mqtt-explorer to track the trafic on my broker topic and noticed that every time I connect my Raspberry pi to the Internet, a topic called “Homeassistant” and several subtopics are created.
I also noticed that my LED only works when the mentioned topics are created and the status is = online…
If the status = offline, the LED cannot be controlled or pinged.
It should be mentioned that the pi creates the mentioned topics after booting and after that the status goes online for several seconds. (LED can be controlled during this time without any problems)
The status then goes offline again and the LED cannot be controlled.
Important: Only if the Pi had Internet access while booting up it will create the topics!
Expected behavior
The problem is that I actually want to control the LED completely locally and without any internet access.
When booting up, the LED should be easily controlled.
Screenshots
Versions:
- Raspbian debian buster v. 10
- OpenHab 2.5.8
- MQTT 2.5.8
Additional context
Maybe someone can tell me if the port (1884) is correct or whether there is a specific port that is used for the Broker.
Also, it would be nice if someone could tell me what the status stands for and if it’s normal for me to need an internet connection while booting the Pi.
Thanks for your help!