Unknown errors in log

Setup, Configuration and Use Runtime
1
  • Platform information:
    • Hardware: RPI 5 4Gb
    • OS: OH5 Openhabian, openHAB 5.0.2 - Release Build
    • Java Runtime Environment: what openhabian installed
    • openHAB version: openHAB 5.0.2 - Release Build
    • The installed bindings are Zwave, Zigbee, Astro, Network, Pushover, Basic UI, RRD4J, JavaScript Scripting and JRuby Scripting

I upgraded from a RPI3 running OH 4 to an RPI5 running OH5 a while back and it’s been working fine. I decided over the last week to clean up the install as there are a number of never deleted leftovers. I’ve been checking the log to find errors I created in the process and it’s all clean now but I have these seemingly meaningless errors and was wondering what they might be. All these errors only happen at startup:

I have 2 Fire TV boxes and I get these errors related to their IPs. Since the series occurs multiple times I may have them out of order as it’s not clear to me where they start and end

18:10:46.442[WARN] [org.jupnp.binding.xml.RecoveringUDA10DeviceDescriptorBinderImpl] - Regular parsing failed
18:10:46.535[WARN] [org.jupnp.binding.xml.RecoveringUDA10DeviceDescriptorBinderImpl] - Regular parsing failed
18:10:46.536[WARN] [org.jupnp.binding.xml.RecoveringUDA10DeviceDescriptorBinderImpl] - Removing leading garbage didn't work
18:10:46.587[WARN] [org.jupnp.util.SpecificationViolationReporter] - UPnP specification violation: No closing element in descriptor
18:10:46.618[WARN] [org.jupnp.binding.xml.RecoveringUDA10DeviceDescriptorBinderImpl] - Removing leading garbage didn't work
18:10:46.629[WARN] [org.jupnp.protocol.RetrieveRemoteDescriptors] - Could not hydrate device or its services from descriptor: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:NFANDROID2-PRV-FTVCUBE2022-AMAZOAFTGAZL-35467-034E5FA8C5BA486, Descriptor: http://xxx.168.xxx.xxx:9080, Root: true
18:10:46.634[WARN] [org.jupnp.util.SpecificationViolationReporter] - UPnP specification violation: No closing element in descriptor
18:10:46.670[WARN] [org.jupnp.protocol.RetrieveRemoteDescriptors] - Could not hydrate device or its services from descriptor: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:NFANDROID2-PRV-FTVSTK-AMAZOAFTA-7348-E9561F58DD1344Z2C301ZC6ADD1E75A21, Descriptor: http://192.168.xxx.xxx:9080, Root: true
18:10:46.671[WARN] [org.jupnp.util.SpecificationViolationReporter] - UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'ProductAgent for Windows'
18:10:46.672[WARN] [org.jupnp.util.SpecificationViolationReporter] - UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'ProductAgent for Windows'
18:10:46.672[WARN] [org.jupnp.util.SpecificationViolationReporter] - UPnP specification violation: UPC must be 12 digits: '00000-00001' for device 'ProductAgent for Windows'

And then I have this error which refers to Node 17 and I’ve no idea where it might be coming from or how to go about looking as the Device that was Node 17 died and was removed long ago.

18:11:16.803[WARN] [org.openhab.binding.zwave.internal.protocol.ZWaveController] - NODE 17: Restore from config: Error. Data invalid, ignoring config.

Any suggestions welcome. None of it seems to be a problem but I’ve no idea why it might care about the Fire TVs as nothing related to them is installed. I’d be happier if I could get rid of them as it would make the log easier to read.

Thanks so much.

2

First these are warnings and not errors. They are not fatal. Nothing is being blocked from working because of these warnings.

Given the name of the class where the warnings are coming from and the fact that you are not using the UPnP binding I’m going to guess these are coming from OH’s suggested add-ons discovery. When OH comes up it will probe the network, file system, etc. looking for technologies for which it has a binding and will recommend those to you when you go to the Add-on Store.

There is a lot of work going on with UPnP right now. See openHAB 5.1.0Mx: UPNP Issues. These warnings might be related to problems that are currently being worked in OH 5.1. These warnings might go away once all that work is merged (and you upgrade of course).

In the mean time, you can turn the UPnP discovery off under MainUI → Settings → Add-on Management → Show Advanced → Toggle off UPnP suggestion finder. You won’t get suggestions for technologies OH might support that use UPnP any more but I suspect that wouldn’t be a hardship for you anyway.

It was physically removed, but it would seem the Zwave controller still knows about it. The only way I know of to remove the node from the controller is through an administration tool like OpenZwave or a tool provided by the vendor. But there may be a way to do it through the add-on now that I don’t know about.

Again, this is a warning and it’s not keeping anything from working.

3

Thanks so much for answering. I figured there was no problem but wanted to check.

FWIW, the only things on the Show Advanced page are:

  • Access Remote Repository (ON)
  • Include (Potentially) Incompatible Add-ons (OFF)

Nothing to do with UPnP. As far as I know nothing on my network uses UPnP though I’m sure something does.

And if no one else says so, you are one of the most useful posters here and I never cease to learn from your posts and I want to thank you so much for that.

4

I thought that was added to 5.0 but I guess it’s not there until 5.1.

Thanks!