Risco problem

[Mpgod80]

The problem

From The log in HA:

2021-12-28 12:57:19 WARNING (MainThread) [homeassistant.components.sensor] sensor.risco_xxxxxxxxxxx_status_events is providing a string for its state, while the device class is 'timestamp', this is not valid and will be unsupported from Home Assistant 2022.2.

What to do?

It is my homealarm Risco.

What version of Home Assistant Core has the issue?

2021.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Risco

Link to integration documentation on our website

https://www.home-assistant.io/integrations/risco

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant[bot]]

risco documentation risco source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

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! _{^{(message by CodeOwnersMention)}}

[robertboccia]

maybe this is the time to integrate the work being done to solve the bigger Risco issue @OnFreund ? I know you have seen the mqtt stuff, possibly now is the time to pull that into a fully local control integration?

[swiergot]

maybe this is the time to integrate the work being done to solve the bigger Risco issue @OnFreund ? I know you have seen the mqtt stuff, possibly now is the time to pull that into a fully local control integration?

Excuse me, what are you referring to?

[pergolafabio]

@robertboccia , there is no python library, the new risco cloud first need to be converted before @OnFreund cau use it... Do you know someone?

You also use the new addon

[OnFreund]

Unfortunately I still don't have the capacity to port the local library to Python, but happy to help out if others pick up the gauntlet. As for this issue, it's way smaller, so maybe I'll manage to get to it. All it takes is converting the strings to timestamps for the sensor states. In any case, this issue will only affect the event sensors - the partitions and zones should continue to function normally.

[Rookie-Ron]

I am not sure if it is related to this issue, but I do have challenges with my Risco (MyElas) 'iConnect2' alarm system. From the Risco integration (I am on HASS Core-2021.12.3) I do not get the 'armed/disarmed' status at all, other than that I can read the changes from the attributes. After exploring the MQTT alternatives [https://github.com/lucacalcaterra/risco-mqtt-bridge] and [https://npm.io/package/risco-mqtt-home-assistant] I think I have narrowed it down to the fact that 'iConnect2' does not have Partitions. From the 'npm.io' alternative I learned I can assign Partition "-1" to be able to get the alarm sensors readings, but still no information about the alarm status 'armed/ disarmed'. This also seems supported by my HASS Logbook, indicating:

The " 'NoneType' object is not iterable' " seems to point to a Partition issue? Anyway: any comments or suggestions? Is it related to HASS or to the Risco API? (from Risco's own Cloud Apps all interactions work perfectly)

[OnFreund]

@Rookie-Ron https://github.com/home-assistant/core/issues/40290

[Rookie-Ron]

@OnFreund : thank you for the quick response! I was aware of #40290, as well as #https://github.com/OnFreund/pyrisco/pull/2 . Are there developments since February?

[OnFreund]

Not that I'm aware