Hello everyone and a big thank you for this open-source home automation. I’m just starting with the installation and I already have a first issue. I followed the instructions to the letter for installing Gladys on a Raspberry Pi (downloading the image and decompressing it, copying the image to the SD card with Etcher, placing the card on the RPI).
The RPI starts correctly, an IP address is assigned to it, but unfortunately I can’t go any further and log into Gladys. The command http://gladys.local in the browser responds with:
Hum, we can’t seem to find this site.
Unable to connect to the server at www.gladys.local.
If the address is correct, here are three other things you can try:
Try again later.
Check your network connection.
If you are connected through a firewall, check that Firefox has permission to access the web.
I must have missed a step, but I can’t see it.
Thanks in advance to those who can put me on the right track for a solution.
A big thank you for your explanations.
Indeed, the RPI does have an IP address.
If I address the RPI via the browser 192.168.x.x (RPI address), I get exactly the same message.
If I access it via Putty in SSH, I access the RPI with a request for User and password but not the nice screen shown in Gladys’s presentation.
Thank you again for your answers
Hello and welcome!
Have you waited long enough? The first startup can take more than ten minutes, depending on the type of Raspberry Pi and your connection!
To check if the Gladys container is properly installed and started, could you type, via SSH with PuTTY, the command
docker logs gladys
`````bash
And let us know what it gives?
Hello and thank you for your quick response,
Here is the message received.
gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js
2021-10-09T10:31:29+0200 <info> 20210129155044-multi-user.js:23 (Object.up) Multi-user migration: 0 users found
Initialising OpenZWave 1.6.0 binary addon for Node.JS.
OpenZWave Security API is ENABLED
ZWave device db : /usr/local/etc/openzwave
User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2021-10-09T10:31:32+0200 <info> index.js:19 (Object.start) Starting example service
2021-10-09T10:31:32+0200 <info> index.js:64 (Object.start) Starting CalDAV service
2021-10-09T10:31:32+0200 <info> index.js:20 (Object.start) Starting Open Weather service
2021-10-09T10:31:32+0200 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2021-10-09T10:31:32+0200 <info> index.js:14 (Object.start) starting GoogleActions service
2021-10-09T10:31:32+0200 <info> init.js:36 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle not attached
2021-10-09T10:31:32+0200 <info> index.js:18 (Object.start) Starting TP-Link service
2021-10-09T10:31:32+0200 <info> index.js:17 (Object.start) Starting eWeLink service
2021-10-09T10:31:32+0200 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
2021-10-09T10:31:32+0200 <info> index.js:15 (Object.start) Starting Bluetooth service
2021-10-09T10:31:32+0200 <info> bluetooth.initPresenceScanner.js:18 (BluetoothManager.initPresenceScanner) Bluetooth configuration: starting presence scanner
2021-10-09T10:31:32+0200 <info> index.js:15 (Object.start) Starting Tasmota service
2021-10-09T10:31:33+0200 <info> index.js:16 (Object.start) Starting zwave service
2021-10-09T10:31:33+0200 <info> bluetooth.initPresenceScanner.js:13 (BluetoothManager.initPresenceScanner) Bluetooth configuration: stopping presence scanner
2021-10-09T10:31:33+0200 <info> bluetooth.initPresenceScanner.js:18 (BluetoothManager.initPresenceScanner) Bluetooth configuration: starting presence scanner
2021-10-09T10:31:33+0200 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2021-10-09T10:31:33+0200 <info> index.js:14 (Object.start) Starting Xiaomi service
2021-10-09T10:31:33+0200 <info> index.js:13 (Object.start) Starting usb service
2021-10-09T10:31:33+0200 <info> index.js:19 (Object.start) Starting Telegram service
2021-10-09T10:31:33+0200 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2021-10-09T10:31:33+0200 <info> index.js:16 (Object.start) Starting RTSP service
2021-10-09T10:31:33+0200 <info> index.js:18 (Object.start) Starting Philips Hue service
2021-10-09T10:31:33+0200 <info> index.js:16 (Object.start) Starting MQTT service
2021-10-09T10:31:33+0200 <info> updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes...
2021-10-09T10:31:33+0200 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.
2021-10-09T10:31:33+0200 <info> index.js:63 (Server.<anonymous>) Server listening on port 80
Hello Pierre-Gilles,
Thank you very much for your quick response.
Yesterday, I was too busy to test the solutions from « GBoulvin, » whom I thank once again.
This morning, I reconnected the RPI and waited about fifteen minutes before testing with the browser. Since the result was still the same, I entered the recommended docker command and sent the result. While waiting for a response that I did not expect so quickly, I left the RPI connected. Before replying to your message, I tried again and there the « miracle » happened, I have the expected menu. I was too rushed, I probably skipped the « wait » information
I will gently tame the box and very certainly head towards Gladys+.
Again, 1000 thanks to all of you and sorry for making you lose your time due to my lack of patience. Have a great day
Daniel
