RPC shutdown does not generate logs

Third party integrations
1

Hello all,

Today, I have tried installing the RPC Shutdown add-on on my Home Assistant Core 245. However, although the add-on itself installs fine, the add-on does not seem to be working at all. As no logs are being generated anywhere, I have no idea what is happening. Also, no core logs are being generated.

image
image1668×405 4.78 KB

Personally, I was just playing around with the add-on, so this is not really a big problem for me, but this might be a general problem related to the 245 update?

Kind regards,

2

I get logs OK:

[14:32:26] INFO: Read alias: acer
[14:32:28] INFO: Shutdown acer -> 172.24.1.230
[14:32:29] INFO: Read alias: dell1
[14:32:30] INFO: Shutdown dell1 -> 172.24.1.167
Could not connect to server 172.24.1.167
Connection failed: NT_STATUS_HOST_UNREACHABLE
Could not connect to server 172.24.1.167
Connection failed: NT_STATUS_HOST_UNREACHABLE
[14:32:36] ERROR: Shutdown fails -> 
[14:32:37] INFO: Read alias: laptop
[14:32:38] INFO: Shutdown laptop -> 172.24.1.206

They don’t survive a HA reboot, though.

3

I have a similar issue

I found similar posts there

4

I was finally able to get this working! Turns out I did not read the instructions carefully enough :slight_smile:

I presumed the RPC Shutdown logs would generate logs as soon as the addon is started, but it only starts logging when an actual trigger for a shutdown is sent.

So once I triggered a restart using the services as indicated in the documentation, I was able to shut down my pc.

5

Has anyone tried this on a domain computer?

If I try the following on the configuration I get this error message:

computers:
  - alias: Laptop
    address: 192.168.2.87
    credentials: mydomainname\username%mypassword
    delay: 0
    message: >-
      Home Assistant is shutting down this PC. This cannot be canceled. Please
      save your work!



[11:12:17] INFO: Read alias: Laptop
[11:12:17] INFO: Shutdown Laptop -> 192.168.2.87
Could not initialise pipe winreg. Error was NT_STATUS_OBJECT_NAME_NOT_FOUND
[11:12:19] ERROR: Shutdown fails ->

If I try the following configuration I get a different error.

computers:
  - alias: Laptop
    address: 192.168.2.87
    credentials: myusername%mypassword
    delay: 0
    message: >-
      Home Assistant is shutting down this PC. This cannot be canceled. Please
      save your work!


[11:28:07] INFO: Read alias: Laptop
[11:28:08] INFO: Shutdown Laptop -> 192.168.2.87
Could not connect to server 192.168.2.87
The username or password was not correct.
Connection failed: NT_STATUS_LOGON_FAILURE
Could not connect to server 192.168.2.87
The username or password was not correct.
Connection failed: NT_STATUS_LOGON_FAILURE
[11:28:09] ERROR: Shutdown fails ->

Thanks in advance for any help

6

Hi @laca75tn, Did you ever resolve this? I am having similar issues.

Update: I was able to get this working by doing the following

Windows Firewall:

File and Printer Sharing (Echo Request - ICMPv4-In) (Domain and Private)

Remote Service Management (NP-In) (Domain and Private)

Services:

Remote Registry (Service → Automatic)

I am shutting down domain PC’s

computers:
  - alias: TEST-PC
    address: 192.168.47.172
    credentials: DOMAIN\user%pass
    delay: 180
    message: >-
      Home Assistant is shutting down this PC. This cannot be canceled. Please
      save your work!
2 Likes