Unable to set the alarm

[karlismaj]

Hello I have following shown in the log. Were is the problem?

Other issue is that i'm getting error Failed to call service alarm_control_panel/alarm_arm_away. must contain at least one entity_id, area_id

Thank you very much

[lucacalcaterra]

Never worked before or before worked and now stops? In second case try to change pin code from alarm panel... let me know

[karlismaj]

Hello. I’ve just set up it and launched. It has never worked so far. Maybe because I’m noob in HA and Mqtt. PIN is right but I think I did not made right HA configuration file so I would appreciate if you could help me with this by sending some examples of code that I need to put into configuration file.

On 13 Sep 2020, at 02:02, Luca Calcaterra notifications@github.com wrote:



Never worked before or before worked and now stops? In second case try to change pin code from alarm panel... let me know

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/35#issuecomment-691568172, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHXRW4UWPUIYVDDMLWZHZCLSFP4WVANCNFSM4RKAPIPA.

[pergolafabio]

If it's to difficult to setup, wait untill Thursday in next release 115, then it's a official integration...

No need anymore for a seperate docker or mqtt

[karlismaj]

You mean it will be available as an home assistant official integration like these? https://www.home-assistant.io/integrations/#alarm Or it will be part of HACS? Thursday, you mean 17th of September? Will app.js still be require to be launched?

[pergolafabio]

Yes, official, no hacs, and yes, this Thursday when beta is over... You can already install beta if you want

[pergolafabio]

https://rc--home-assistant-docs.netlify.app/integrations/risco/

[karlismaj]

Hello

I see that Risco is now officially released. I’ve installed it, added account and and pin. Connection was successful, but I cannot add alarm card because entity for risco is not found.

There is no drop down for risco in entity list

Many thanks

From: pergolafabiomailto:notifications@github.com Sent: svētdiena, 2020. gada 13. septembris 13:23 To: lucacalcaterra/risco-mqtt-bridgemailto:risco-mqtt-bridge@noreply.github.com Cc: karlismajmailto:km@outlook.lv; Authormailto:author@noreply.github.com Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Unable to set the alarm (#35)

https://rc--home-assistant-docs.netlify.app/integrations/risco/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/35#issuecomment-691652399, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHXRW4XPO37B6CSRO5LUNZLSFSMTTANCNFSM4RKAPIPA.

[pergolafabio]

no idea, working fine here :), also updated

[karlismaj]

Do you use standard alarm panel card? Can you send me a code from the card? Maybe i can manually add it. I’ve now installed risco on 3 different HA installations including a fresh one without and no luck.

From: pergolafabiomailto:notifications@github.com Sent: ceturtdiena, 2020. gada 17. septembris 23:26 To: lucacalcaterra/risco-mqtt-bridgemailto:risco-mqtt-bridge@noreply.github.com Cc: karlismajmailto:km@outlook.lv; Authormailto:author@noreply.github.com Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Unable to set the alarm (#35)

no idea, working fine here :), also updated

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/35#issuecomment-694480296, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHXRW4ROHUPIAABOOBQC4GDSGJWFZANCNFSM4RKAPIPA.

[pergolafabio]

Yeah, just default lovelace card, no code

[karlismaj]

Sorry for asking so much questions, but do you have wifi connected system? I have GSM based, maybe this is the problem as HA cannot find wifi device on my network.

From: pergolafabio notifications@github.com Sent: Friday, September 18, 2020 12:39 AM To: lucacalcaterra/risco-mqtt-bridge risco-mqtt-bridge@noreply.github.com Cc: karlismaj km@outlook.lv; Author author@noreply.github.com Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Unable to set the alarm (#35)

Yeah, just default lovelace card, no code

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/35#issuecomment-694513493, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHXRW4W3C3OB5A3GCKSOPITSGJ6YLANCNFSM4RKAPIPA.

[pergolafabio]

You need riscocloud indeed

[karlismaj]

I do have. I use iRISCO mobile app. I was able to connect HA to my Rus iCloud account. It recognized all my zones. But I don’t see entity in the list so I could not add it to alarm card. What is the code for that? Maybe I could just write it manually...

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: pergolafabio notifications@github.com Sent: Friday, September 18, 2020 8:52:23 PM To: lucacalcaterra/risco-mqtt-bridge risco-mqtt-bridge@noreply.github.com Cc: karlismaj km@outlook.lv; Author author@noreply.github.com Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Unable to set the alarm (#35)

You need riscocloud indeed

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/35#issuecomment-695003270, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHXRW4RDQZQ2GLTREAIL7BLSGOM5NANCNFSM4RKAPIPA.

[pergolafabio]

No idea, no coded needed, there must be an entity created the same like the other sensors and binary sensors

[pergolafabio]

Can you make some screenshots from the entities created in the risco integration? Do you only see binary sensors there? Also is there an error in your log file?

But discuss here please :

https://community.home-assistant.io/t/risco-lightsys-alarm-component/82359/156

It has nothing to do with this docker anyway

[lucacalcaterra]

close for inactivity