Universal Devices ISY/IoX Integration not controlling a lock

[frr032]

The problem

Can't control a i994 lock entity (lock.foyer_front_door_lock) from home assistant. It's controllable from the i994 admin interface.
When I attempt to lock/unlock the lock from HA it displays a message; Failed to lock XX XX XX 1, it is not a lock node.

What version of Home Assistant Core has the issue?

core-2025.3.4

What was the last working version of Home Assistant Core?

unknown

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Universal Devices ISY/IoX

Link to integration documentation on our website

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

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:245
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 1:36:56 PM (1 occurrences)
Last logged: 1:36:56 PM

[140528952449424] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2794, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2837, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/lock/__init__.py", line 221, in async_handle_lock_service
    await self.async_lock(**self.add_default_code(kwargs))
  File "/usr/src/homeassistant/homeassistant/components/isy994/lock.py", line 85, in async_lock
    raise HomeAssistantError(f"Unable to lock device {self._node.address}")
homeassistant.exceptions.HomeAssistantError: Unable to lock device XX XX XX 1

=================================================================

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:245
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 1:36:56 PM (1 occurrences)
Last logged: 1:36:56 PM

[140528952449424] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2794, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2837, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/lock/__init__.py", line 221, in async_handle_lock_service
    await self.async_lock(**self.add_default_code(kwargs))
  File "/usr/src/homeassistant/homeassistant/components/isy994/lock.py", line 85, in async_lock
    raise HomeAssistantError(f"Unable to lock device {self._node.address}")
homeassistant.exceptions.HomeAssistantError: Unable to lock device XX XX XX 1

=========================================================================================
Logger: pyisy
Source: components/isy994/lock.py:84
First occurred: 1:36:56 PM (1 occurrences)
Last logged: 1:36:56 PM

Failed to lock XX XX XX 1, it is not a lock node.

Additional information

When I change the status of the lock in the UD ISY i994 interface the lock changes and HA shows the correct statyus (unlocked) but I cannot control it from the HA interface.

FYI: I have reloaded the US ISY integration many times and restarted HA many times.

[home-assistant]

Hey there @bdraco, @shbatm, mind taking a look at this issue as it has been labeled with an integration (isy994) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of isy994 can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign isy994 Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

isy994 documentation
isy994 source
_{^{(message by IssueLinks)}}

[shbatm]

@home-assistant add-label problem in dependency

[shbatm]

@frr032 Looks like this is for an Insteon 2862-222 Lock Controller, is that correct? If so, I think I know what the issue is--the Insteon Device Category (0x0F) is missing from the check to allow lock/unlock commands.

[frr032]

@frr032 Looks like this is for an Insteon 2862-222 Lock Controller, is that correct? If so, I think I know what the issue is--the Insteon Device Category (0x0F) is missing from the check to allow lock/unlock commands.

Thanks for your reply!! Yes it is a Insteon 2862-222 Lock Controller,

The integration was working at some point. I don't use the front door lock very often via HA so I'm not sure when it became non functional.