-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: LoggedUser does not save or work #168
Comments
Please hold... |
Did it work, problem solved? |
Can you send me the exceptions? I agree that it's useful to know who's actually using the machine, might need to make a seperate sensor for that. |
Its only done it a couple of times after I installed the beta, I will try and find them and send them along. |
Hey @shuntfield, is this still an issue with the latest release? |
@LAB02-Admin I haven't had chance to check yet, I don't know if I am configuring the satellite sensor right. |
I'm not sure that I am configuring the sensor correctly or if HASS Agent does what I want it to do: The Top one is the Satellite service, it shows what users are actually logged into the machine, the bottom one is IOT Link. What IOT Link shows is the user that is currently using the machine, if its on the login screen then it shows "system" so if you look at the coloured bands, you see on IOT link Purple which is "system" and Magenta which is "Home User" and "graha" when I am logged in on HASS satellite as I am logged in and also home user I get both, not just one. It might be useful in another context but I only want to see what actual user is using the computer. If that makes sense! The Exception error hasn't appeared since the first time I got one. Hope this helps! |
Yea I'm getting same behaviour shows pc name not the user when used at satellite sensor. The local sensor works OK but only works for who installed hassagent If another user logs in the locals show nothing. |
You're right @shuntfield, I forgot the actual-logged-on part, created a ticket so I won't forget: hassagent-166 Thanks @blair287, I'll look into that as well |
Great stuff 👍🏻 |
Should be fixed in the latest beta if you want to test: |
@LAB02-Admin yup just tested it, "LoggedUser" and it works fine, it swaps to "None" when no user is logged in, but that is fine, I can use that - great stuff! |
Please make sure your bug isn't already listed on HASS.Agent's issue tracker:
https://lab02research.youtrack.cloud/
There's a list of open bugs & features on the right. On the left you can see what's being worked on, what's planned and what's ready for the next release.
If you're not sure, don't worry, just go ahead and we'll discuss :)
Describe the bug
Adding the sensor "LoggedUser" in the satellite service doesn't seem to work, when I add it it generates an error in the log, and although it appears added nothing is sent via MQTT and when you exit and return to the Satellite Service Config page, the sensor is gone. Readding it results in the same.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect the sensor to return the value of the current logged in user, if no user is logged in "SYSTEM"
If the same sensor is added in hass agent, it saves but the output is meaningless, because the sensor does not work when a user is not logged in, and also it does not change when the user is changed.
Screenshots


If applicable, add screenshots to help explain your problem.
Misc info (please complete the following information):
Please check what's applicable (multiple answers possible):
Additional context
Add any other context about the problem here.
log.txt
Logs
If possible, please provide the logs of HASS.Agent and - if applicable - the Satellite Service. You can find HASS.Agent's logs by going to the main window, then
Configuration
->Logging
->open logs folder
. The Satellite Service's logs are in the same window, but theSatellite Service
tab ->open service logs folder
. If you want, you can mail them to [email protected]The text was updated successfully, but these errors were encountered: