john30 / ebusd-esp Goto Github PK

Helpful when having more adapters and no other means to distinguish them.

Hello!

I want to implement my own firmware for esp32 to transmit data from eBus to ebusd.
The reason is that I need to control some additional relay from the same esp32 board using HomeAssistant, and as I understand - recommended firmware works only as eBus communicator.

Maybe you can kindly give some hints to esp<->ebusd exchange protocol description?

I bought this D1 mini Pro with external antenna to improve the WiFi range of my ebus adapter 3:
https://www.reichelt.com/be/nl/d1-mini-pro-esp8266-cp2104-set-met-antenne-d1-mini-pro-ant-p266067.html

After flashing with the Pro firmware, I can connect to the EBUS access point and use the web interface at 192.168.4.1. But when I change the configuration to use my home WiFi access point, check & load, save & reboot, the device reboots but the configuration was not stored. The EBUS access point comes up again.

I found this closed issue, but I couldn't find any useful information.

HI John,

I noticed random crashes of ebusd-esp. So far one that I can reproduce is when I restart the wifi access point or wifi is down for any reason and then back again, ebusd-esp will not reconnect to wifi or at least it's web config page is no longer available. Could be related to esp8266/Arduino#4445 .
I'm using the latest build 20181125.

the heap size constantly decreases as shown on the web UI without any ebusd traffic

I am trying to control a Wolf CWL Excellent 400 with this setup. I am able to control the fans using EBUSD, but since I also have a controlunit attached to the EBUS, it basically resets the fan speed every 30 seconds to it's original value.

My idea is now to disconnect the controlunit from the EBUS during the time I want to control the CWL using EBUSD. Once I want the automatic program to continue, I simply reconnect the EBUS to the controlunit.

For this I would use a IRF520 connected to a GPIO of the ESP. Hence it would be great, if I would switch a GPIO through a call to the web interface of the EBUS-ESP.

Hi,
I just received my Ebus adapter v.3 with a pre-flashed Wemos D1 mini. It had a black-on-yellow 'esp3' Dymo label sticker on the ESP-12F module.

All good and fine, I could see the EBUS ssid, I connected to it, configured my home network ssid and password, rebooted, and it was nicely getting an IP address from my internal DHCP server.
Then I soldered the pinheaders on to allow it to marry it to the EBUS adapter itself.
From that moment, after inserting into the EBUS adapter and removing the Wemos from the adapter, the pre-flashed firmware was always rebooting, due to watchdog timer kicking in, bootmode (3,6).
Whatever I tried. reset, unplug/plug the usb, nothing helped. I could see the short flash every x seconds and I saw the same wdt reboot message on serial port over and over.

Then i tried to reflash using both the nodemcu flasher AND the esptool flasher, both as per instructions, using the downloaded ebus-v3-d1mini.bin file. Same effect. Reboots of the Wemos d1 mini.

I though it was maybe broken, so I decided to try something else. I quickly took an arduino blinky example from/in PlatformIO, flashed it to the board, and look, it worked fine. Nice -stupid- blinky.
I tried again putting the official firmware on it using both tools ... wdt timer kicking in again.

Then, almost desperate, I tried the 'official' Espressif flasher, downloaded from their website. And see, when flashing the same bin file as I've done about 10x before, this time it worked. It has 'properly' written the firmware file, reset the config and I see the default EBUS ssid back.

I stuck the soldered Wemos module on the EBUS Adapter, re-plugged in the usb cable and guess what, adapter orange and green led full on, blue led flashing, NO fast Wemos blue led flashing and no EBUS ssid anymore. Deja-vu feeling ...

Take it off the adapter ... try again ... luckily the EBUS ssid is back.
So i start to suspect the laptop USB power port I use for setting up. And indeed, when connecting to a USB powerbank, the Wemos d1 mini inserted IN the EBUS adapter nicely work together and I still have the EBUS ssid.

I can continue... Just lost a few hours :)

I just wrote this so it can be found (when asking our good Friend) if other people might have similar issues. And maybe so you can can update the documentation, also indicate the need to supply a more than decent amount of mA otherwise funny things can happen, requiring some unexpected tinkering. And maybe give the Espressive tool some well deserved mention, as for some reason, the other tools didn't reflash the firmware back correctly.

Cheers.

Hello,

