Yes MQTT works fine for Zigbee2mqtt
logs from addon:
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] mosquitto.sh: executing...
[01:35:01] INFO: Certificates found: SSL is available
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[01:35:02] INFO: Starting NGINX for authentication handling...
[01:35:02] INFO: Starting mosquitto MQTT broker...
1637454902: mosquitto version 1.6.12 starting
1637454902: |-- *** auth-plug: startup
1637454902: Config loaded from /etc/mosquitto/mosquitto.conf.
1637454902: Loading plugin: /usr/share/mosquitto/auth-plug.so
1637454902: ├── Username/password checking enabled.
1637454902: ├── TLS-PSK checking enabled.
1637454902: └── Extended authentication not enabled.
1637454902: Opening ipv4 listen socket on port 1883.
1637454902: Opening ipv6 listen socket on port 1883.
1637454902: Opening websockets listen socket on port 1884.
1637454902: Opening ipv4 listen socket on port 8883.
1637454902: Opening ipv6 listen socket on port 8883.
1637454902: Opening websockets listen socket on port 8884.
1637454902: Warning: Mosquitto should not be run as root/administrator.
1637454902: mosquitto version 1.6.12 running
1637454902: New connection from 127.0.0.1 on port 1883.
1637454902: New connection from 172.30.32.1 on port 1883.
1637454902: Socket error on client <unknown>, disconnecting.
1637454902: New client connected from 172.30.32.1 as 6NML7UUex77jxR6jHMX8mR (p2, c1, k60, u'homeassistant').
[01:35:03] INFO: Successfully send discovery information to Home Assistant.
[01:35:03] INFO: Successfully send service information to the Supervisor.
Hey Guys, I had the same problem here, and for lucky I found a hidden button…
Select the ‘password’ field and press tab, it will select a hidden button that connect into the MQTT.
Also, FWIW, hopefully it helps others. I’ve installed this on two different machines. I got MQTT setup, my resolution was large enough to see the save button for the MQTT server information. Once I did that and enable the service any of the sensors I added weren’t showing up in the UI, but did in Home Assistant.
To resolve this you could kill the Windows service manually or just restart your machine and it should be good to go after that.
I managed to get it working by creating a WMIsensor with the following code :
SELECT Present FROM Win32_PnPEntity WHERE Name='HID-compliant game controller'
The Device with the Name 'HID-compliant game controller' only appear when my controller is connected via bluetooth. The sensor turn to True when the controller is connected to my PC which trigger an automation to launch Steam in Big Picture Mode.
The custom command to launch Steam in Big Picture Mode :
Hi all… this project is great! I have it up and running with just a few sensors (to test), and it works great. However, when I run UserInterface.exe to add some more sensors, it opens up as if I have nothing configured (no MQTT setting, no connection, no sensors etc.). My configuration .json files all look fine, and the background service is running fine, but the user interface doesn’t seem to be reading these at all. Any ideas?
Thank you for this project ! It’s so powerfull… and resource efficient !
Just one question: is there please a way to get the CPU temperature as it already is for the GPU ?
Hi, When I open the HASS Workstation Service I see Unspecified Error and I can’t figure out why. I’ve tried killing the HASSWS service and restarting it on the Windows PC but that doesn’t help.
As far as I can tell I’ve configured the MQTT broker on my HomeAssistant and it is running ok.
I’m struggling to get this to work with my instance’s External IP. In short, I have an external IP and access my instance through Clodufared (HTTPS - only). What is the proper way to send messages to my MQTT broker on this external IP (https://www.home-example.com)?
You would need to check the Use TLS button and have the certs loaded into the PC. I havent used external accessible MQTT for ages, but from memory you just used the external hostname or IP address. I dont believe I used https: in the connection URL.
I assume you have your MQTT server already accessible through TLS?