-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
email used as "changed_by" #135
Comments
On setup I collect the username of the user HA logs into sector with to use as default user for changing the alarm. It's not excellent but a way to deal with a crapy api in this case. |
There is no reason to set this value ever, all logs have the user information that changed things. This is like an audit of changes to the alarm system. Randomly setting values makes the data completely untrustworthy. |
I don't necessarily agree since the only time it's set manually is when done from HA and therefore we know which user it is. The problem with double state changes will remain so people will have to adjust their automations accordingly. |
Not true, I simply set up a "user" in sector which is "home" with it's own passcode. So at least in my case it should never use that value as sector is returning a username. This worked perfectly fine before and was always the correct value. In what case does sector not return a User that changed the alarm? This is part of the audit logs of what has happened to the alarm. This is my automation:
And then I get messages like:
|
Describe the bug
Recently, not exactly sure when it started, but often the "changed_by" user is my email address which the integration seems to be taking from the integration config rather than the actual values in the logs. Nowhere is email configured as a user in home assistant so this should never be the case.
Version
0.3.8
Expected behavior
Use the information from sector alarm for showing state, don't blend with assumed data from login information or otherwise
Sector always has the "changed by" information as part of the audit trail for the alarm.
The text was updated successfully, but these errors were encountered: