remote_homeassistant: Remote lock not working

running home-assistant-remote latest. Both instances on the same LAN subnet

Slave has zwave locks paired using Open ZWave beta (but the behaviour was the same with the traidtionnal ZWave integration)

config is :

remote_homeassistant:
  instances:
  - host: 192.168.1.249
    port: 8123
    access_token: !secret access_token
    entity_prefix: cabs_
    subscribe_events:
      state_changed
        - service_registered
        - zwave.network_ready
        - zwave.node_event
    include:
      domains:
      - sensor
      - switch
      - zwave
      - lock
      - climate
      entities:
      - binary_sensor.rpi_power_status

When a ZWave lock is asked to lock or unlock Home Assistant fires a message saying Call to lock/unlock service failed.

I’ve tried a workaround by putting the slave machine interface in panel : panel_iframe:

  cabins:
    title: 'Cabins'
    url: 'https://externalURL.duckdns.org/lovelace/default_view'
    icon: mdi:home-group

but I’m facing a authentification problem as when the slave interface comes in the screen it asks for a login. I would like it to not ask and use the authentication token (or any other means) so that the end user of the interface doesn’t have to login twice (hard to explain why there’s two logins). If there’s a way to do that or to make the lock.unlock service work I’ll be happy to know how to do it.

Nothing noticable in HA logs nor in Supervisor.