# Title: ebusd (v0.1.0) on Gladys OS / Raspberry Pi 5: « ebusd does not respond to 192.168.1.13:8888 (element not found) » although ebusd is reachable **URL:** \ **Category:** Configuration\ **Tags:** integration-externe\ **Created:** [November 13, 2026, 6:19pm UTC](https://community.gladysassistant.com/t/titre-ebusd-v0-1-0-sur-gladys-os-raspberry-pi-5-ebusd-ne-repond-pas-a-192-168-1-13-8888-element-not-found-alors-qu-ebusd-est-joignable/11569 "2026-11-13T18:19:28Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![XDECO](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xdeco/32/22996_2.png) [@XDECO](https://community.gladysassistant.com/u/XDECO)\ **Post date:** [November 13, 2026, 6:19pm UTC](https://community.gladysassistant.com/t/titre-ebusd-v0-1-0-sur-gladys-os-raspberry-pi-5-ebusd-ne-repond-pas-a-192-168-1-13-8888-element-not-found-alors-qu-ebusd-est-joignable/11569/1 "2026-11-13T18:19:28Z")
Hello, I’m trying the external integration **ebusd** by @Will_71 (`ghcr.io/william-de71/gladys-ebusd:0.1.0`) and the test fails even though everything seems correct on my end. Can you tell me if the problem comes from the integration? **Environment** - Gladys Assistant **5.3.2** on **Gladys OS** (Raspberry Pi 5, Raspberry Pi OS Trixie 64-bit, flashed with Raspberry Pi Imager). Containers: `gladys`, `watchtower`, `ebusd`, `gladys-ext-william-de71-gladys-ebusd`. - **ebusd** `john30/ebusd` 26.1.26.1 in Docker on the same Pi (192.168.1.13): `docker run -d --name=ebusd --restart=unless-stopped -p 8888:8888 john30/ebusd --scanconfig -d ens:192.168.1.14:9999` - **Adapter** : eBUS Adapter Stick C6 (ESP32-C6), firmware 20261109, on Wi-Fi (192.168.1.14), enhanced protocol over TCP. Adapter Status page: “ebusd connected: yes”, “eBUS signal: no signal” (normal, see below). ![2-adaptateur-page-status](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/4/2/423059f4311ef70e62242d8564edfc2e24a96e4f.png) Adapter settings (Enhanced protocol, TCP): ![3-adaptateur-protocole-enhanced-tcp_1](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/7/8/785259ef80cff89a571e1d406ff9981046c72a08.png) - **Boiler** : Vaillant, **not yet connected** (I’m preparing the installation before connecting it). The eBUS signal is therefore “no signal” for now. **Integration Configuration** Ebusd address: `192.168.1.13` (without `http://`), port `8888`, empty username and secret, “Allow modifications” unchecked. The configuration saves without any issues. **What I Observe** The test displays `ebusd does not respond to 192.168.1.13:8888 (element not found)` and the badge remains on “Disconnected”: ![Capture d’écran 2026-11-13 à 18.16.53](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/5/85ccdd8301627997032c107984101b6068b9ca3e.jpeg) A few minutes earlier, with the same configuration, another message appeared: “ebusd responds but hears nothing on the eBUS: check the adapter and its wiring”. No errors in `docker logs gladys-ext-william-de71-gladys-ebusd` (only `[gladys-sdk] connected to Gladys`). **What Shows That ebusd Is Reachable and Working** - `docker exec ebusd ebusctl info`: ```auto version: ebusd 26.1.26.1 device: 192.168.1.14:9999, TCP, enhanced, firmware 1.1[6b09].1[6b09] signal: no signal reconnects: 0 masters: 1 messages: 11 address 31: master #8, ebusd address 36: slave #8, ebusd ``` - `docker exec ebusd ebusctl find`: ```auto Broadcast Datetime = no data stored Broadcast Error = no data stored Broadcast Id = no data stored Broadcast IdAnswer = no data stored Broadcast Signoflife = no data stored Memory Eeprom = no data stored Memory Ram = no data stored ``` Ebusd responds correctly and only knows its 7 internal messages, with no Vaillant devices, since the boiler is not connected. - `nc -vz 192.168.1.13 8888` from the Pi: succeeded. - From **inside the integration container** (`net.connect` under Node): `172.30.0.1:8888` OK and `192.168.1.13:8888` OK. - ebusd has been running for several hours without reconnection. **My Hypothesis** `element not found` seems to be a response from ebusd to a command targeting a missing element. I reproduced it manually: ```auto docker exec ebusd ebusctl find -c bai ERR: element not found ``` (`bai` is the Vaillant boiler circuit, which is absent in my case since it is not connected.) However, a simple `ebusctl find` works and does not return this error. The integration may treat this response as a failure (“ebusd is not responding”) when in fact ebusd is responding and simply indicating that the element does not exist yet. **My questions** 1. Is it this response (`ERR: element not found`, for example when searching for a circuit like `bai`) that the integration receives? In this case, can it be treated as “no device found” rather than a failure when the bus is empty? 2. Does the boiler need to be connected and detected by ebusd for the test to pass? 3. Is there a way to get more detailed logs in the integration container? I can provide additional logs or screenshots. Thanks in advance! ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [November 13, 2026, 7:19pm UTC](https://community.gladysassistant.com/t/titre-ebusd-v0-1-0-sur-gladys-os-raspberry-pi-5-ebusd-ne-repond-pas-a-192-168-1-13-8888-element-not-found-alors-qu-ebusd-est-joignable/11569/2 "2026-11-13T19:19:04Z")
I’m trying to look into it as soon as possible. I’ll keep you posted. ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [November 13, 2026, 9:54pm UTC](https://community.gladysassistant.com/t/titre-ebusd-v0-1-0-sur-gladys-os-raspberry-pi-5-ebusd-ne-repond-pas-a-192-168-1-13-8888-element-not-found-alors-qu-ebusd-est-joignable/11569/3 "2026-11-13T21:54:13Z")
Thanks for this very complete feedback, your diagnosis was correct: the problem came from the integration, not your installation. Here’s what was happening. When no device is yet present on the eBUS, ebusd 26.1 responds ERR: element not found to the find -d command (the list of messages that already have a value). This wasn’t coming from a search on bai. The integration took this response as a failure and displayed « ebusd is not responding ». I reproduced your exact situation with the official ebusd 26.1 image, with no devices on the bus. To answer your questions: 1. Yes, it was indeed this error. The next version (0.2.0) considers this response as an empty bus, and no longer as an error. 2. No, the boiler does not need to be connected for the connection to work. As long as it isn’t, the status will indicate « ebusd responds but hears nothing on the eBUS ». This is normal, since the adapter is in « no signal » mode. This is the message you saw a few minutes earlier. 3. For the logs, two new features: - The Logs tab on the integration page now indicates the connection to ebusd, the connection loss with the reason and the command involved, and what each search found (version, signal, number of messages, devices). - A new setting, Detailed Log, in the « Troubleshooting » section, also writes each command sent to ebusd and its response. The secret is never written. Enable it to study a problem, then disable it. As soon as the new version is available, just update the integration. When your boiler is connected, if a device or value is missing, enable detailed logging and post the lines, along with the ebusctl info response. Thanks again for testing! ---
**Author:** ![XDECO](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xdeco/32/22996_2.png) [@XDECO](https://community.gladysassistant.com/u/XDECO)\ **Post date:** [November 13, 2026, 10:21pm UTC](https://community.gladysassistant.com/t/titre-ebusd-v0-1-0-sur-gladys-os-raspberry-pi-5-ebusd-ne-repond-pas-a-192-168-1-13-8888-element-not-found-alors-qu-ebusd-est-joignable/11569/4 "2026-11-13T22:21:56Z")
@Will_71 Thanks for the quick response 👋 it’s working now. Here are the screenshots As soon as I connect the boiler, I’ll give you feedback ```auto [2026-11-13T22:12:14.594Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80) [2026-11-13T22:12:14.614Z] [INFO] ebusd: connected at 192.168.1.13:8888 [2026-11-13T22:12:14.615Z] [INFO] ebusd 26.1.26.1: signal none, 9 messages defined, 0 with data, 0 devices [2026-11-13T22:12:26.056Z] [INFO] ebusd 26.1.26.1: signal none, 9 messages defined, 0 with data, 0 devices [2026-11-13T22:12:41.138Z] [INFO] ebusd 26.1.26.1: signal none, 9 messages defined, 0 with data, 0 devices [2026-11-13T22:13:12.924Z] [WARN] [gladys-sdk] connection to Gladys lost (close code 1006) [2026-11-13T22:13:12.924Z] [WARN] [gladys-sdk] not connected to Gladys (ws://172.30.0.1:80), retrying in 1000 ms (attempt 1) [2026-11-13T22:13:13.607Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80) [2026-11-13T22:13:13.683Z] [INFO] ebusd: connected at 192.168.1.13:8888 [2026-11-13T22:13:13.683Z] [INFO] ebusd 26.1.26.1: signal none, 9 messages defined, 0 with data, 0 devices [2026-11-13T22:13:44.161Z] [INFO] ebusd 26.1.26.1: signal none, 9 messages defined, 0 with data, 0 devices ``` ![Screenshot 2026-11-13 at 23.19.33](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/3/835add1184012001447872f90a17440dc3c993c2.jpeg) ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [November 13, 2026, 11:01pm UTC](https://community.gladysassistant.com/t/titre-ebusd-v0-1-0-sur-gladys-os-raspberry-pi-5-ebusd-ne-repond-pas-a-192-168-1-13-8888-element-not-found-alors-qu-ebusd-est-joignable/11569/5 "2026-11-13T23:01:45Z")
ok keep me posted