Unifi Protect Entry Sensor Not Recognized in Unifi Protect Integration

🛎️ Get Help Integrations
1

Doing another Unifi Protect Integration with Hubitat and found the following Unifi Entry Sensor (Part Number USL-Entry-3) is not recognized. I enabled debug and the following information was captured (below). Is there any chance this could be remediated quickly as I have "MANY" of these sensors and additional deployments next couple of weeks with this setup.

app:462026-05-03 05:10:34.386 PM

debug

No child sensor or camera device found for ID 69c5c1110315f803e4000b07; skipping

app:462026-05-03 05:10:34.384 PM

debug

parseNvrJson()

app:462026-05-03 05:10:34.382 PM

debug

Parsed JSON: [item:[metadata:[sensorMountType:[:]], start:1777853435343, end:1777853435343, id:69f7e3fb01866003e410a238, type:sensorClosed, device:69c5c1110315f803e4000b07, modelKey:event], type:add]

app:462026-05-03 05:10:34.380 PM

debug

componentParse: {"item":{"id":"69f7e3fb01866003e410a238","modelKey":"event","type":"sensorClosed","start":1777853435343,"end":1777853435343,"device":"69c5c1110315f803e4000b07","metadata":{"sensorMountType":{}}},"type":"add"}

app:462026-05-03 05:10:34.339 PM

debug

No child sensor or camera device found for ID 69c5c1110315f803e4000b07; skipping

app:462026-05-03 05:10:34.337 PM

debug

parseNvrJson()

app:462026-05-03 05:10:34.335 PM

debug

Parsed JSON: [item:[metadata:[sensorMountType:[:]], start:1777853433494, end:1777853435343, id:69f7e3f901f06003e410a231, type:sensorOpened, device:69c5c1110315f803e4000b07, modelKey:event], type:update]

app:462026-05-03 05:10:34.332 PM

debug

componentParse: {"item":{"id":"69f7e3f901f06003e410a231","modelKey":"event","type":"sensorOpened","start":1777853433494,"end":1777853435343,"device":"69c5c1110315f803e4000b07","metadata":{"sensorMountType":{}}},"type":"update"}

app:462026-05-03 05:10:32.504 PM

debug

No child sensor or camera device found for ID 69c5c1110315f803e4000b07; skipping

app:462026-05-03 05:10:32.502 PM

debug

parseNvrJson()

app:462026-05-03 05:10:32.500 PM

debug

Parsed JSON: [item:[metadata:[sensorMountType:[:]], start:1777853433494, end:null, id:69f7e3f901f06003e410a231, type:sensorOpened, device:69c5c1110315f803e4000b07, modelKey:event], type:add]

app:462026-05-03 05:10:32.498 PM

debug

componentParse: {"item":{"id":"69f7e3f901f06003e410a231","modelKey":"event","type":"sensorOpened","start":1777853433494,"end":null,"device":"69c5c1110315f803e4000b07","metadata":{"sensorMountType":{}}},"type":"add"}

2

As noted in the UI, the sensor piece is currently in beta (it was just introduced in platform 2.5.0) and supports only motion-capable sensors:

UI screenshot: Only motion-capable sensors are currently supported
UI screenshot: Only motion-capable sensors are currently supported743×117 6.92 KB

So, the correct way to phrase this is as a feature request, not "remediation" -- it's just doing what it says it does. :slight_smile:

But fortunately, additional sensor types and additional events for motion-capable sensors are planned for future releases. As usual, there is no guaranteed timeline.

3

In the meantime you could try a community Unifi Protect integration... that does support the Entry sensor (and others). Although not the Relay yet (no data samples).

4

@snell - I use your integration and run it on other jobs. I agree, it works. Just was trying to normalize to hubitat listed integrations. If they cannot get a timely fix, I will lean back to your great work!

Cheers!

5

Again, this is a actually a feature request. :wink: But it's on the list!

6

@bertabcd1234 - Thanks for the reply and look forward to it!

7

Ah (glad it works for you)!

In any case, that is why I mentioned one in the meantime. @bertabcd1234 will get it added, I am sure, but there is a lot of stuff (as always) going with Hubitat and only so many people. Whereas most community developers have a "niche" that they are more focused on.

8

FYI: contact sensors, among others, are now supported in release 2.5.0.140, an update to 2.5.0 currently in beta, that is likely be released soon if you are not in beta.

As before, this piece of the integration itself (regardless of platform release status) is still in beta, but there should be enough data -- if all logging is enabled -- to troubleshoot if not.