Android Notifications Binding - errors when openhab is starting

Add-ons Bindings
1

Hi I’m using openhab 4.1.1 on ubuntu 22.04. When openhab is starting I have such errors:

2024-02-11 21:10:00.563 [ERROR] [ions.internal.FireTvDiscoveryService] - bundle org.openhab.binding.androidnotifications:4.2.0.202402011056 (328)[org.openhab.
binding.androidnotifications.internal.FireTvDiscoveryService(425)] : Constructor with 0 arguments not found. Component will fail.
2024-02-11 21:10:00.585 [ERROR] [ions.internal.FireTvDiscoveryService] - bundle org.openhab.binding.androidnotifications:4.2.0.202402011056 (328)[org.openhab.
binding.androidnotifications.internal.FireTvDiscoveryService(425)] : Error during instantiation of the implementation object: Constructor not found.
2024-02-11 21:10:00.637 [WARN ] [y.mdns.internal.MDNSDiscoveryService] - bundle org.openhab.core.config.discovery.mdns:4.1.1 (170)[org.openhab.core.config.dis
covery.mdns.internal.MDNSDiscoveryService(142)] : Could not get service from ref {org.openhab.core.config.discovery.mdns.MDNSDiscoveryParticipant}={service.id
=842, service.bundleid=328, service.scope=bundle, osgi.ds.satisfying.condition.target=(osgi.condition.id=true), component.name=org.openhab.binding.androidnoti
fications.internal.FireTvDiscoveryService, component.id=425}
2024-02-11 21:10:00.648 [WARN ] [y.mdns.internal.MDNSDiscoveryService] - bundle org.openhab.core.config.discovery.mdns:4.1.1 (170)[org.openhab.core.config.dis
covery.mdns.internal.MDNSDiscoveryService(142)] : DependencyManager : invokeBindMethod : Service not available from service registry for ServiceReference {org
.openhab.core.config.discovery.mdns.MDNSDiscoveryParticipant}={service.id=842, service.bundleid=328, service.scope=bundle, osgi.ds.satisfying.condition.target
=(osgi.condition.id=true), component.name=org.openhab.binding.androidnotifications.internal.FireTvDiscoveryService, component.id=425} for reference MDNSDiscov
eryParticipant

But sending text or pictures to Chromecast TV is working.

2

That’s not an official add-on, it’s from the marketplace (I’m assuming Android Notifications Binding: Support for multiple methods to send Video, Images and Text to Android TV, Fire TV or Sheild TV).

Just to get the obvious stuff out of the way first.

Have you installed this in the past 25 days? If you installed before that point it might be the case that a version of the binding for 4.0 was published which may not work with 4.1.

3

Yes, I installed it about 2 weeks ago.

4

@Andy_Co
EDIT: I can confirm it does it here too. Will need to look into it when I get some time, it will not effect the opperation of the binding, only stops the discovery from working as it has 3 methods and probably only 1 of the 3 works for discovery.