Then I had the .jar file, and it was gone. Unless I’m very mistaken.
But thanks for the info!
Same here after upgrading to 4.3.1. After installing it again, all ESP’s were working again. Also in the running config, I couldn’t add a new ESP, Binding didn’t give me the option. Re-installed it again and no problems adding the new ESP.
There is a bug somewhere in core that yet has to be found, see https://github.com/openhab/openhab-core/issues/4494
Was there ever a way to handle the unknown unit? Can someone share with me their RATGDO ESPHome things file so i can try loading it from a file and edit the unit for that channel? I created a Things file but don’t think i did it right.
Unit 'codes' unknown to openHAB, returning DecimalType for state '2411.0' on channel 'esphome:device:8dcf64d482:rolling_code_counter'
You need to update the esphome firmware to have it send a valid unit - or no unit at all. It is meant as a warning that there is a mismatch.
A work around could be to set the Log level for this logger to a higher level - or to create a config parameter in the binding or thing to ignore these mismatches.
If I understand correctly, openHAB 5 will run on Java 21, so I imagine all bindings will have to work with Java 21 as well… Hopefully, that’s not too much recoding?
Java is (generally) backwards compatible, moving to Java21 is mainly about using newer constructs & apis for various reasons. I’d be a bit surprised if the binding didn’t run on Java21 today, but I haven’t tested.
Whether it runs on OH5 or not depends whether the core maintaines introduces some breaking changes. I’m not aware of any, but I’m not following too closely either.
Feel free to test and report back.
1 Like
i don’t know if i had a RPI firewall problem but i could not connect to my ESPhome anymore
19:08:06.344 [WARN ] [phome.internal.handler.ESPHomeHandler] - [REMOVEMEWHENADDINGbewaesserung] Error initial connection
no.seime.openhab.binding.esphome.internal.comm.ProtocolAPIError: Failed to connect to 'bewaesserung.local.' port 6053
at no.seime.openhab.binding.esphome.internal.comm.ESPHomeConnection.connect(ESPHomeConnection.java:65) ~[bundleFile:?]
at no.seime.openhab.binding.esphome.internal.comm.EncryptedFrameHelper.connect(EncryptedFrameHelper.java:76) ~[bundleFile:?]
at no.seime.openhab.binding.esphome.internal.handler.ESPHomeHandler.connect(ESPHomeHandler.java:189) ~[bundleFile:?]
at no.seime.openhab.binding.esphome.internal.handler.MonitoredScheduledThreadPoolExecutor$TimedRunnable.run(MonitoredScheduledThreadPoolExecutor.java:140) [bundleFile:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.nio.channels.UnresolvedAddressException
at sun.nio.ch.Net.checkAddress(Net.java:149) ~[?:?]
at sun.nio.ch.Net.checkAddress(Net.java:157) ~[?:?]
at sun.nio.ch.SocketChannelImpl.checkRemote(SocketChannelImpl.java:816) ~[?:?]
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:839) ~[?:?]
at java.nio.channels.SocketChannel.open(SocketChannel.java:285) ~[?:?]
at no.seime.openhab.binding.esphome.internal.comm.ESPHomeConnection.connect(ESPHomeConnection.java:56) ~[bundleFile:?]
... 9 more
I was trying to set up my first esphome device today, and got the same exception on OpenJDK 17.
The issue was that I wrote http://, and that couldn’t be resolved. I think you might have an extra “.” at the end of the name, try bewaesserung.local without the dot.
Also read the first part of the thing uid. There is a hint there 
Edit: I updated the FAQ
thanks… i recompiled with no unit and worked perfectly.
I’m using ESPhome with the native API on OH 4.3.1. I want a binary sensor on my esphome device to send a command (vs an update) to an item. Is there a supported way to do this?
PS, Arne, this binding is awesome. I’m on my second esphome device now; the first making a status/control panel for my shop, the second acting as an interface for my Dylos air quality sensor. I plan to update another of my hand-crafted ESP8266 sensors (temperatures from our boiler) to esphome as well.
Hi, I dont think OH allows bindings to send commands to the framework. While there might be something in the ESPHome API spec, I have not studied this Home Assistant Service in detail.
The good news is that your case can easily be solved by standard OH concepts. One is to create a (very) simple rule to listen for updates or changes from the binary sensor (OH) item, and then sending a command to the desired item.
I don’t know which rule engine/language you are using, so I’m not going to craft any examples 
Good luck with your shop setup!
1 Like
Thanks. I’d considered that option, but was concerned that it might cause a ping pong effect between OH and the esphome device. I’ll give it a try and see what happens.
I use ECMAscript, btw. It’ll be a simple implementation.
My add-on store ESPHome binding got uninstalled again… Any idea how that’s possible?
I assume you upgraded OH, and that you had the binding installed from the marketplace opposed to jar-file in the addons folder?
Correct.
It happened again… @seime, do you have a jar file I can use?
(Alternatively, if you have an idea on how to get more info an these strang auto-uninstall, I’d happily try that. I thought I’d ask a broader audience: ESPHome binding keeps disappearing)
Yes, just follow the first link in the initial post in this thread.