Need help :)
I am struggling to capture if I can plug the wemos D1 mini with the esera ebus coupler through the mini USB port. If yes, which configuration should I use ?

Thanks !

to 63 chars

The README lacks flashing instructions for ESP32. I tried this to flash the Lolin32 binary to ESP32-DevKitC board:

th@slepice:~/ebusd-esp/dist$ ~/.local/bin/esptool.py --port /dev/ttyUSB0 erase_flash
esptool.py v3.1
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, Coding Scheme None
Crystal is 40MHz
MAC: 24:0a:c4:13:3e:58
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 7.3s
Hard resetting via RTS pin...

th@slepice:~/ebusd-esp/dist$ esptool.py --port /dev/ttyUSB0 write_flash -z 0x1000 ebus-v3_lolin32.bin 
esptool.py v3.1
Serial port /dev/ttyUSB0
Connecting.......
Detecting chip type... ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, Coding Scheme None
Crystal is 40MHz
MAC: 24:0a:c4:13:3e:58
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00001000 to 0x000d0fff...
Compressed 849472 bytes to 477659...
Wrote 849472 bytes (477659 compressed) at 0x00001000 in 42.5 seconds (effective 159.9 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

After reset I am getting reboot loop:

th@slepice:~/ebusd-esp/dist$ screen /dev/ttyUSB0 115200

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:192468
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:192468
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:192468
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:192468
ets Jun  8 2016 00:22:57

I am using this version of esptool:

th@slepice:~/ebusd-esp/dist$ ~/.local/bin/esptool.py version
esptool.py v3.1
3.1

Hi I am having problems with the EBUS adaptor 2.0(WMOS) Build 20181125.
I have it set to a fixed IP address example 192.168.1.17 - and set the corresponding mask and gateway. . Everything seems fine and I can access it ok with the IP address and connect to it ok..
After a few hours I rechecked it and its IP address has changed to a DCHP allocated address.
The web screen still shows the fixed IP settings i.e. 192.168.1.17 but its actual address I have to use to access the WEB interface is my next free DCHP address (192.168.1.102). Changing the settings on the WEB screen or rebooting don’t change it back to the Fixed address. The only way I can restore the Fixed IP address it to use the Firmware update option and reload the Firmware.. Then the WMOS reboots to the fixed IP address without any changes having to be made to the configuration screen.
Do any of the unused inputs on the WMOS trigger anything - I have tied the RESET input to 3v3 in case this was the problem but other unused inputs are left floating.
I have checked for any power stability problems but this does not seem to be the problem.
Any suggestions welcome , alternatively could you let me see the source code so I can debug this myself..

I have got this board: https://ebus.github.io/adapter/raspberrypi
When connect to my RPi it works perfectly fine:

But I do not want to run this via the RPi anymore. So I hooked it up to a wemos d1 mini.
5V to 5V
3.3V to 3.3V
TX to RX
RX to TX
(also tried TX to TX and RX to RX)
GND to GND

Now it does not work when connected to the d1 mini with https://github.com/john30/ebusd-esp as firmware.

This is the config:

Any ideas what could be wrong? I check wiring several times. Looks good to me.

Hi,
I want to use the EBUSD v3 adapter together with a MQ5 gas sensor.
The MQ5 module needs 5V.

I see there's a J3 header proving GND + D7 pins. Since that D7 pin is directly connected to the Wemos input pin, do we have to use a voltage divider to feed the 3.3v high level through?

I'm powering the EBUSD v3 adapter using USB port J2, so as far as I can see (in the schematic), there's no 5V pin easily accessible anymore on the board. Am I correct?
Where would you then get the required 5V from? Apart from running a tiny wire from the input leg of the TS1117 LDO underneath the Wemos D1 mini?
That should not be the preferred/only way...

Or did you have another gas-sensor in mind when designing this board?

Also, how would the binary gas/no gas detected state be exposed in software? Can it publish MQTT messages? Any examples?

Overall, I see there's a definitive idea to support a gas sensor on the PCB and in the web config frontend but the actual implementation/usage is unclear from the documentation.

Also, I would like to use ESBHome as sensor platform for the EBUSD module to expose to HomeAssistant. I see in the documentation that these things are [todo]. Are they still coming or is this due to real-life issues (aka lack of time) in-definitively postponed?

Thanks.

too risky, e.g. when used on extension board

Hardware:

NodeMcu v1.0
Protherm Skat 9

Using all the defaults and RX/TX pins I get the following status:

Chip ID: 007a55a0
Hostname: ebus-7a55a0
Up time: 72
Free heap: 34736
ebusd connected: no
eBUS signal: no signal
eBUS initial signal: echo

And heater fails to f.49 error, according to manuals description is Short circuit on the eBus, overload on the eBus or on the eBus 2 of a voltage source with different polarity.

Any ideas how to debug this?

UPD: I've just found a note that voltage on EBUS should be 15-24 Volts, not sure how to properly archive this.
UPD: Looks like I miss the ebus adapter, it wasn't clear for me that ESP can't drive the bus directly.

Hi,
when trying to do a docker pull, as per your instructions, on my 64bit Raspberry but whatever I try, I'm getting an image for linux/amd64 architecture served. Is the auto multi-arch selection working fine? Are the other achitectures uploaded?

actually, my platform as per uname -m is:

Then, when trying to specify the specific platform to pull (hard-coded) on the docker run command line, I'm getting the same error:

Also with arm64v8 as platform:

also with the linux/arm32v7 platform:

Are the linux/arm* architectures missing or am I doing something wrong?
Can you provide, in case not provided or help further? All my other containers on this box are fine, no single issue with architectures so I feel it must be an EBUSD image issue.

Also, can you provide some examples for docker-compose usage?
It might save time later for people wanting to implement.
I started with it but I could not verify it yet since I can't even get the base use-case (with docker run) working due to the missing image for my architecture.

services:
#  ebusd:
#    container_name: ebusd
#    image: john30/ebusd
#    restart: unless-stopped
#    ports:
#      - "8888"
#    volumes:
#      - ./volumes/ebusd/data:/data
#    command: -f --scanconfig --mqttport=1883 --mqtthost=192.168.0.11 --mqttuser=ebusd -d enh:192.168.0.128:9999

Thanks.

Hi guys. First of all many thanks for the great job.

There are connection issues with ESP8266 and some hi-performance routers, which I personnally experienced with Netgear R8000 and Asus RT-AX92U. The ESP8266 would hardly connect to the router (or not connect at all).
This can be solved easily by changing the WiFi mode of the ESP8266.
With my router I need to use mode G for a flawless usage.

So please here is my request:
Would you please add a new config item « WiFi mode » with values B,G and N and use it in the setup routine, depending on the config:
WiFi.setPhyMode(WIFI_PHY_MODE_11B);
or WiFi.setPhyMode(WIFI_PHY_MODE_11G);
or WiFi.setPhyMode(WIFI_PHY_MODE_11N);

With that I would be able to use ebusd-esp with my router.

Many thanks
Mike

I've been testing 2 days so far and I don't get the ebus adapter working. I flashed the ebus-v2_nodemcu1.bin using the nodemcu firmware programmer. It starts good, and can enter the setup. After the reboot, the nodemcu makes a coonection to the WIFI, but after 5 seconds (when entering eBUS mode) no communication possible. I can't ping the device, no connection is made, and nothing in the serial monitor eather... Someone else had this problem? @john30 , any idea what can be wrong here? Is the nodemcu waiting for something in eBUS mode before starting up a network connection? I can't find the sourcefile to see where it can go wrong.
Thanks in advance for helping me out!

Hey John,

Against which version of esp8266 library is this firmware linked? Is it 1.7.1 or later?

I just gave your firmware a try yesterday (I want to passive read my eBUS), but the ESP crashes very often.

Also it is annoying that the firmware configuration has no option to freely use any digital input pin. Also I would like to disable TX completely, since I do not want to write to the eBUS.

My ESP board is a cheap chinesium one:
NodeMcu Lua ESP8266 ESP-12E CH340G

After 's' - connect Wi-Fi and reboot, no 'sensor' displayed at 'D4'.
Is that some bug?

Enter your choice: s Sensors: D4: 288D3C94971203: temperature=23.69 1 sensors found

Hi,
Im tryi'ng to configure my EBUSD Adapter v3 to connect my home WLAN. But every time, after entering SSID and password + Save/reboot in the web frontend, the Wemos D1 mini kind of hangs and only gets out of it by using the reset button, coming back with the default EBUS SSID. So my entered config is not saved.

Then I tried to do the same thing it via the CLI, over the serial port. I enter the same details, I can do a connect test there and it looks like I'm connected fine, I'm getting an IP address. So far so good. Then I chose '0' to save and reboot and alas, I'm getting again the EBUS SSID :( Same behaviour as using the web frontend.

And this is while saving and rebooting ... Back to square one.

I also tried to do an F: (Factory reset) and then setting the WIFI config parameters + save&robbot but I'm having the same behaviour.

I also tried restoring factory settings with 'f' : no luck, same behaviour.

I also tried the same with a powered hub in the middle, to rule out power issues: Same behaviour.

This is my EEPROM dump:

EEPROM dump:
0000  c9 00 11 01 ff ff ff ff ff ff ff ff ff ff ff ff  ................
0010  ff ff ff ff ff ff ff ff ff ff ff ff 03 00 00 00  ................
0020  00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0030  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0040  ff ff ff ff 64 00 ff ff 00 00 00 00 00 00 00 00  ....d...........
0050  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0060  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0070  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0080  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0090  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
00a0  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
00b0  ff ff ff ff ff ff ff ff ff ff ff ff ff fb bb f2  ................
00c0  cf 98 c3 7b 53 8e fc 85 ff 27 d2 1d 02 ac 88 c1  ...{S....'......
00d0  4c 40 a3 fd 74 ad a3 f5 0c b4 48 9b ff ff ff ff  [email protected].....
00e0  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
00f0  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0100  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0110  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0120  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0130  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0140  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0150  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
0160  ff ff ff ff ff ff ff ff ff ff 5c cf 7f 9a e6 25  ..........\....%
0170  81 02 ff ff 96 14 11 01 24 00 00 00 00 00 00 00  ........$.......
0180  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
0190  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
01a0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
01b0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
01c0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
01d0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
01e0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
01f0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Any idea?

Thanks,

hi friend,

I need some help.
I just trie to connect the ebus adapter2.2 today (buyed batch december 2018).
But no success.
i have installed the last firmware ebusd-esp Build: 20191229

I removed the extention board.
connected my vaillant turbotech pro to the ebus terminal on base board.
Powered the wemos using the usb interface.

on the ebus-esp i see:
ebusd connected: yes (inactive)
eBUS signal: no signal

Is there any polarity for the ebus on the base board.
For info my ebus thermostat work perfectly, i have tried to install both in parallel and separately same issue.
here the command used to launch the ebus damon ./src/ebusd/ebusd -d 192.168.2.225:9999 -l /var/log/ebusd.log --scanconfig --latency=20000 --address=01

Could you help?

Something is wrong? Or I'm doing something wrong?
I'm not able to change the TCP/IP - even I enter from 'putty' or from 'browser'
the address is not changing.
I want to change to '135' but the board is always appearing under '237'.

P.S. The board used: WEMOS D1 mini; today I specially purchased it as I had problems with mini PRO.

Hi,

I have a vailant boiler and am in the process of tryin to read various things like flow, return, target and room temperatures off the Ebus when i came across this.

I have extensively used ESP modules for various things such as temp sensors and temp/humidity sensors, mostly based on Arduino with my own code.

I was looking at your implementation but it doesn't say anything about how the data comes out of the ESP to something workable.

Matt

I wanted to test 'PRO' version, but it is some problem with saving the configuration.
When I set-up with USB, all goes O.K. I.e. wi-fi is connecting.

But when opening the page, doing some additional changes, etc. and then saving...

After reboot it is not possible to connect with the IP defined.

But when (again) connecting via USB - the screen is initial, looks like no data saved...

=================
Additional 'small-bug' on the initial screen 'host-name' is not updated, even if defined by user...
It is still default 'ebus-ct...'.
But on next screen it is O.K., given name by user 'ebus'.

Hello. Thanks for your project! I want to ask - is it possible to add, like, basic authentication access to web configuration page? Because any user in local network can change parameters, I think this is security issue. P.S. Sorry for my English.

Not sure this is feasible but would be great. Otherwise updating means quite a lot of dismantling the current installation. On demand would suffice.

Hello,
First give a all thumbs up for the programmer that have done all this work.
Im trying to implement it on my "Saunier Duval Thelia Condens 30-A, that I know forefact that have Ebus and even the brand sells some expensive wifi thermostat to it.
That being said I bougth the adapter and open my boiler.
Im gona share what I've seen prior to connect it first time.
Ebus voltage is stable at 21.0 volts (thats weird) but yet flashed the wemos and im able to enter the HTML page of connection however I see this on the Weemos and make no sense to me.
Could be something going crazy on the boiler? Something on the adapter?
Have no ideia how to do now, since there is some other point on the pcb that is around 17v but still get this:

Chip ID: 00513121
Hostname: ebus-513121
Up time: 4637
Free heap: 33024
ebusd connected: no
eBUS signal: no signal

see atachement

How should I test further?

Thanks for your kind help

I've problem with enabling eBus server on my WeeMos D1 mini.
Whenever I'm trying to save config and reboot I'm getting to default state with EBUS AP and following DHC status:
WIFI IP address: DHCP (failed: disconnected, reason: 1)

Config steps:

1. Choose SSID (option 1)
2. Set WiFi secret (option 2)
3. Check connection (option c). After this step I see device got IP address and I can log in on device.
4. Save and reset (option 0)

After that all time I getting:

load 0x4010f000, len 3584, room 16
tail 0
chksum 0xb0
csum 0xb0
v2843a5ac
~ld

Welcome to eBUS adapter 3, build 20201122
Configured as WIFI access point EBUS without password.
For configuration with web browser, connect to this WIFI and open http://192.168.4.1/
Entering configuration mode.
Chip ID: 00458AE4
Hostname: ebus-******

       Configuration (new):
                            1. WIFI SSID: **EBUS**
                                               2. WIFI secret:
                                                                3. WIFI IP address: **DHCP (failed: disconnected, reason: 1)**
    w. WIFI power: normal
                          4. WIFI hostname: ebus-458ae4
                                                        5. eBUS RX+TX PINs: Adapter 3 RX+TX (GPIO3+1)
                                                                                                      6. ebusd connection: enhanced on port 9999
                          7. HTTP TCP port: 80
                                               8. LED PINs: RX:disabled, TX:disabled
                                                                                     9. Initial PINs: D4:H

                                                                                                           p. Set current PINs: D4:H
              t. Toggle current output PIN
                                           s. Scan & read sensors
                                                                  c. Connect WIFI
                                                                                  e. Dump EEPROM content
                                                                                                         f. Load factory settings
           F. Factory reset (i.e. erase EEPROM)
                                                o. OTA enabled: waiting
                                                                        r. Reboot (without saving)
                                                                                                   0. Save configuration and reboot

            Enter your choice:

Hi, John
I got some problems with the hardware that I bought from you 2 years ago. I get an error while I try to update my Wemos D1mini lite from ebus v2.0 to ebus v3.0. I tried to do it from ebus html page, bu I got an error:
Update error: ERROR[10]: Magic byte is wrong, not 0xE9

Also, I tried to load firmware with esptool.py and I successfully loaded firmware into my Wemos but it doesn't work: WIFI network EBUS does not appear.
Could you help me please to resolve the issue?
Thank you

Hello,

thanks for the ebusd software, I'm using it for a year or two now on my vaillant heater.

I struggle with the following:

When my router reboots and new IP addresses get assigned, it's never able to connect to the heater immediately. However normally it randomly starts working again (now we're already a few days later ...). Nothing changed in the hardware or its connections. I've tried rebooting the devices, regular restarts with sudo systemctl restart ebusd, ... .

So my question, is there some reliable startup procedure to get connection to the ebus?

I'm running the ebusd-esp software on a wemos with the v2 adapter, the ebusd software is running on a tinkerboard (this points to the IP address of the ebusd-esp).

Some more information below:

in /etc/default/ebusd I use
EBUSD_OPTS="-d 192.168.0.193:9999 -l /var/log/ebusd.log --scanconfig --latency=50000 --address=01"

The ebusd-esp adapter reports:

Build: 20191110
ebusd device string: 192.168.0.193:9999


Hostname: ebus-e387f5
Up time: 25445
Free heap: 30472
ebusd connected: no
eBUS signal: no signal
eBUS initial signal: yes 

some part of the ebusd.log:

2021-02-20 18:53:47.114 [main notice] SIGTERM received
2021-02-20 18:53:47.268 [main notice] ebusd 21.2.v21.2 started with auto scan on device 192.168.0.193:9999
2021-02-20 18:53:47.596 [bus notice] bus started with own address 01/06
2021-02-20 18:53:51.899 [main notice] ebusd stopped
2021-02-20 18:55:47.505 [main notice] ebusd 21.2.v21.2 started with auto scan on device 192.168.0.193:9999
2021-02-20 18:55:47.836 [bus notice] bus started with own address 01/06
2021-02-20 18:55:57.671 [main notice] update check: OK
2021-02-20 18:57:57.908 [main notice] update check: OK
2021-02-20 18:58:03.619 [main notice] SIGTERM received
2021-02-20 18:58:03.704 [main notice] ebusd 21.2.v21.2 started with auto scan on device 192.168.0.193:9999
2021-02-20 18:58:04.031 [bus notice] bus started with own address 01/06
2021-02-20 18:58:08.229 [main notice] ebusd stopped
2021-02-20 19:00:14.099 [main notice] update check: OK
2021-02-20 19:05:44.479 [main notice] ebusd 21.2.v21.2 started with auto scan on device 192.168.0.193:9999
2021-02-20 19:05:44.841 [bus notice] bus started with own address 01/06
2021-02-20 19:07:54.914 [main notice] update check: OK
2021-02-20 19:09:20.264 [main notice] SIGTERM received
2021-02-20 19:09:20.379 [main notice] ebusd 21.2.v21.2 started with auto scan on device 192.168.0.193:9999
2021-02-20 19:09:20.700 [bus notice] bus started with own address 01/06
2021-02-20 19:09:25.305 [main notice] ebusd stopped
2021-02-20 19:11:30.772 [main notice] update check: OK

ebusctl info

stijn@tinkerboard:/etc/default$ ebusctl info
version: ebusd 21.2.v21.2
update check: OK
signal: no signal
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd

Hi! I have had to download and configure lolin32 in the ESP-WROOM-32. This module was assembled with the eBUS adapter on one board. Connected the module through TCP to ebusd (RPI4). On the eBUS there is a Vaillant boiler only, which is sent AUTO-SYN. I connected a UART sniffer on the Rx WROOM, where both Tx and Rx (zero modem on the eBUS adapter) can be seen. ebusd started full-scan:
EBUSD_OPTS="--scanconfig=full -d 192.168.1.101:9999 --answer --localhost -p 8888 --httpport=8889 --enablehex --logfile=/home/pi/Desktop/shara/ebusd.log --loglevel=debug"
and sees a mismatch between the sent commands from ebasd and the transmitted bytes from the WROOM in eBUS. Is there a precedent for WROOM to work correctly with lolin32 firmware?

Hi,

I have the new ebus2 adaptor since this week-end, and had a very strange issue twice since then:

I'm using the new OpenHab2 ebus binding, with much more success than with esera ethernet coupler.

After some time, I remark that the boiler stopped being regulated, and just start to heat very strongly, and the VRC470 screen complained about lost ebus communication.

• On the eBus adaptor, I can see the red LED continously blinking, one or two time pe.cond, yellow led is lit and green LED seems to blink as usual, but less visible than the RED, so I'm not so sure about this.
• On the ebusd-esp web page, I can see than the connection is not active anymore.
• On OpenHab side, the binding is disconnected, and logs does not show specific error message, just that communication stopped with the adaptor.

I guess the ebusd is stuck in, a loop, spaming the ebus bus, preventing the VRC470 to effectively control the boiler. As soon as I disconnect the adaptor from the ebus, boiler come back to standard behavior, as well as VRC470.

Since the connection is lost with the openHAB binding, the origin of the spam shouldn't be the binding itself.

I have then many questions:

• So what could explain this condition, especially why is the ebusd-esp continusly sending things while being disconnected on TCP/UDP client side ?
• What could be done to troubleshoot this ?
• Is there a way to get a log of what the ebusd-esp is sending or receiving ? A special debug web page would help a bit.
• I'm a bit reluctant to let it connected without supervision for now :/ Is there a way to prevent the boiler to heat up too much in case of such event ? I am wondering if lowering the manual heat poti, that is supposed to be set at max when connected to a VRC could be lowered for that.

I'm using the 2.1 adapter with attached WEMOS. As my heating does not supply VL temps for HK1 and HK2 I'd like to add those. 1-wire sensors with precision reading seem to be the obvious choice.

In 7f1af89, analog input was added. Would it be possible to consider adding 1-wire as well, at least for testing purposes to see if it can still keep the ebus timing?

Any plans to release source code?

Thank you very much for your your code!

I am using a nodeMCU in combination with the Pedotherm / Vaillant - recoVAIR 350.

I think I have a working ebus connection.

Here is the status:

eBUS adapter 3
Build: 20201122
ebusd device string: enh:192.168.178.126:9999
WiFi signal: 54% (-73dBm)
Status
Configuration
PINs
Firmware update
Chip ID: 0058bb2d
Hostname: ebusLueftung
Up time: 204
Free heap: 34288
ebusd connected: no
eBUS signal: acquired
eBUS initial signal: yes

But I can not see any logs here:
http://192.168.178.126:9999/

I alway get the error message:
ERR_INVALID_HTTP_RESPONSE

What can I do? Who can I get the data or the control for this device?

Thank you very much,

Regards,

Martin

Hello!
I could not find the source code for the binaries in the dist folder.
I would like to port it over to STM32F4 with integrated ethernet MAC.

Dear John30,

I'm a newbie on ebusd, and tried to flash your mod'd firmware (20190407) to a Wemos D1 Mini.
I accessed the flashed fw with a cellphone and configured the WiFi to the RasPi's WiFi. After a restart Wemos connected to the RasPi correctly, but when I tried to give a fix IP address, save it and reboot, the Wemos stayed on the DHCP'd IP, and not the fix. I tried to reflash and set the fix IP again and again, but the firmware can't save the IP. (There was ESPEasy and Tasmota on the Wemos before, and those were working flawlessly with a fix IP.)

Ok, I tried then to connect Wemos on USB with Putty, but it can't: the Putty window is empty with the COM port (I flashed Wemos through this port, so the virtual COM9 is WORKING) and with 115200 bps.

What can I do to give the fix IP to the Wemos/eBUS adapter 2.0?

Thanks for any ideas!

And an other bug: on the Configuration page there is a setting in the 3rd line: "gateway", but it contains really the netmask (255.255.255.0), not the WiFi gateway. If I write the real gateway in the box, and press Save & Reset, the Wemos isn't accessible at all and it can't connect to the WiFi.
![ebusd bin error]

The Configuration page is here (the "ebusd device string" is the IP that Wemos is on the WiFi. I tried to save and reset a few times, with that "3rd WIFI IP address" fix IP setting, but the IP isn't changed)
(https://user-images.githubusercontent.com/51930390/62709257-4eb32480-b9f5-11e9-857f-510a85dfa941.jpg)

Please add “wifi_set_phy_mode(WIFI_PHY_MODE_N);”. This will give possibility to use 802.11n.

Hi John,

it seems you bin file is corrupt, it is only 45k in size.
When I download the whole repository I can find a proper sized file.
Is it correct you are not hosting your source code?

Greetings, Jeroen

My esp-ebus-adapter sometimes becomes unavailable and does not come up again. From other projects I know that the low-level IP stack of esp sometimes can make problems and requires a full reboot to be able to connect to the wifi again.
Therefore I wonder if there is any restart strategy implemented if the wifi connection is lost (or/and if no ebusd is connected) for a couple of minutes?

Hi,

I have a dedicated ssid for my iot devices where all works fine. However for this one I cannot save wifi password (64 characters):

Its the same for serial configuration

Any ideas?

I have flashed such device - but it is not working good...
I'm taking about version with external antenna and - I think - 16MB of memory...

Hi, this firmware looks great! Please is it possible to include links to instructions how to wire NodeMCU (and the other module types) ? Just to complete the picture..

I have the firmware loaded on my nodemcu but I don't know how to wire it to my heater. I understand it's possible to make a simple read-only ebus interface with these instructions:https://ebus-wiki.org/lib/exe/fetch.php/ebus/arduinoebus.pdf Is it possible to use this with it?

Thank you
Tom

Hi,

Currently hosted *.bin is continuously rebooting throwing dump in COM port. I've succsseed flashig last release from Dec 2017.

If the output of the self-made ebus adapter V1.6 is connected to RX, the signal does not reach low level (confirmed by oscilloscope) which means the direct RX mode does not work.

Everything works fine if D1 is used for reception (in combination with the setting SW D1).