Hi Jeff,
please state the version of the binding you are using and send DEBUG level logs via PM.
BRG
Hi Jeff,
please state the version of the binding you are using and send DEBUG level logs via PM.
BRG
Hi Arne -
Iām using version 4.1.0.202503070857.
The log for the first issue is attached. To create this log:
I restarted my esphome device
Turned the Pool_Zero_Flow_Sensor switch a few times and the esphome never saw this action. I never saw the āSending message type HomeAssistantStateResponseā in the log.
I then disabled and re-enabled the openhab thing
Turned the Pool_Zero_Flow_Sensor switch and now the esphome device saw this action. In the log this was:
Sending message type HomeAssistantStateResponse with content 'entity_id: "itemstatechangedevent.pool_zero_flow_sensor"
Well, after quite a while of testing, some progress here and there, I have to remove the esphome binding from OpenHAB because I cannot make it work stable.
I spent the last couple of months without major issues (just the one random device going offline but returned by itself ) but this last week all of my esphome devices go offline routinely and stay offline or āyellowā. Every day I have to go into the karaf console to restart the binding.
Iāve been using mqtt and while auto discovery has some problems, it may be a worth it alternative and Iāll be exploring that.
I can only assume that the problem lies in my setup, maybe docker, but unfortunately I donāt have enough knowledge to troubleshoot the issue.
Iām sad today ![]()
Just wanted to share that if anyone is seeing this behavior, then youāre not alone.
Still very happy with it since june 2024. I donāt use docker. It is very stable but at every OH update I have to reinstall it. This has been discussed earlier I think.
Not the same issue. Seine was always very kind to me and assisted, but the problem never truly went away unfortunately.
I am still getting the following error message:
[REMOVEMEWHENADDINGirrf] Ping responses lacking. Waited 6 times 30s, total of 180s. Last pong received at 2025-05-11T10:30:55.137826937Z. Assuming connection lost and disconnecting
How can I fix this?
Running the latest version?
running 4.3.5 of OH and ESPhome add-on Updated At 12. march 2025 09:36
This one is really hard to debug because I donāt see this myself at all (other connection issues related to a crowded radio environment however - but always the same 3 devices that are acting up).
There are a few things you can try; see first and third FAQ entry: GitHub - seime/openhab-esphome: ESPHome native API implementation for openHAB binding
Iām also sending you a new version in a PM where Iāve rewritten the thread handling just to see whether it helps or not. One caveat is that Iāve removed support for plaintext password which has been deprecated for a year or so. Hopefully no-one is using it anyways. But Iām not ready to publish yet.
Please enable DEBUG logs and send to me when you see the problem. If I have nothing to investigate it is really hard to figure out the culprit.
BRG
Iāve got two of time lying around for a few months now, and itās about time I configured them, and put them to work ![]()
But I canāt figure out from the link how to install the necessary software on it⦠Whereās the yaml code?
Thanks for your assistance!
Updated version out, see initial thread post for details.
Is it possible to install an older version of this binding? It was working for me before the latest OpenHAB update.
I have 4x Konnected Panel Pros (https://konnected.io/), which connect using the ESPHome API without an API key.
There is a way to add them to ESPHome, but itās not working for me and adds a layer of unnecessary complexity even if I can get it working.
Why is the API encryption key required? Why canāt it be like it was before?
If I downgrade openHAB, will this binding downgrade too and go back to the way it was until I can get my device sorted?
Or is there a jar file of an older version of this binding that will work in the latest OH?
Can you update them wirelessly?
Itās complicated. Itās a standalone product that happens to use ESPHome firmware and api. It works standalone with itās app for changing settings and setup, this is why it has worked for me until now, but the app has no api settings. There is a way to adopt them into ESPHome and customise the firmware, but for some reason they arenāt being discovered by ESPHome, so I need to trouble shoot all of that first.
I didnāt see this as a breaking change in the OH release notes, only in this thread. Either I missed it or it wasnāt there.
There was only warning if you were following this thread. I had no reason to need this thread until now.
I may not be explaining myself properly. Let me try again.
This binding connects to devices that use a firmware called esphome.
Esphome is part of nabu casa / home assistant.
The āownersā informed the community here:
About this coming change in 2023. Changes to esphome also affect bindings because if they remove features we also lose them.
So⦠if youāre not following esphome news, you get surprises like this ![]()
ok, well weāre here now, whether itās my fault or not.
I tried downgrading OH as far as I could without breaking even more stuff, but it is still using the newest ESPHome binding. Is there a jar of the last version of the ESPHome binding?