How to call ebusctl reload from Home Assistant

[HLFCode]

Every time my HA host reboots some of the ebus sensors become unavailable in HA.
This is confirmed by MQTT explorer that they are no longer in homeassistant->sensor

I can fix this by restarting the ebusd addon some time after the HA boot but this is a lengthy operation.

I've discovered executing reload from an external putty telnet terminal (to homeassistant.local:8888) enables the missing sensors and adds them to mqtt homeassistant->sensor so HA then picks them up

So my question is how can I create a HA service which connects to the ebusd addon and calls for a ebusctl reload?

Sorry if this is the wrong place to ask

[cociweb]

are you sure that ebusctl is the root cause? usually my ebus adapter became unresponsive/send garbage info then ebusctl does not decode the information well.

my solution is to reload the ebus adapter with curl on http://< ip >/config?reboot=Reboot in a shell command execution after 10 mins when a sensor became unavailable. (my trigger entity is the external temp: that is refreshed most commonly in my system.)

This reload force to try a handshake with the ebusctl which is almost an ebusctl reload.

[HLFCode]

I think the problem is with HA auto discovery in ebusd.

After a reboot, ebusd does not seem to pass on all the sensors to mqtt for HA to discover.

For example, my heat pump has a circuit ehp and a sensor sourcetempoutput. This should be presented to HA auto discovery in the homeassistant.sensor.ebusd_ehp_SourceTempOutput_temp topic

This sometimes/usually does not happen after a reboot so HA does not know about this and other ebusd sensors even though ebusd is updating the values in mqtt topic ebusd.ehp.SourceTempOutput

Issuing a reload command to ebusd forces a refresh of the homeassistant.sensors topic and HA then picks it up.

What I want to do is have an automation issue the reload command to ebusd a whenever the sourcetempoutput sensor is unavailable

[HLFCode]

@cociweb

with curl on http://< ip >/config?reboot=Reboot in a shell command

Could you provide more info on this please?

[LukasGrebe]

If the value is not polled by ebusd, having HA and ebusd Addon restart will not „see“ the value on the ebus until your ebus device sends a value.
Depending on device, manufacturer and value these are only sent once per day or every few hours. Some statistical values are only sent once per the bus once per month or year.

This could explain why the sensor has no value - if it was never sent on the ebus within the timeframe since your last ebusd addon restart.

This would be an ebusd config issue not related to this project.

[HLFCode]

@LukasGrebe Interesting, if I do a read sourcetempoutput it gives a value instantly implying it has already been polled/read but still does not go into the HA auto discovery.
read -f sourcetempoutput doesn't do it either.
I'll pose a question on john30/ebusd

[cociweb]

Could you provide more info on this please?

So it is only useable when your adapter disconnects from the ebusctl service (maybe you have some wifi issues, or any other reason)
You can create an automation where the trigger is on a commonly refreshed entity's availability

alias: EBUS restart
description: ""
triggers:
  - to: unavailable
    entity_id:
      - sensor.external_temperature
    for:
      hours: 0
      minutes: 10
      seconds: 0
    trigger: state
conditions: []
actions:
  - action: shell_command.shell_ebus_adapter_restart
    metadata: {}
    data: {}
mode: single

where the shell_command.shell_ebus_adapter_restart is the following in your configuration.yaml:

shell_command: 
  #EBUSDd adapter restart
  shell_ebus_adapter_restart: 'curl -X GET --output /dev/null http://< ebus_adapter_ip >/config?reboot=Reboot'

As Lukas mentioned, it won't change the certainty of the messages. The ebus messages are highly dependent on their value change frequency and the poll priority class (R1-R9), which are hard-coded in your ebus controller.

Additionally, you can play with the retain of the mqtt messages, but that is another concept.

[LukasGrebe]

Version 26.1 fixed reading write only and broadcast messages from cache this may be related. please upgrade and update this issue.