UniFi Protect lux mapping out of range

[vash2695]

The problem

Getting this error every 10 seconds:

2024-07-22 12:08:34.076 ERROR (MainThread) [uiprotect.api] Exception while running subscription handler
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/uiprotect/api.py", line 860, in emit_message
sub(msg)
File "/usr/src/homeassistant/homeassistant/components/unifiprotect/data.py", line 296, in _async_process_ws_message
self._async_update_device(new_obj, message.changed_data)
File "/usr/src/homeassistant/homeassistant/components/unifiprotect/data.py", line 233, in _async_update_device
self._async_signal_device_update(device)
File "/usr/src/homeassistant/homeassistant/components/unifiprotect/data.py", line 340, in _async_signal_device_update
update_callback(device)
File "/usr/src/homeassistant/homeassistant/components/unifiprotect/entity.py", line 238, in _async_updated_event
self._async_update_device_from_protect(device)
File "/usr/src/homeassistant/homeassistant/components/unifiprotect/number.py", line 273, in _async_update_device_from_protect
self._attr_native_value = self.entity_description.get_ufp_value(self.device)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/uiprotect/utils.py", line 651, in get_top_level_attr
value = getattr(obj, attr)
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/uiprotect/data/devices.py", line 1130, in icr_lux_display
return LUX_MAPPING_VALUES[10 - self.isp_settings.icr_custom_value]
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
IndexError: list index out of range

What version of Home Assistant Core has the issue?

core-2024.7.3

What was the last working version of Home Assistant Core?

core-2024.7.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

unifiprotect

Link to integration documentation on our website

https://www.home-assistant.io/integrations/unifiprotect

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

unifiprotect documentation
unifiprotect source

[darkrain-nl]

This happens to me as well when the settings for nightvision are like so:

I think it has to do with the "under 1" setting.

[vash2695]

I hadn't set any custom settings for night vision, but I did have some custom color settings. Setting those back to default seems to have fixed the issue, but that may mean that anyone using non-default settings on any of their cameras may be having this issue as well.

[BerserkeR-Git]

I have the same issue, looks like you have to reset all custom picture settings but the custom night vision trigger seem to work on 1 lux though, it only crashes the package again if you'd use the new '< 1 lux' setting. So in short, all the custom values should be looked at otherwise the package might crash; IndexError: list index out of range

[shatt3r3d]

Can confirm, this absolutely breaks person detection and causes it to stop after setting night vision settings to "auto" or above "1" (specifically not < 1 lux) it works again. Also I think adding fine-tuning image settings breaks detection so have left it as default for now but there will be so many people trying to figure this out.

I was wondering why after some time had passed why person detection all of a sudden stopped. Turns out after looking at the logs and can confirm the "IndexError: list index out of range" constantly running through the error logs of HA.

This requires a lot of troubleshooting and looking at logs, then googling to find this issue logged on Github- I can say with certainty there are a lot of people in this boat but will blame other aspects of HA if not rectified.

[shatt3r3d]

This happens to me as well when the settings for nightvision are like so:

I think it has to do with the "under 1" setting.

@darkrain-nl This is definitely the case, or at least it has been with me.

I specifically set to < 1 lux so that I have colour footage at all times and did not want it to ever come on as will others who wish to have the same setup.

Once I set it to a number either 1 or above (which increases the chances of night vision kicking in) detections work (as long as I dont have any fine-tuning settings on image settings changed from default either.