Closed majkers closed 4 years ago
Please fill out the issue template, you can find it by clicking on New Issue
and then selecting Report a bug with Home Assistant
. Copy and paste the provided template into this already created issue, click preview to take a look at the empty template and then fill out as much as you can. Any additional information can be helpful!
Thanks for understanding :)
Done
Hey there @onfreund, mind taking a look at this issue as its been labeled with an integration (risco
) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
hi, this is an duplicate , already created this issue
R u sure that is the same? according to log it is not. I' d rather @OnFreund judge that.
Yes , seems log is different when reading/writing state, I updated mine also, you can close this one
Sorry, you are right, it's indeed different, sorry for confusion
This error is returned directly from Risco. My guess is it's a permission issue. Risco is very picky about users working concurrently , especially with different permissions. Are you also using the app/website? Also try to see if you disconnect from everything (especially the MQTT version if you had it running), give it an hour (at least 1 full hour), and then try again.
Yes. I arm it with system owner user from risco cloud and I have a separate user created for HA integration. That might be the case... Sometimes I get an error that I can not arm/disarm it from risco cloud when it was armed/disarmed in HA..
My recommendation is to also create a separate non-owner user to use with Risco cloud. Keep your owner user for when you need to make changes to users, etc...
Yeah that's it. I've just armed one partition from HA with simple user and could not disarm it from risco app where I have system owner logged in with info that other session is open and that operation can not be done with 2 different users with different permission level. Anything that can be done in HA besides creating separate non owner user for risco app?
My recommendation is to also create a separate non-owner user to use with Risco cloud. Keep your owner user for when you need to make changes to users, etc...
OK. I close it for now
maybe better to put this in documentation?
BTW it is strange that system owner can not disarm/arm when it was set by "simple" user
@pergolafabio that's a good idea. Can you change the documentation? (really easy, and can be done directly from github - no need to setup a development environment).
@majkers I agree, but unfortunately that's how Risco works š¤·āāļø
done
lets see, what happens, never did a PR before š
https://github.com/home-assistant/home-assistant.io/pull/14551
The problem
After upgrading to HA 0.115 from 0.114.4 while trying to disarm one partition that is armed (via Risco cloud page) and entering PIN code I get an error
Environment
I am using HASSIO on RPi3
Problem-relevant
configuration.yaml
Done via UI
Traceback/Error logs
Additional information
Armin and disarming partition via HA works just fine although if I enter wrong PIN and use glance card I don't get any error...