As I don’t have any traction in the Unifi 5.1 thread, I’ll open a new one
Not sure if this should go here or should I create a new thread. I’ve updated to OH5.2 yesterday and new Unified Unify binding giving me some problems:
- As I understand Network part of the binding supposed to work as it works before, however without any changes to the infrastructure all the devices went into “Unknown” state.
Log is showing this:
2026-07-12 23:45:59.136 [DEBUG] [.network.api.cache.UniFiVoucherCache] - Put #0 entries in UniFiVoucherCache:
2026-07-12 23:45:59.136 [DEBUG] [l.network.api.cache.UniFiClientCache] - Could not find an entry in the cache for id: '74:d0:2b:7d:07:d5'
2026-07-12 23:45:59.136 [DEBUG] [l.network.api.cache.UniFiClientCache] - Could not find an entry in the cache for id: '74:d0:2b:7d:07:d5'
2026-07-12 23:45:59.137 [DEBUG] [twork.api.cache.UniFiControllerCache] - Could not find a matching client for cid = 74:d0:2b:7d:07:d5
which is fine, this device was not on the network for sometime and not in Unify Cache anymore, so its status supposed to be “Unknown”. Other devices are in the cache and in the log:
- UniFiClient{id: '658aa097e64367069f419c2b', mac: 'e8:9c:25:94:d7:f0', ip: '192.168.10.142', hostname: 'kpanchen01', name: 'kpanchen01', wired: true, guest: false, blocked: false, experience: 75, device: UniFiDevice{mac: '68:d7:9a:6f:47:dd', name: 'KNP Basement Main Switch', type: 'usw', model: 'US624P', version: '7.4.1.16850', experience: 92, disabled: false, led: null, uptime: 4141249, site: UniFiSite{id: '6118d52d19617e0ac0faac0d', name: 'default', desc: 'Default'}}}
But nothing indicates that binding ever evaluated this device (same with other devices), basically only one is evaluated.
- Protect bridge configuration. If protect bridge is configured like it was provided in the documentation:
Bridge unifi:nvr myNvr "UniFi Protect NVR" [] {}
Log just gave an error configuring bridge:
2026-07-13 00:11:41.814 [INFO ] [enhab.core.model.core.internal.ModelRepositoryImpl] - Loading DSL model 'unifi.things'
2026-07-13 00:11:41.869 [WARN ] [enhab.core.model.core.internal.ModelRepositoryImpl] - DSL model 'unifi.things' has errors, therefore ignoring it: [8,19]: missing ':' at 'knpprotect'
If bridge is configured with “:” like this “unifi:nvr:knpprotect” it still gives an error but works and things / items go online:
2026-07-13 00:13:13.581 [INFO ] [enhab.core.model.core.internal.ModelRepositoryImpl] - Loading DSL model 'unifi.things'
2026-07-13 00:13:13.605 [INFO ] [enhab.core.model.core.internal.ModelRepositoryImpl] - Validation issues found in DSL model 'unifi.things', using it anyway:
Line 8: Provide a thing type ID and a thing ID in this format: <thingTypeId> <thingId>
Are those bugs or is it me doing something wrong?
Thank you!! K.
Update: so I turned machine which was offline back online today and after that all other things went from unknown to online, seems like a bug in the binding where after failure it is not evaluating other things, if somebody can confirm that scenario I’ll open a bug report!