search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.39k stars 30.29k forks source link

Risco Cloud cannot connect #94124

Closed pvdhelm1974 closed 4 months ago

pvdhelm1974 commented 1 year ago

The problem

i get this error when i connect to my risco panel.

Opnieuw proberen in te stellen: {'result': 72, 'validationErrors': None, 'errorText': None, 'errorTextCodeID': None, 'status': 200, 'response': None}

i paid for the cloud service and it's active on my phone and my wifes phone

What version of Home Assistant Core has the issue?

2023.5.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

joostlek commented 1 year ago

Can you give more context by filling in the issue template? What are the reproduction steps etc

home-assistant[bot] commented 1 year ago

Hey there @onfreund, mind taking a look at this issue as it has been labeled with an integration (risco) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `risco` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign risco` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)

risco documentation risco source (message by IssueLinks)

OnFreund commented 1 year ago

Result 72 means that the panel is not accessible to the cloud system. Usually an intermittent network error.

pvdhelm1974 commented 1 year ago

My panel is accesible to the cloud system because i can reach it with my irisco app on my phone

Met vriendelijke groet,

Patrick van den Helm @.***

Van: On Freund @.> Verzonden: Tuesday, June 6, 2023 9:30:53 PM Aan: home-assistant/core @.> CC: Patrick van den Helm @.>; Author @.> Onderwerp: Re: [home-assistant/core] risco cannot connect (Issue #94124)

Result 72 means that the panel is not accessible to the cloud system. Usually an intermittent network error.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/94124#issuecomment-1579333167, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR4Q722KBLXDJX4KKAAD5G3XJ6AO3ANCNFSM6AAAAAAY4TBFIA. You are receiving this because you authored the thread.Message ID: @.***>

krism23 commented 1 year ago

Experiencing the same problem after update to HA 2023.6, before the upgrade everything worked fine

Whixter commented 1 year ago

Experiencing the same problem after update HA 2023.6 Before everything worked fine. Tried to change the polling time to check if any block has been implemented by Risco but nothing changed. Automations cannot work anymore as entities intermittendly become unavailable.

OnFreund commented 1 year ago

@home-assistant rename Risco Cloud cannot connect

OnFreund commented 1 year ago

I'm not really sure what can be the cause of a regression - the integration hasn't changed in months, so it's either:

  1. A different change in HA that affected the integration
  2. A change in Risco cloud

I no longer have a cloud subscription - can anyone confirm that it's still working with HA 2023.5?

seederp2p commented 1 year ago

Hi!

I'm getting this error:

Logger: homeassistant.components.risco Source: helpers/update_coordinator.py:229 Integration: Risco (documentation, issues) First occurred: 10:05:40 AM (2 occurrences) Last logged: 10:06:42 AM

Error fetching risco data: {'result': 72, 'validationErrors': None, 'errorText': None, 'errorTextCodeID': None, 'status': 200, 'response': None}

It happens from times to times which my lead to problems with automations (example, if I have a conditition where it checks if the status changes from "armed away" to "disarmed"

I'm using 2023.8.2

OnFreund commented 1 year ago

This error usually indicates a loss of connection between the cloud and your local Risco system.

seederp2p commented 1 year ago

This error usually indicates a loss of connection between the cloud and your local Risco system.

I'm monitoring my IP module and it doesn't lose local connection.

Maybe it would be better to implement a "retry" count?

Otherwise it won't be possible to implement automation based on the status change like from "armed away" to "disarmed" because sometimes it will be in the state "Unavailable"

OnFreund commented 1 year ago

Not sure how your monitoring is implemented and whether it's a good approximation of the cloud connection, but I can say that this error is returned from the Risco cloud when it can't access the panel.

I no longer have an active cloud subscription, but if you create a PR with a retry mechanism I'm happy to review it.

Additionally, if this is a concern, I would consider switching to the local flavor of the integration, which doesn't have this problem, and is also faster.

Whixter commented 1 year ago

Indeed this is not a connection issue with the cloud as the cloud app works smoothly without disconnection.I also have Ip and gsm module as a Backup, thus I guess this could be due to some cloud protection.Inviato da iPhoneIl giorno 17 ago 2023, alle ore 13:03, seederp2p @.***> ha scritto:

This error usually indicates a loss of connection between the cloud and your local Risco system.

I'm monitoring my IP module and it doesn't lose local connection. Maybe it would be better to implement a "retry" count? Otherwise it won't be possible to implement automation based on the status change like from "armed away" to "disarmed" because sometimes it will be in the state "Unavailable"

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

OnFreund commented 1 year ago

Indeed this is not a connection issue with the cloud as the cloud app works smoothly without disconnection.

The app doesn't monitor the status of the alarm 24/7, so won't be affected by an intermittent loss of connection.

seederp2p commented 1 year ago

Not sure how your monitoring is implemented and whether it's a good approximation of the cloud connection, but I can say that this error is returned from the Risco cloud when it can't access the panel.

I no longer have an active cloud subscription, but if you create a PR with a retry mechanism I'm happy to review it.

Additionally, if this is a concern, I would consider switching to the local flavor of the integration, which doesn't have this problem, and is also faster.

I’m monitoring my IP module on my network management system and also on my firewall. I don’t see any network drops.

I’m not a developer so I’m afraid I can’t create such PR

seederp2p commented 1 year ago

Not sure how your monitoring is implemented and whether it's a good approximation of the cloud connection, but I can say that this error is returned from the Risco cloud when it can't access the panel. I no longer have an active cloud subscription, but if you create a PR with a retry mechanism I'm happy to review it. Additionally, if this is a concern, I would consider switching to the local flavor of the integration, which doesn't have this problem, and is also faster.

I’m monitoring my IP module on my network management system and also on my firewall. I don’t see any network drops.

I’m not a developer so I’m afraid I can’t create such PR

I'm available to provide enough data / testing to get this ok.

@OnFreund , are you available to improve this integration with me providing the data you need?

OnFreund commented 1 year ago

I doubt that remote debugging is going to help here - I'm not sure what data is going to help. Your best bet is to find a developer with an active cloud subscription who can build some mechanism that ignores intermittent failures. The other option is to find the source of disconnections in your network, but that's not going to work 100% - it's still going to happen every now and then based on my experience with their cloud.

OnFreund commented 1 year ago

And of course, you can always switch to the local flavor of the integration, which is faster and more reliable.

seederp2p commented 1 year ago

Contributor

Thanks for your reply.

In this case I think that implementing a simple "retry" for the polling would "solve" the issue because, in fact, all the operations of arming and disarming works fine. It just looks like, sometimes their cloud service is not responding in a proper manner.

There are no disconnections on my network. My troubleshoot makes me believe that the problem is on their cloud services.

Regarding the local configuration, it didn't work in my case, don't really know why.

issue-triage-workflows[bot] commented 10 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

seederp2p commented 10 months ago

To anyone who would like to have a more reliable information regarding the alarm state (assuming that the disconnects are something that we can't fight for the momment) I created this template:

- platform: template
  sensors:
    alarm_state:
      friendly_name: "Alarm State"
      value_template: >-
        {% if is_state('alarm_control_panel.alarm', 'unavailable') %}
          {{ states('sensor.alarm_state') }}
        {% elif is_state('alarm_control_panel.alarm', 'armed_away') %}
          Armed away
        {% elif is_state('alarm_control_panel.alarm', 'disarmed') %}
          Disarmed
        {% else %}
          {{ states('sensor.alarm_state') }}
        {% endif %}

This way, you can use this template as a sensor state that ignores the "unavailable" state. So you can use it in your automations like "change from armed away to disarmed" without worring about the fact that it might be "unavailable".

This is not a perfect solution... but in my use case it works just fine.

Cheers.

issue-triage-workflows[bot] commented 7 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ilmisu commented 7 months ago

hi all, I've updated my Risco ProSys main Board, and the status with the cloud communication is even worse than before. the board is cable wired, not wifi, and constantly I get partitions not available, this way: image frankly speaking is not reliable anymore as integration. plus, I can't use the local polling configuration, with an Unknown error, due to the missing Proxy or something similar. any hint in how to make it more stable and reliable?

OnFreund commented 7 months ago

I can't use the local polling configuration, with an Unknown error, due to the missing Proxy or something similar

Please be more specific.

ilmisu commented 7 months ago

I can't actually, the error is only "unknown error" and I found something about this browsing other users' issues... I'm sorry. If you tell me how I could provide more info...

Il Mer 21 Feb 2024, 10:01 On Freund @.***> ha scritto:

I can't use the local polling configuration, with an Unknown error, due to the missing Proxy or something similar

Please be more specific.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/94124#issuecomment-1956180951, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMBVO2OMV7MMPQCXDX4IISDYUWZX3AVCNFSM6AAAAAAY4TBFICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWGE4DAOJVGE . You are receiving this because you commented.Message ID: @.***>

ilmisu commented 7 months ago

I can't use the local polling configuration, with an Unknown error, due to the missing Proxy or something similar

Please be more specific.

Hey man, I'm sorry, I was assuming that the PIN code to be configured onto local integration was the site code, but is the default one for risco panel.... So now I got my alarm system locally integrated with HA. :)

OnFreund commented 7 months ago

Great. I think you'll find it much better than the cloud based integration.

seederp2p commented 7 months ago

I can't use the local polling configuration, with an Unknown error, due to the missing Proxy or something similar

Please be more specific.

Hey man, I'm sorry, I was assuming that the PIN code to be configured onto local integration was the site code, but is the default one for risco panel.... So now I got my alarm system locally integrated with HA. :)

What Pin is that?

ilmisu commented 7 months ago

Is 5678 as per help on HA site about the integration.

Il Mer 21 Feb 2024, 17:04 seederp2p @.***> ha scritto:

I can't use the local polling configuration, with an Unknown error, due to the missing Proxy or something similar

Please be more specific.

Hey man, I'm sorry, I was assuming that the PIN code to be configured onto local integration was the site code, but is the default one for risco panel.... So now I got my alarm system locally integrated with HA. :)

What Pin is that?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/94124#issuecomment-1957101793, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMBVO2KMUMZORIQB5HZCBX3YUYLHDAVCNFSM6AAAAAAY4TBFICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXGEYDCNZZGM . You are receiving this because you commented.Message ID: @.***>

seederp2p commented 7 months ago

It says that "this access code is NOT the same as the installer/subinstaller code, and with older models, you might need to either disconnect your system from the cloud, or set up a proxy that will allow you to connect both locally and via the cloud."

In what models is it necessary to disconnect from the cloud.

I've a third party company that needs cloud access. They basically monitor my infrastructure so this is something I can't remove...

OnFreund commented 7 months ago

In what models is it necessary to disconnect from the cloud.

I don't know which models supports two connections and which only one (otherwise I would have added it to the docs).

I've a third party company that needs cloud access. They basically monitor my infrastructure so this is something I can't remove...

Dispatch companies usually have other means of connecting to the panel (GSM, LoRa, etc...). Connecting over cloud is very error prone.

issue-triage-workflows[bot] commented 4 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.