An ebusd add-on

On official version no working connection by WIFI… no found label where we can put address IP, only found port for TCP…
ALso should add label as Address IP and next select list with: TCP, UDP and ENH…

Wi-Fi connection is available in beta in the official version but is unreleased. The code needs to be improved before it is ready for release. I will try and get a new pull request open in next week or so.

I do not have a wi-fi enabled device so am doing this out of good will. Please feel free to fix this and open a pull request yourself if this is a feature you need.

Ok if you need tester i can also beta… Thanks for your work.

Hello timstanley1985,

thanks for your work. The configpath works.

The next step is to get the data out from the ebusd.

Greetings Tobias

New release :fireworks::sparkler:

0.83

  • BREAKING: Remove old style loglevel and logareas option

  • BREAKING: Remove TCP port option. Port will default to port 8888 internally. External port can be configured in network options

  • IMPROVE: Add access level config option

  • IMPROVE: Enable custom config files (save in config folder)

  • IMPROVE: Configure logger for individual areas

  • IMPROVE: Add watchdog URL so Home Assistant can restart eBUSd if it crashes

  • IMPROVE: Allow access with HTTP and TCP client

  • IMPROVE: Add MQTT retain option

  • IMPROVE: Add custom commandline options

  • BETA: Allow wireless ebusd adapter

0.82

  • IMPROVE: Enable custom CSV files (save in /config folder)

Custom CSV files:

To use custom CSV config files you can use the configpath option. You can create a local copy of GitHub - john30/ebusd-configuration: ebusd configuration files in your “/config” folder and change configpath to e.g. “/config/ebusd-configuration/latest/en”. Custom CSV files must be in the /config folder.

HTTP and TCP client Access

To use HTTP and TCP clients enter port numbers into the add-on network settings and activated in the config.

Custom command line options

You can add any command line options using the custom command line options field. Check the eBUSd wiki for all available options - 2. Run · john30/ebusd Wiki · GitHub

For example --initsend --dumpconfig

BETA - Wireless eBUSd adapter support

This release includes beta support for wireless eBUSd adapters. This is just a proof of concept at this stage and will be improved in the next release. To test wireless support enter the IP address into the custom device box. You must select a usb device to validate the config but it will be ignored at runtime

For example enh:192.168.0.7:9999

I would recommend using MQTT. If you set up some MQTT sensors and then send a get command with ?1 as the payload eBUSd will poll the reading every 30 second and publish the reading via MQTT

sensor:
  - platform: mqtt
    unique_id: ebusd_WaterPressure
    name: Ebusd WaterPressure
    state_topic: 'ebusd/bai/WaterPressure'
    value_template: "{{ value.split(';')[0] }}"
    unit_of_measurement: Bar
  - platform: mqtt
    unique_id: ebusd_FlowTemperature
    name: Ebusd FlowTemperature
    state_topic: 'ebusd/bai/FlowTemp'
    value_template: "{{ value.split(';')[0] }}"
    unit_of_measurement: °C
  - platform: mqtt
    unique_id: ebusd_ReturnTemperature
    name: Ebusd ReturnTemperature
    state_topic: 'ebusd/bai/ReturnTemp'
    value_template: "{{ value.split(';')[0] }}"
    unit_of_measurement: °C
  - platform: mqtt
    unique_id: ebusd_BoilerModulationTempDesired
    name: Ebusd BoilerModulationTempDesired
    state_topic: 'ebusd/bai/ModulationTempDesired'
    unit_of_measurement: '%'
  - platform: mqtt
    unique_id: ebusd_FlowTempDesired
    name: Ebusd FlowTempDesired
    state_topic: 'ebusd/bai/FlowTempDesired'
    unit_of_measurement: '°C'
  - platform: mqtt
    unique_id: ebusd_RemainingBoilerblocktime
    name: Ebusd RemainingBoilerblocktime
    state_topic: 'ebusd/bai/RemainingBoilerblocktime'
    unit_of_measurement: Minutes
