Bug: hass.agent client side issues with notifications [distinct from 2024.4.5 update notifications issue] #80
Comments
|
That is strange, first thing that comes to my mind is that notifications for forked HASS.Agent version may be disabled in windows settings (Settings->Notifications and actions) but then it produces something like this: The difference between original and forked version is LAB02-Research#18 (notification library change from "UWP.Toolkit" to "Windows APP SDK") - some users experienced silent crashes on some Windows 11 versions with UWP.Tookit. Did you do any kind of modification to your systems? (privacy scripts etc) |
|
yea that was my initial guess as well, but i confirmed before posting that it shows up as the same app in the windows notifications settings and is enabled.
modifications -- startallback is the only thing i can think of that i use that could conceivably be interfering. i used the original hass agent + start all back for several years without issue, but i suppose that doesn't necessarily mean it'll play nice with this new fork.
in any case, that's only on my windows 11 machine so -- i'm also having issues on my w10 laptop and don't have starall back installed there (or anything else really -- it is my work computer so i keep it very stock).
that said, i didn't specifically check the logs on all three machines so its possible i'm having one issue on the w10 laptop and a separate issue on my w11 pcs. i'll look at all 3 logs tomorrow and report back.
…--
rob lee
m: 310.431.1619
________________________________
From: amadeo-alex ***@***.***>
Sent: Friday, May 3, 2024 2:32:43 AM
To: hass-agent/HASS.Agent ***@***.***>
Cc: robertoleonardo ***@***.***>; Author ***@***.***>
Subject: Re: [hass-agent/HASS.Agent] Bug: hass.agent client side issues with notifications [distinct from 2024.4.5 update notifications issue] (Issue #80)
That is strange, first thing that comes to my mind is that notifications for forked HASS.Agent version may be disabled in windows settings (Settings->Notifications and actions) but then it produces something like this:
2024-05-03 11:26:27.298 +02:00 [WRN] [NOTIFIER] Showing notifications might fail, reason: DisabledForApplication
The difference between original and forked version is LAB02-Research#18<LAB02-Research#18> (notification library change from "UWP.Toolkit" to "Windows APP SDK" - some users experienced silent crashes on some Windows 11 versions.
Did you do any kind of modification to your systems? (privacy scripts etc)
—
Reply to this email directly, view it on GitHub<#80 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADELGE5EP4QI3HLGEF6B6ZTZANKTXAVCNFSM6AAAAABHER3LOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJSGY2DKMRVGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Additional link regarding the elevated/admin programs and app sdk notifications - https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/app-notifications/app-notifications-quickstart?tabs=cs |
|
ah ha - your ideas made me remember: i have UAC disabled. i just reenabled and rebooted and, sure enough, notifications work. good call. that's a bummer - i cannot stand UAC and, given the choice between living with the stale version of hass.agent or keeping uac enabled for notifications, i'm going to choose to stay with the old hass.agent. we've reached the outer limits of my technical know-how so i have no idea -- is this just something that's never gonna change and i'm going to have to live with it, or might there be a way for notifications to be made to work without forcing me to keep uac enabled? |
|
The question if it's not going to change can be separated into two:
There is however other option you can try. There are ways to launch program as "non-elevated" but I don't think those will work with UAC disabled. One more thing that comes to my mind, can you right click the "HASS.Agent.exe" (not the shortcut), then "Properties", "Compatibility" and see if the "Run as administrator" is checked? |
|
yea i've just spent the last two hours figuring out how to run unelevated
with uac disabled -- most of the nirsoft and other third party utilities
that are supposed to let you run unelevated don't do so when uac is
disabled, but i did finally figure out a way forcing unelevated privileges
(i had to create a dummy local user account and then use psexec/runas).
Alas, even though it shows the process as running unelevated in taskmanager
-- notifications still don't work.
oh well! i'll survive. thanks for the explanation and all your efforts --
totally get it, and i totally appreciate it! i only need notifications on
my main pc -- so i'll probably just leave the original version installed
there, and then have the fork running on my other two
…On Fri, May 3, 2024 at 4:03 AM amadeo-alex ***@***.***> wrote:
The question if it's not going to change can be separated into two:
1. Is m$ going to support notifications in elevated application? (just
to be clear, I find the restriction laughable but I've learned that
sometimes they just don't give)
2. Is HASS.Agent (we as a fork) going to handle it somehow? This is a
longer answer, the only way I can see it happening is for me to abstract
all notification code and then have both "UWP.Toolkit" and "Windows APP
SDK" as a selectable option for the users. This however is simpler said
than done not mentioning that most likely there won't ba a feature parity
between those two - TL;DR: time & effort
There is however other option you can try. There are ways to launch
program as "non-elevated" but I don't think those will work with UAC
disabled.
One more thing that comes to my mind, can you right click the
"HASS.Agent.exe" (not the shortcut), then "Properties", "Compatibility" and
see if the "Run as administrator" is checked?
—
Reply to this email directly, view it on GitHub
<#80 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADELGE5VFDYFVV3EWC645SDZANVGLAVCNFSM6AAAAABHER3LOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJSG44DANRYGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
rob lee
m: 310.431.1619
|
Describe the bug
i was on the original LAB02 Version of HASS Agent until i started having the integration side notification issue that everyone else has had with the recent ha update. in the process of sorting that out, i learned about this fork for the window client and made the transition [sidenote: thanks for keeping this project alive!]
i was able to fix the server side notifications error with the modifications to init.py described in the related issue, but now i'm realizing that notifications don't work client side either. the "test notifications" button doesn't give me anything. my logs are below.
i just downgraded to the lab02 version again and the test notifications button works again -- so it doesn't appear to be anything relating to my windows settings.
this is what my log says on multiple machines i've tried it on
Misc info (please complete the following information):
Please check what's applicable (multiple answers possible):
The text was updated successfully, but these errors were encountered: