New to Gladys and used to tinkering with Home Assistant, I wanted to migrate for greater simplicity. However, I’m encountering several problems following a bad network configuration that crashed my Unraid server.
My Configuration :
Hardware : Lenovo ThinkCentre M710q.
Stockage : DAS TerraMaster 4-bay (USB).
Dongles : Zigbee (on /dev/ttyACM0) and Asus BT500 Bluetooth.
Gladys : Installed via Docker on Unraid (currently in Bridge mode on port 8006 to avoid conflicts).
The problem :
After attempting to configure the Bluetooth dongle, I switched Gladys to Host network mode, which caused a complete Unraid crash (IP/port conflict) and corruption of my boot key. I had to recreate a « New Config » and delete the corrupted Docker image.
Since then, I have two major issues:
MQTT and Zigbee services : The built-in containers no longer exist. I tried a manual reinstallation via Unraid’s Apps tab, but Gladys doesn’t seem to communicate with them.
Is there a way to force Gladys to reinstall and manage these containers itself (Mosquitto/Zigbee2MQTT) to restore native operation?
How can I make sure that the new containers correctly point to my old data in /mnt/user/appdata/?
Bluetooth (Asus BT500) : My dongle is still not recognized in the Gladys interface (« No device found »). I have enabled Privileged mode and tried a USB passthrough via /dev/bus/usb, but without success.
Do you have any tips to stabilize Bluetooth on Unraid and correctly link the MQTT/Zigbee services after such a crash?
I’ll try to help you with the Docker and Gladys side, but not Unraid (I only know it by name).
Are you using docker run or docker compose?
For network mode, you absolutely need to be in host.
For the port, you can use 8420.
For the directory mapping, I’d say /mnt/user/appdata/gladysassistant:/var/lib/gladysassistant provided you of course have a gladysassistant directory in your appdata, otherwise you’ll need to adjust the path.
Do you need the zigbee2mqtt integration AND the MQTT integration?
If you only want zigbee, the zigbee2mqtt integration already manages 2 containers: zigbee2mqtt and mosquitto.
If you need to manage virtual devices and/or subscribe to topics coming from other systems, then you need to enable the MQTT integration (hope I’m being clear ).
I’m not a Docker command-line specialist since I do everything through Portainer to add/modify/remove, but you can already run a docker ps to see what’s running and a docker ps -a to see everything that exists.
A container from the integrations can be dead and you would then need to remove it with docker rm nom-container.
Okay, moving on to Bluetooth and I’ll be quicker because I don’t have it
What will you use BT for?
According to the doc, it’s only for detecting phone presence.
Hello,
So I was so fed up that I did a clean install … For Bluetooth I would like to set up a presence detection system using key fobs as explained in the
I managed to get my tweak working on the Asus BT500. The problem was a conflict with Unraid’s port 80.
Here’s the ultimate method to make everything work perfectly:
Step 1 : Install Bluetooth drivers on Unraid
Since Unraid is lightweight, you need to teach it to speak « Bluetooth ».
In Unraid, go to the Plugins tab > Install Plugin.
In the URL field, paste this address to install the un-get tool: https://raw.githubusercontent.com/ich777/un-get/master/un-get.plg and click Install.
Open Unraid’s Terminal (the >_ icon at the top right).
Type un-get update and press Enter.
Type un-get install bluez and press Enter. (This installs the drivers).
Step 2 : Turn on the server antenna
Still in the Unraid terminal, run the following command to start the Bluetooth service:
/etc/rc.d/rc.bluetooth start(Your Unraid server now recognizes your USB dongle!)
Step 3 : The « Magic » Gladys Docker configuration
Go to Unraid’s Docker tab, click the Gladys Assistant icon and choose Edit. Make exactly these changes:
Network Type : Set it to Host(required to see the radio antenna).
Clean the old config : Remove your old Port rules (e.g. 8006:80) and your old Bluetooth USB devices (e.g. --device=/dev/bus/...).
Create the DBUS bridge : Click Add another Path…
Config Type : Path
Name : DBUS
Container Path : /var/run/dbus
Host Path : /var/run/dbus
The anti-crash tweak (Most important!) : To prevent Gladys from crashing your server by using port 80 (already taken by Unraid), click Add another Path… and create this variable:
Config Type : Variable
Name : Gladys Internal Port
Key : SERVER_PORT
Value : 8006
Step 4 : Apply and Scan!
Click APPLY at the bottom to recreate the container.
Go to the Gladys interface in your browser (e.g. http://IP_OF_YOUR_SERVER:8006). Your Unraid won’t crash!
Go to Integrations > Bluetooth. The error will be gone. You can start a scan and detect your key fobs, thermometers, etc.