addons
addons copied to clipboard
rpc_shutdown not working for win11 computer
Describe the issue you are experiencing
The add-on works for my win10 computers, but not my win11 computer (same microsoft account same login). The error message in the add-on log are: [20:19:37] INFO: Read alias: Laptop [20:19:38] INFO: Shutdown Laptop -> 192.168.1.246 Could not connect to server 192.168.1.246 Connection failed: NT_STATUS_CONNECTION_REFUSED Could not connect to server 192.168.1.246 Connection failed: NT_STATUS_CONNECTION_REFUSED [20:19:39] ERROR: Shutdown failed:
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
RPC Shutdown
What is the version of the add-on?
Current version: 2.5
Steps to reproduce the issue
- setup the action to shutdown my computers in an automation
- the windows 10 computer shutdown
- the 2 windows 11 don't, and the error is shown in logs connection refused ...
System Health information
System Information
| version | core-2025.5.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.13.3 |
| os_name | Linux |
| os_version | 6.6.74-haos-raspi |
| arch | aarch64 |
| timezone | America/Toronto |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| HACS Data | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 2.0.5 |
| Stage | running |
| Available Repositories | 2015 |
| Downloaded Repositories | 28 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | April 22, 2026 at 20:00 |
| relayer_connected | true |
| relayer_region | us-east-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | true |
| google_enabled | true |
| cloud_ice_servers_enabled | true |
| remote_server | us-east-1-0.ui.nabu.casa |
| certificate_status | ready |
| instance_id | 2c2063d9fbed470983aba2ed17492a56 |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 15.2 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2025.05.3 |
| agent_version | 1.7.2 |
| docker_version | 28.0.4 |
| disk_total | 234.3 GB |
| disk_used | 25.2 GB |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | |
| board | rpi5-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Get HACS (1.3.1), File editor (5.8.0), openWakeWord (1.10.0), Piper (1.5.4), Whisper (2.5.0), Matter Server (8.0.0), ESPHome Device Builder (2025.5.2), Terminal & SSH (9.17.0), Samba share (12.5.1), Assist Microphone (1.3.0), RPC Shutdown (2.5), Firefox (1.5.0), Firefox (Edge) (1.5.0), Docker Wyze Bridge (2.10.3), Speech-to-Phrase (1.3.0), Z-Wave JS (0.13.1), Plex Media Server (3.6.4), Vaultwarden (Bitwarden) (0.24.1), Mosquitto broker (6.5.1) |
Dashboards
| dashboards | 10 |
|---|---|
| resources | 8 |
| views | 56 |
| mode | storage |
Network Configuration
| adapters | lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethc0cfb69 (disabled), veth8333d38 (disabled), veth45ec02f (disabled), veth6d42a1a (disabled), vethfb3095b (disabled), veth6100eef (disabled), veth0d10c5c (disabled), veth9cb1926 (disabled), vethcac6b8f (disabled), veth3bc0078 (disabled), veth9bd0f8d (disabled), veth4ccce66 (disabled), veth7cf0625 (disabled), veth5b4dae2 (disabled), vethde9686f (disabled), vethbe76fee (disabled), vethfaaf948 (disabled), veth9e9fc8a (disabled) |
|---|---|
| ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.1.194/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethc0cfb69 (), veth8333d38 (), veth45ec02f (), veth6d42a1a (), vethfb3095b (), veth6100eef (), veth0d10c5c (), veth9cb1926 (), vethcac6b8f (), veth3bc0078 (), veth9bd0f8d (), veth4ccce66 (), veth7cf0625 (), veth5b4dae2 (), vethde9686f (), vethbe76fee (), vethfaaf948 (), veth9e9fc8a () |
| ipv6_addresses | lo (::1/128), end0 (fd83:984d:edae:e9e1:b463:be7f:3b70:31c7/64, fe80::6dd1:3ab5:3e9b:5192/64), hassio (fe80::584e:ecff:feb9:5fad/64), docker0 (fe80::54bb:a7ff:fe14:6d1e/64), vethc0cfb69 (fe80::a068:5dff:fe5a:1981/64), veth8333d38 (fe80::78e7:4ff:fef1:ba04/64), veth45ec02f (fe80::88ea:dbff:fed4:2d76/64), veth6d42a1a (fe80::b808:76ff:fecc:60ad/64), vethfb3095b (fe80::10c2:23ff:fe76:cc7a/64), veth6100eef (fe80::4c27:8dff:fe40:1cfe/64), veth0d10c5c (fe80::34fe:b4ff:fedf:7812/64), veth9cb1926 (fe80::897:f3ff:fe8b:ad6f/64), vethcac6b8f (fe80::dc7c:35ff:fe1a:248f/64), veth3bc0078 (fe80::d042:acff:fe71:a7ee/64), veth9bd0f8d (fe80::54ae:81ff:fefa:dd68/64), veth4ccce66 (fe80::e0db:c4ff:feaa:e195/64), veth7cf0625 (fe80::a897:3bff:fe28:6547/64), veth5b4dae2 (fe80::30ce:4fff:fe77:7008/64), vethde9686f (fe80::607e:13ff:fef4:850c/64), vethbe76fee (fe80::e4a9:72ff:fe9a:ad8a/64), vethfaaf948 (fe80::878:1dff:fe1f:2a3e/64), veth9e9fc8a (fe80::4c7f:3dff:fe01:214a/64) |
| announce_addresses | 192.168.1.194, fd83:984d:edae:e9e1:b463:be7f:3b70:31c7, fe80::6dd1:3ab5:3e9b:5192 |
Recorder
| oldest_recorder_run | May 27, 2025 at 00:19 |
|---|---|
| current_recorder_run | June 7, 2025 at 13:22 |
| estimated_db_size | 983.12 MiB |
| database_engine | sqlite |
| database_version | 3.48.0 |
Sonoff
| version | 3.8.2 (c4b6fda) |
|---|---|
| cloud_online | 1 / 1 |
| local_online | 1 / 1 |
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
[20:19:37] INFO: Read alias: Laptop
[20:19:38] INFO: Shutdown Laptop -> 192.168.1.246
Could not connect to server 192.168.1.246
Connection failed: NT_STATUS_CONNECTION_REFUSED
Could not connect to server 192.168.1.246
Connection failed: NT_STATUS_CONNECTION_REFUSED
[20:19:39] ERROR: Shutdown failed:
Additional information
No response
I’m experiencing the same issue—have you found a solution? This feature was very important to me.
I’m experiencing the same issue—have you found a solution? This feature was very important to me.
I have not sadly, and I am not sure if the developer of this add-on is still active, so we might be out of luck
Important update! Enabling WMI in Firewall does not work. Instead, enable "Remote Service Management".
I am pretty sure I did that, but to triple check, can you provide more details on location of this setting?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.