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.4k stars 30.3k forks source link

Risco Intergration not maintaining consistent connection #53079

Closed robertboccia closed 2 years ago

robertboccia commented 3 years ago

The problem

Risco did some updates on the 13th of July to their cloud environment, since then the Risco intergration has seen intermittant connectivity issues to the Risco service.

What is version of Home Assistant Core has the issue?

2021.7.2

What was the last working version of Home Assistant Core?

2021.6.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Risco

Link to integration documentation on our website

https://github.com/home-assistant/core/tree/dev/homeassistant/components/risco

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Error fetching risco data: {'result': 72, 'validationErrors': None, 'errorText': None, 'errorTextCodeID': None, 'status': 200, 'response': None} 8:42:57 AM – (ERROR) Risco - message first occurred at 6:55:11 AM and shows up 46 times

Additional information

No response

OnFreund commented 3 years ago

Thanks for the new issue @robertboccia As I mentioned in the previous one - based on previous reverse engineering, result 72 means lost connectivity between the the Risco system and the Risco cloud. You can also disconnect your system and witness the same error.

Hopefully, a local integration (once we have it), won't suffer from these problems.

OnFreund commented 3 years ago

As for the public cloud API (if it's ever released), I'm not sure it will help in this case.

robertboccia commented 3 years ago

Thanks for the new issue @robertboccia As I mentioned in the previous one - based on previous reverse engineering, result 72 means lost connectivity between the the Risco system and the Risco cloud. You can also disconnect your system and witness the same error.

Hopefully, a local integration (once we have it), won't suffer from these problems.

as you would have seen there are now multiple people having the same issue, so not just me and certainly not related to my lan or outbound internet connectivity.

OnFreund commented 3 years ago

I'm not saying it's related to you, and it definitely could be related to the Risco update. What I'm saying is the the problem is between the Risco system and the cloud, not HA. The HA integration is getting that error from the cloud system.

probot-home-assistant[bot] commented 3 years ago

risco documentation risco source (message by IssueLinks)

PoudNL commented 3 years ago

I also experience connectivity issues with the native Risco App on mobile phone. Time outs occur almost every time and only after a couple of tries, I am able to manage my system. When Risco resolves that problem, this issue will most probably also been resolved

robertboccia commented 3 years ago

@OnFreund i have had word back from risco that all intergration going forward will have to be done via their API, there is a registration process to get access to the API.

pergolafabio commented 3 years ago

are you talking about the cloud api or local api?

i think cloud api is not released yet; my contact told me it should be available in the next risco cloud update 5.x

robertboccia commented 3 years ago

are you talking about the cloud api or local api?

i think cloud api is not released yet; my contact told me it should be available in the next risco cloud update 5.x

Cloud API

pergolafabio commented 3 years ago

is that registration process already active? have you more info about it?

robertboccia commented 3 years ago

I am trying to get detail on how to register but I imagine @OnFreund would have to possibly do this as the owner of this integration. I have asked them for the email contact, and await their response

OnFreund commented 3 years ago

The main question is whether users will have to pay to have this API open.

In any case, I think the local integration might be a better path forward - it's probably more stable since it's harder for them to change, doesn't require a paid plan, and works locally rather than on the cloud (and their cloud is really slow).

pergolafabio commented 3 years ago

yes, local is indeed the best option have you already tried that other project? Do you know if it uses the API? or did he crack the security? please also note, local will not work for everyone with older systems i have an "older" lightsys , with older type of TCP module, that module doesnt open port 1000 when cloud is enabled newer TCP modules do allow port 1000 open with cloud enabled

make sure its in the readme :-)

robertboccia commented 3 years ago

In an ideal world local would be great, given that my risco system so far has cost in excess of 10k usd I'm very concerned about throwing away this investment, so local would mean this isn't money down the drain. However at this stage I'll take anything that works, since my light automations are using the risco passives etc. I have a prosysplus with plenty of out door passives and indoor passives. So it would a huge waste to dump it.

robertboccia commented 3 years ago

@OnFreund drop me your email and I will pass onto risco for them to contact you with regards to api robert.boccia@live.co.za

pergolafabio commented 3 years ago

I'm interested too :-)

Will drop a mail too

robertboccia commented 3 years ago

Response from Risco

They can contact Risco by following the link: https://www.riscogroup.com/content/contact-us

Or you can provide me with the developer's details, and I will pass it onto Risco so they can contact with the developer.

dJos1991 commented 3 years ago

Thanks for the new issue @robertboccia As I mentioned in the previous one - based on previous reverse engineering, result 72 means lost connectivity between the the Risco system and the Risco cloud. You can also disconnect your system and witness the same error.

@OnFreund I've also some errors with code 72 and it will not create the alarm control panel (the binary sensors for the motion detectors are created):

Error while setting up risco platform for alarm_control_panel Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 250, in _async_setup_platform await asyncio.shield(task) File "/usr/src/homeassistant/homeassistant/components/risco/alarm_control_panel.py", line 55, in async_setup_entry for partition_id in coordinator.data.partitions File "/usr/local/lib/python3.9/site-packages/pyrisco/risco.py", line 134, in partitions self._partitions = {p["id"]: Partition(p) for p in self._raw["partitions"]} TypeError: 'NoneType' object is not iterable

I'm not sure the problem is related to my internet connection or just the connection (cable or rj45 connectors) from the alarm to the switch. My switch port is reporting that the link is only 10 Mbit half-duplex. Somebody that can tell me if this is normal or not? It's the lightsys 2, one year old.

pergolafabio commented 3 years ago

Mine is 100 Mbit, not gigabit

OnFreund commented 3 years ago

@dJos1991 Looks like you had connection errors when the integration was loading. Reloading it should bring back the partitions.

robertboccia commented 3 years ago

@OnFreund have you managed to make any progress on the local ?

OnFreund commented 3 years ago

Not really, and I doubt I'll make any soon. Sorry, just don't have the capacity to handle it now.

github-actions[bot] commented 2 years 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.