HASS Agent Notifications Stopped Working
I had notifications working, and now even the local test notification is not showing up.
The logs just state it failed to create the notification, but is no more verbose than that.
I am using a scheduled task to run this as admin (same user who has local admin privileges), seems to work fine when run normally. The admin account and my main account are the same. I am just referring to right clicking and running as admin.
I am running as admin, as a Powershell script I am using needs local admin perms.
12 Replies
Help us Help Others!
To help others find answers, you can mark your question as solved via
Right click solution message -> Apps -> ✅ Mark Solution
Help us Help You!
Please don't delete messages or posts because it makes it impossible to understand what happened. If you don't want your messages to be seen then don't post here.
Please provide us with the version number of your app.
You can find it by clicking the ? at the bottom of the main page and checking under the logo that shows.We will help as soon as possible. While you're waiting you can try the following:
- Checkout the documentation. - Search here in discord for previously solved similar issues.
@Amadeo
o/
can you please provide more context?
for example what are you running as admin?
optimistic-goldOP•2mo ago
im running the hass agent as admin so that a script that checks the result of "powercfg /requests" can be checked.
Solution
That doesn't work, hass.agent is user, satellite is admin
If you need to run an admin script/command you will need a scheduled task
The admin access and Ur user account may look the same but they aren't the same in the programs
That's why you can still do right click run as admin, separate ways of executing
I should correct this, it's not recommended or supported
optimistic-goldOP•2mo ago
I understand the differences now. Sorry for troubling you with something so basic.
Thank you for your help!
That's okay, did you get your commands working?
optimistic-goldOP•2mo ago
I did, the commands were already working when running as admin, so it was as simple as setting up the same sensor in the service config.
One observation though, is that when using the button to test the Powershell sensor in the service config. The output complained of a lack of admin privileges, but it works fine in normal operation as a service sensor.
Does the test button for the service Powershell sensor, not run with the same permissions as the service itself?
Not my expertise, @Amadeo ?
ya, the UI test will run it as your user
not as service (which has system level permissions)