binary_sensor:
  - platform: mqtt
    unique_id: ebusd_WP
    name: Ebusd WP
    state_topic: 'ebusd/bai/WP'
    payload_on: 'on'
    payload_off: 'off'
  - platform: mqtt
    unique_id: ebusd_ACRoomthermostat
    name: Ebusd ACRoomthermostat
    state_topic: 'ebusd/bai/ACRoomthermostat'
    payload_on: 'on'
    payload_off: 'off'
  - platform: mqtt
    unique_id: ebusd_Flame
    name: Ebusd Flame
    state_topic: 'ebusd/bai/Flame'
    payload_on: 'on'
    payload_off: 'off'
#    force_update: true
  - platform: mqtt
    unique_id: ebusd_running
    name: Ebusd Running
    state_topic: 'ebusd/global/running'
    payload_on: 'true'
    payload_off: 'false'
  - platform: mqtt
    unique_id: ebusd_signal
    name: Ebusd Signal
    state_topic: 'ebusd/global/signal'
    payload_on: 'true'
    payload_off: 'false'
automation:
  alias: eBUSd - Set polling for readings
  description: Send get command with polling priority 1
  trigger:
  - platform: state
    entity_id: binary_sensor.ebusd_running
    to: 'on'
    for:
      hours: 0
      minutes: 0
      seconds: 0
  - platform: homeassistant
    event: start
  condition: []
  action:
  - delay:
      hours: 0
      minutes: 10
      seconds: 0
      milliseconds: 0
  - service: mqtt.publish
    data:
      topic: ebusd/bai/WaterPressure/get
      payload: '?1'
  - service: mqtt.publish
    data:
      topic: ebusd/bai/FlowTemp/get
      payload: '?1'
  - service: mqtt.publish
    data:
      topic: ebusd/bai/ReturnTemp/get
      payload: '?1'
  - service: mqtt.publish
    data:
      topic: ebusd/bai/ModulationTempDesired/get
      payload: '?1'
  - service: mqtt.publish
    data:
      topic: ebusd/bai/FlowTempDesired/get
      payload: '?1'
  - service: mqtt.publish
    data:
      topic: ebusd/bai/WP/get
      payload: '?1'
  - service: mqtt.publish
    data:
      topic: ebusd/bai/ACRoomthermostat/get
      payload: '?1'
  - service: mqtt.publish
    data:
      topic: ebusd/bai/Flame/get
      payload: '?1'
  mode: parallel
  max: 10

I am starting testing :slight_smile:

Good option will be implement when we type password for MQTT and after save settings password will be show as ***********

New release :sparkler::fireworks:

0.84

  • IMPROVE: Add Polish translation (@pepsonEL)

  • IMPROVE: Improve configuration of network eBUSd adapters.

  • BREAKING: Remove foreground option. eBUSd will now run in foreground by default.

  • BREAKING: Network device config has changed. Custom_device has now changed to wireless_device

I don’t think it is possible to ***** the password field in the config

Now tested version 0.84 and works perfect. For network device i set only adress IP without device USB and works good. Thanks

Does everyone use MQTT with eBUSd? I have just written a pull request which would make MQTT mandatory and configured automatically.

Any concerns if I merge this for the next release?

Yes i use MQTT

Hi timstanley1985,

I also use MQTT and it works good.

Greetings Tobias

New release :sparkler::fireworks:

0.85

  • IMPROVE: Automatically configure MQTT
  • IMPROVE: Add MQTT log configuration option
  • IMPROVE: Use precompiled eBUSd

I think we are getting pretty close to a 1.0 release. Are there any features missing or any bugs that need fixing?

Hi. I try it but when click UPDATE and check Create Backup, it create backup very very very long and then start update. I think that it is very long time…

Hi, moved from manually created ebusd docker to this addon without an issue. Everything working fine for both reading and writing to ebus. Thanks a lot!

But tell me how works MQTT automatically ? WHere we can put login and pass and addres IP ?

I do not need to put user/password.
If you are using MQTT broker addon from HA, ebusd addon use HA user/password probably.

To put IP:port for network ebusd adapter you need to switch " Show unused optional configuration options" on configuration page.

Local MQTT server is discovered automaticaly I assume.

For me its no working… no send data to mqtt…