Riscocloud upgraded to 5.2 , error code 200 about risco-mqtt-bridge HOT 64 CLOSED

I got it !!! I'll test on my system and after , if it's ok, publish a new relase !

from risco-mqtt-bridge.

test it, works perfect!

from risco-mqtt-bridge.

from risco-mqtt-bridge.

@lucacalcaterra should be able to fix it , probably a small code change
when i try this docker/Addon, that one is still able to connect and get status
https://github.com/martingrayson/risco-hass-bridge

from risco-mqtt-bridge.

Hy guys !

Be patience, i'll check it..

Not sure if my panel has been migrated to 5.2

After your 5.2 updates,t he web interface of risco is still the same ?

from risco-mqtt-bridge.

all panels are migrated, it was the cloud itself :), if was offline today worldwide :)

from risco-mqtt-bridge.

all panels are migrated, it was the cloud itself :), if was offline today worldwide :)

I was in doubt... if there was different regional servers... ok. I'll check,

ps I've a fix for arm/disarm multi partition too in next commits..

from risco-mqtt-bridge.

ah nice, but i only have 1 partition :)

but anyway, it would be great if you could change the state like arm/disarmed based on an event, and not the state on riscocloud.com , so we have the change instant without that 4 min delay (when arming from hardware panel)

from risco-mqtt-bridge.

@lucacalcaterra should be able to fix it , probably a small code change
when i try this docker/Addon, that one is still able to connect and get status
https://github.com/martingrayson/risco-hass-bridge

@pergolafabio are you sure this addon still works with new risco cloud 5.2 ?

from risco-mqtt-bridge.

Before i've read this, i've investigated...

The problem it's probably with the axios library used.

I'm migrating all http requests to got js library , it should works...

If the way it's right tomorrow i'll have a fix.

ps the solution proposed in previous post cannot used here because i've managed all http calls with axios, so... be patience..

from risco-mqtt-bridge.

Hi All, Partial success for me. If i arm / disarm from the risco phone app my home assistant now sees this and updates but if i try to arm / disarm from home assistant itself i get error 500 as below: [cid:c9a26035-1d08-40d2-bc86-e00f17495625] I also get this coming through on the logs [cid:96d06337-ca42-41cd-8754-73c9674c896d]
________________________________ From: Luca Calcaterra [email protected] Sent: 20 September 2019 11:22 To: lucacalcaterra/risco-mqtt-bridge [email protected] Cc: rob1981forest [email protected]; Comment [email protected] Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26) Yes, Docker hub automatically rebuild it... Do a docker pull ! Il giorno ven 20 set 2019 alle ore 13:06 pergolafabio < [email protected]> ha scritto:
I see new release, I am running the docker version, is that also deployed? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26?email_source=notifications&email_token=AAGWZUI4UV2FJAKODCWVM23QKSVE5A5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7GLPMI#issuecomment-533510065>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGWZUJ7VRTWXFQPIZSGVE3QKSVE5ANCNFSM4IX7R2YA .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub<#26?email_source=notifications&email_token=ALCGLUFRYJ3CVCXKM7LKSDDQKSW7XA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7GMPLI#issuecomment-533514157>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUA3QSVTNU2Z77Y7KBLQKSW7XANCNFSM4IX7R2YA.

Just tried on my system... same issue.. error 500. Have you multiple partitions ? I'll debug it

from risco-mqtt-bridge.

I updated to 1.4.1 . Who can test it for arm/disarm commands ? Some issue still presents because i need to manage multiple partitions, but hope works for who has one partition only

from risco-mqtt-bridge.

i tried on my system ... seems it's ok...

from risco-mqtt-bridge.

I hope public API is released soon

from risco-mqtt-bridge.

from risco-mqtt-bridge.

Thanks for a quick fix lucacalcaterra. Love your work.

If anyone can assist me in the upgrade would be appreciated

I have a home assistant running on synology via docker. How will I upgrade to your new version?
I currently have the version prior the 5.2 which was working fine. Do I just upgrade the docker image and run?

from risco-mqtt-bridge.

Yeah, just update the docker, pull new image

from risco-mqtt-bridge.

