Qualcuno mi può aiutare?
Hello,
I don’t know when but I’ve started to receive random errors:
ERROR (MainThread) [homeassistant.components.risco] Error in Risco library: Risco error: N04
ERROR (MainThread) [homeassistant.components.risco] Error in Risco library: Timeout in command: CLOCK
I mean random because now I don’t have any automation connected to the Alarm, neither bypass on, neither try to perform any action. Do you have any idea about what can be?
I’m getting the clock timeout error as well. Seems to occur approximately every half hour… Everything seems to be working fine though.
those clock commands can be ignored, they are just there to kee connection alive
Hey.
Did you manage to I solve it?
Can’t connect to the local integration.
Disabled cloud. Checked my access code which is 5678
I even connected to the brain with Configuration System.
Any ideas?
Getting error with RID command
Thank you
I am getting this error too.
What is this? Is it like the integration times out when it tries to poll the alarm or is it something else?
Logger: homeassistant.components.risco
Source: components/risco/init.py:97
integration: Risco (documentation, issues)
First occurred: 3:06:06 PM (4 occurrences)
Last logged: 3:40:00 PM
- Error in Risco library: Risco error: N04
- Error in Risco library: Timeout in command: CLOCK
Good Afternoon,
I have a Risco LightSys system and I am having problems with front and rear door sensor, I would be happy to remove them if I can, or even bypass the 2 (in their zone numbers), it just doesn’t seem to be working for me, anybody had any experience with this?
Thank you
Are you trying to bypass while the alarm is armed? That doesn’t work on my system, but I can bypass when it’s disarmed (the Risco app behaves the same way, not just HA)
No so the last 3 nights we have not been able to set just downstairs in the evening, so it is disarmed but I am arming just downstairs, it starts beeping as normal, then carries on beeping as if we have set the whole house (which I haven’t), so I have to run downstairs, when I got to zone status it varies between the 2, front door and back door to say not ready, I tried bypassing the 2 with no joy as the keypad chime disappears and also the kept counts down from 0.01 second but you do have time to go upstairs but doesn’t always work
Are you bypassing or using a specific arming mode? It’s unclear from the description.
It also sounds like there’s some hardware defect.
I am using my master code to access the system, then it comes to bypass, you choose, on time, permanently and then the list of zones comes up, get to the zone, press the house icon with the padlock inside and it turns the No in the top right corner to Yes and then press bottom right button.
When you then go to zone status it does say zone front door bypassed, how do you bypass zones on yours? I realised you have to press the house with padlock to change the no word to yes
It sounds like you’re describing the app or your panel, not HA.
Yes I am trying to bypass 2 zones using my keypad, the RiscoApp I used to have which I don’t anymore didn’t have that function I don’t believe, it went off again last when the front door was disabled and it was set for downstairs only and we went upstairs
OK, this is a discussion about the Risco integration for Home Assistant, but it sounds like you have a problem with your hardware. I would suggest reaching out to your installer.
Thanks for the reply, that’s fine, I cancelled my subscription as they have alarming prices, and charged us for things not done, I called a seperate engineer who quoted £120 for the first hour, don’t suppose he will take a hour, extortion
Thanks
Hi all, I’m in need of support here…
I setup the cloud integration. Arming works, however I can only disarm using the grand master (or installer, or site pin). User codes are rejected in the integration, although they work on the physical keypad.
In the local integration it’s even worse: I can arm the alarm, but no code whatsoever is accepted to disarm it. Again, the codes do work on the keypad, but the integration rejects all of them.
In the logs I can only see this:
2024-05-26 15:46:34.615 WARNING (MainThread) [homeassistant.components.risco.alarm_control_panel] Wrong code entered for disarming
2024-05-26 15:46:42.497 WARNING (MainThread) [homeassistant.components.risco.alarm_control_panel] Wrong code entered for disarming
2024-05-26 15:46:52.033 WARNING (MainThread) [homeassistant.components.risco.alarm_control_panel] Wrong code entered for disarming
Any ideas? Is there a debug mode to get more info?
Thanks!
With both cloud and local, the pin is the one you set the integration up with.
1 Like
Thanks. With the cloud integration, it did accept the Installer code. Now I tested with the local integration and indeed it only accepts the “access code”.
In any case this works now, thanks!
Hi all,
did somebody understood how to retrieve the “ready to arm” status?
Just to better clarify, if some zones are not “off” (e.g. one window open), any automation with automatic arming results in an error “N12” and an abnormal exit from the automation.
In short, I don’t know how to “catch” the exception (to send me a message that the Alarm was not armed), so I’m trying to understand if, in a cleaner way, there is any bynary_sensor which states that Alarm is ready to be armed (e.g. all zones are in off status) without creating a mega-group.
This should give you the list of triggered zones (make sure to replace with the right config entry id):
{{ integration_entities("<config entry id>") | select("match", "binary_sensor.") | reject("search", "_alarmed") | reject("search", "_bypassed") | select('is_state', 'on') | list }}