Find way in your Synology (i used it but don't remind so much ) to delete container ... then pull the new image and then recreate you container

from risco-mqtt-bridge.

... find some helps on synology site or net..

from risco-mqtt-bridge.

from risco-mqtt-bridge.

gonna close ticket, all is working fine and stable

thnx again @lucacalcaterra

from risco-mqtt-bridge.

I finally figured it out. In case someone still has problems with 5.2 - my riscocloud email had a + sign in it which caused login problems, probably because of postData

from risco-mqtt-bridge.

from risco-mqtt-bridge.

from risco-mqtt-bridge.

Yeah, using it now, also arm commands are working

from risco-mqtt-bridge.

from risco-mqtt-bridge.

Yeah give Luca time!

Here is a fix :

szlaskidaniel/homebridge-risco-alarm#17 (comment)

from risco-mqtt-bridge.

Ah , good news, thnx

from risco-mqtt-bridge.

from risco-mqtt-bridge.

Perfect, thnx!

from risco-mqtt-bridge.

I see new release, I am running the docker version, is that also deployed?

from risco-mqtt-bridge.

from risco-mqtt-bridge.

from risco-mqtt-bridge.

no issue here
make sure you are logged out from the app, you cant have 2 logins at same time....
just close the app, wait for idle timeout, takes about 3-4 min
then try again

from risco-mqtt-bridge.

from risco-mqtt-bridge.

indeed, now i notice 500 too
strange, i was quite sure i was able to arm/disarm from HA
i only have 1 partition

from risco-mqtt-bridge.

I'm checking it..

from risco-mqtt-bridge.

for info : when i tried to arm, i received a email notification from risco :

Event Zone Omitted - 'xxx', 'xxx' occurred at your system at 20/09/2019 15:15:00

from risco-mqtt-bridge.

also some info from error log, maybe it can help :

at process._tickCallback (internal/process/next_tick.js:189:7)

(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 11)

20-09-2019 15:17:57 debug: polling ...

20-09-2019 15:17:57 debug: return null, overview empty!

from risco-mqtt-bridge.

Probably the http requests suffers the same bug of login (initial issues). Should not be a great problem to fix

from risco-mqtt-bridge.

I can test, but not today :(
If docker is also updated?

from risco-mqtt-bridge.

I can test, but not today :(
If docker is also updated?

Intel image yes, armhf i'm uploading...

from risco-mqtt-bridge.

Yeah, Intel here...is it updated already now?

from risco-mqtt-bridge.

Kids are home in 10 min, maybe I can test late this evening when everyone is a sleep ;)

from risco-mqtt-bridge.

hey @lucacalcaterra thank you for working on this 🙇

I tried both branches, master and riscocloud-5.2, on both it seems like logging in works fine, but then I get disconnected from cloud warning and it tries to relogin continuously:

https://cl.ly/1007155f0752

20-09-2019 18:59:22 debug: Class Connection Constructor end
20-09-2019 18:59:25 info: Connected to MQTT Server
20-09-2019 18:59:25 debug: Logged...Response code is 302: OK
20-09-2019 18:59:27 debug: return null, overview empty!
20-09-2019 18:59:27 debug: newarmstatus emitted
20-09-2019 18:59:27 debug: no new status
20-09-2019 18:59:27 debug: Init function for getting data from Cloud completed: OK
20-09-2019 18:59:27 debug: polling started...
20-09-2019 18:59:37 debug: polling ...
20-09-2019 18:59:37 debug: return null, overview empty!
20-09-2019 18:59:37 debug: Polled...counter:  0
20-09-2019 18:59:37 warn: Disconnected from cloud...relogin and init...
20-09-2019 18:59:37 debug: Logged...Response code is 302: OK
20-09-2019 18:59:39 debug: return null, overview empty!
20-09-2019 18:59:39 debug: newarmstatus emitted
20-09-2019 18:59:39 debug: no new status
20-09-2019 18:59:39 debug: Init function for getting data from Cloud completed: OK
20-09-2019 18:59:47 debug: polling ...
20-09-2019 18:59:47 debug: return null, overview empty!
20-09-2019 18:59:47 debug: Polled...counter:  1
20-09-2019 18:59:47 warn: Disconnected from cloud...relogin and init...
20-09-2019 18:59:48 debug: Logged...Response code is 302: OK
20-09-2019 18:59:49 debug: return null, overview empty!
20-09-2019 18:59:49 debug: newarmstatus emitted
20-09-2019 18:59:49 debug: no new status
20-09-2019 18:59:49 debug: Init function for getting data from Cloud completed: OK

HASS doesn't report alarm status this way. Has anyone had similar problem?

I've got multiple partitions. I'll wait for a proper fix if this is the issue

from risco-mqtt-bridge.

from risco-mqtt-bridge.

i think @pawelnguyen is also working, but it seems the bridge is always logging out/in
you dont see that bevaviour in yours? i have not updated yet

from risco-mqtt-bridge.

from risco-mqtt-bridge.

ok, upgraded here too now, polling seems fine here also

from risco-mqtt-bridge.

from risco-mqtt-bridge.

Upgraded here also, seems ok now, altho i can be logged in to the APP, web interface , and have it polling away .. and no issues.

from risco-mqtt-bridge.

Yeah, just update the docker, pull new image

Thanks, done that and is working fine again

from risco-mqtt-bridge.

Thanks

from risco-mqtt-bridge.

I have this error with a fresh install today ...
16-01-2020 17:34:21 debug: Class Connection Constructor end 16-01-2020 17:34:21 info: Connected to MQTT Server 16-01-2020 17:34:22 error: Exceptions on login response: Error: Request failed with status code 200 16-01-2020 17:34:22 debug: ...site and Pin Code sent...Response code is 302: OK 16-01-2020 17:34:23 debug: return null, overview empty!

from risco-mqtt-bridge.

from risco-mqtt-bridge.

didnt happen to me anymore tough , a few months ago, indeed, all pins were somehow blocked, only way to login ; was to change/use the pins on the panel itself
pins on cloud/app were blocked

from risco-mqtt-bridge.

Been using your docker image for a while, with success i might add. So thank you for the effort so far! However since the upgrade (hosed up my HA installation in the meanwhile and too lazy to do something about it :-P) i've been getting the following errors:
18-01-2020 13:00:30 error: Exceptions on login response: Error: Request failed with status code 200 18-01-2020 13:00:40 warn: Disconnected from cloud...relogin and init... ... 18-01-2020 13:01:21 warn: Disconnected from cloud...relogin and init... 18-01-2020 13:01:21 error: Exceptions on login response: Error: Request failed with status code 200

Any idea what might be causing this? Like @pawelnguyen mentioned, i also have a "special character" in my e-mail adres, which is a _ (underscore). Any suggestions are welcome!

from risco-mqtt-bridge.

Been using your docker image for a while, with success i might add. So thank you for the effort so far! However since the upgrade (hosed up my HA installation in the meanwhile and too lazy to do something about it :-P) i've been getting the following errors:
18-01-2020 13:00:30 error: Exceptions on login response: Error: Request failed with status code 200 18-01-2020 13:00:40 warn: Disconnected from cloud...relogin and init... ... 18-01-2020 13:01:21 warn: Disconnected from cloud...relogin and init... 18-01-2020 13:01:21 error: Exceptions on login response: Error: Request failed with status code 200

Any idea what might be causing this? Like @pawelnguyen mentioned, i also have a "special character" in my e-mail adres, which is a _ (underscore). Any suggestions are welcome!

Anyone? Can I t-shoot this situation? Would be cool to arm/disarm the house again.

from risco-mqtt-bridge.

@DanVer1758 in my case the problem was that I was using a + sign in my gmail email. I worked around it by creating a new user with a [email protected] mail instead of using [email protected]. I also changed my code as @lucacalcaterra mentioned. If I were you, I'd create a separate user for HA with an email without _. Also you can double check that in your docker image there's all recent changes for 5.2

from risco-mqtt-bridge.

@pawelnguyen thanks a bunch, seems that got me a step further. I will have another look in the weekend. I've downloaded the latest image created, so i'd reckon that should cover the recent changes. However, i'll also double check that. Keep you posted.

from risco-mqtt-bridge.

Thanks a bunch @pawelnguyen. Seems that removing a special character from the login has done the trick :-) and everything is up and running again. @lucacalcaterra: Maybe an idea to get the postData to accept special characters?

from risco-mqtt-bridge.

dont think ll changes are needed, public API will be released in riscocloud 5.5
then this docker maybe become obsolute anyway

from risco-mqtt-bridge.

Very much true, however as we don't know the exact timelines I thought I'd propose it :-)

from risco-mqtt-bridge.

ETA is july! ;-)

from risco-mqtt-bridge.