Riscocloud upgraded to 5.2 , error code 200

today riscocloud upgraded to 5.2
seems this bridge doesnt connect anymore now :(
if i restart the docker, i now get :
18-09-2019 16:19:30 warn: Disconnected from cloud...relogin and init...
18-09-2019 16:19:30 error: Exceptions on login response: Error: Request failed with status code 200

Yeah, not working for me either and has been flawless for months.
Cloud update must have broke this.
Help !!!!!!!
Rob
Get Outlook for Androidhttps://aka.ms/ghei36

From: pergolafabio<EMAIL_ADDRESS>Sent: Wednesday, September 18, 2019 3:23:07 PM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
today riscocloud upgraded to 5.2
seems this bridge doesnt connect anymore now :(
if i restart the docker, i now get :
18-09-2019 16:19:30 �[33mwarn�[39m: Disconnected from cloud...relogin and init...
18-09-2019 16:19:30 �[31merror�[39m: Exceptions on login response: Error: Request failed with status code 200
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUFG7CC3MKNRFAFHDTDQKI2UXA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HMFCD4A, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUHOJIMK7MQTH7OWAE3QKI2UXANCNFSM4IX7R2YA.

@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

Just a side on this....
Somehow a while back I managed to create a risco installer account ........my panel isn't registered in there, it's still in my alarm company one.
Shows quite a lot of things and I assume I could move my panel into here if it was unregistered from the alarm company one.
Would this help anyone in anyway ?
Get Outlook for Androidhttps://aka.ms/ghei36

From: pergolafabio<EMAIL_ADDRESS>Sent: Wednesday, September 18, 2019 3:30:49 PM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
@lucacalcaterrahttps://github.com/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
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUGRZ77PLFYTHUUSE5LQKI3RTA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7AIRHQ#issuecomment-532711582, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUFB53AXWG7PBS2UX4DQKI3RTANCNFSM4IX7R2YA.

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 ?

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

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..

Just a side on this.... Somehow a while back I managed to create a risco installer account ........my panel isn't registered in there, it's still in my alarm company one. Shows quite a lot of things and I assume I could move my panel into here if it was unregistered from the alarm company one. Would this help anyone in anyway ? Get Outlook for Androidhttps://aka.ms/ghei36
…
________________________________ From: pergolafabio<EMAIL_ADDRESS>Sent: Wednesday, September 18, 2019 3:30:49 PM To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26) @lucacalcaterrahttps://github.com/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 — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#26?email_source=notifications&email_token=ALCGLUGRZ77PLFYTHUUSE5LQKI3RTA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7AIRHQ#issuecomment-532711582>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUFB53AXWG7PBS2UX4DQKI3RTANCNFSM4IX7R2YA.

about 6/7 months ago, you could access your own panel as installer, now this is not possible anymore, only alarm company can do it now , risco changed that behaviour
i am an installer, i have asked risco to remove me registered panel from the alarm company, so i can manage my own panel, 1 good reason, if you want to attach cameras to risco, this can only be done by installers  and i dont want installers to access my cameras, so i am now direct connected :)

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)

@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 ?

Yeah, using it now, also arm commands are working

Hey all,
Any news on the issue here ? Look a simple fix ?
Did the official API from risco ever happen ?
It's funny home many of my automations now don't work without this !!!
Thanks
Rob
Get Outlook for Androidhttps://aka.ms/ghei36

From: pergolafabio<EMAIL_ADDRESS>Sent: Thursday, September 19, 2019 5:23:04 AM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
Yeah, using it now, also arm commands are working
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUDVSBG6TGWFXUXMYMTQKL5CPA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7CFBJY#issuecomment-532959399, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUCCSBET73HC4KGA5EDQKL5CPANCNFSM4IX7R2YA.

Yeah give Luca time!
Here is a fix :
https://github.com/szlaskidaniel/homebridge-risco-alarm/issues/17#issuecomment-533266650

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..

Ah , good news, thnx

Great, will try it out
Get Outlook for Androidhttps://aka.ms/ghei36

From: pergolafabio<EMAIL_ADDRESS>Sent: Friday, September 20, 2019 4:32:50 AM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
Ah , good news, thnx
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUENEGLL4YU2J2HGJFDQKQ76FA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7FOK6I#issuecomment-533390713, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUAJ74FN2SOX3S7LEP3QKQ76FANCNFSM4IX7R2YA.

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

Perfect, thnx!

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

Yes, Docker hub automatically rebuild it... Do a docker pull !
Il giorno ven 20 set 2019 alle ore 13:06 pergolafabio <
<EMAIL_ADDRESS>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
https://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=AAGWZUI4UV2FJAKODCWVM23QKSVE5A5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7GLPMI#issuecomment-533510065,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGWZUJ7VRTWXFQPIZSGVE3QKSVE5ANCNFSM4IX7R2YA
.

test it, works perfect!

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_ADDRESS>Sent: 20 September 2019 11:22
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>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_ADDRESS>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
https://github.com/lucacalcaterra/risco-mqtt-bridge/issues/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 GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUFRYJ3CVCXKM7LKSDDQKSW7XA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7GMPLI#issuecomment-533514157, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUA3QSVTNU2Z77Y7KBLQKSW7XANCNFSM4IX7R2YA.

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

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_ADDRESS>Sent: 20 September 2019 11:22 To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>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_ADDRESS>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

Yeah same I'm afraid.
You running home assistant and the risco bridge in a Synology docker ?
Get Outlook for Androidhttps://aka.ms/ghei36

From: pergolafabio<EMAIL_ADDRESS>Sent: Friday, September 20, 2019 1:58:43 PM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
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
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUFT4RF3NZ5UCHXR3U3QKTCIHA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7GTYKY#issuecomment-533543979, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUFEUHTZHWGU3A7HH6TQKTCIHANCNFSM4IX7R2YA.

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

I'm checking it..

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

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!

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

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

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

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

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

Yeah, Intel? Is it updated already now?

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

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

I hope public API is released soon

Just tested and all working now !!
Thanks a lot for getting this sorted.
Rob
Get Outlook for Androidhttps://aka.ms/ghei36

From: pergolafabio<EMAIL_ADDRESS>Sent: Friday, September 20, 2019 4:16:17 PM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
I hope public API is released soon
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUCI7XSRT6GVBR7HIO3QKTSMDA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7HAKTQ#issuecomment-533595470, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUG7VKQR6KVS4XMM7XTQKTSMDANCNFSM4IX7R2YA.

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

Mine been up 2 hours and still working ok
Get Outlook for Androidhttps://aka.ms/ghei36

From: Paweł Nguyen<EMAIL_ADDRESS>Sent: Friday, September 20, 2019 6:04:40 PM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
hey @lucacalcaterrahttps://github.com/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
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUGANBVBPQHLKDWYKTDQKT7CRA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7HJ7KQ#issuecomment-533634986, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUGJ75NMJFHYDSRTPYTQKT7CRANCNFSM4IX7R2YA.

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

No, my logs are just full of the polled .....counter number increasing as expected....
I only have 1 partition though
Get Outlook for Androidhttps://aka.ms/ghei36

From: pergolafabio<EMAIL_ADDRESS>Sent: Friday, September 20, 2019 6:32:19 PM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
i think @pawelnguyenhttps://github.com/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
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUG4GPBJXV3RWP5QPXLQKUCKHA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7HMF4A#issuecomment-533644016, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUGIERJY3VN2XXFFNVTQKUCKHANCNFSM4IX7R2YA.

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

I still get that 'unhandled promise rejection' error quite often but it all seems to work as needed at moment
Get Outlook for Androidhttps://aka.ms/ghei36

From: pergolafabio<EMAIL_ADDRESS>Sent: Friday, September 20, 2019 6:35:57 PM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
ok, upgraded here too now, polling seems fine here also
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUBO5UOQ7FDE67F6SADQKUCX3A5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7HMPMQ#issuecomment-533645234, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUCJMAVPMEQJZWJ4O7DQKUCX3ANCNFSM4IX7R2YA.

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.

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?

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?

Yeah, just update the docker, pull new image

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

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

You don't need to delete container in Synology.
Just stop it, then clear from the menu and pull latest image......simple
Get Outlook for Androidhttps://aka.ms/ghei36

From: Luca Calcaterra<EMAIL_ADDRESS>Sent: Saturday, September 21, 2019 9:12:19 PM
To: lucacalcaterra/risco-mqtt-bridge<EMAIL_ADDRESS>Cc: rob1981forest<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [lucacalcaterra/risco-mqtt-bridge] Riscocloud upgraded to 5.2 , error code 200 (#26)
... find some helps on synology site or net..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=ALCGLUG55JTXDCCTKZ6M4DTQKZ52HA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IY3XQ#issuecomment-533827038, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCGLUF7PHUE23ZWQKC2ZITQKZ52HANCNFSM4IX7R2YA.

Yeah, just update the docker, pull new image

Thanks, done that and is working fine again

Perfect!!!
Il Dom 22 Set 2019, 01:07 mrbarbz<EMAIL_ADDRESS>ha scritto:

Yeah, just update the docker, pull new image
Thanks, done that and is working fine again
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lucacalcaterra/risco-mqtt-bridge/issues/26?email_source=notifications&email_token=AAGWZUJG6AA4B2YBX2V4NDDQK2SMTA5CNFSM4IX7R2YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7I3ERQ#issuecomment-533836358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGWZULRWZLXECZC4VXNKULQK2SMTANCNFSM4IX7R2YA
.

gonna close ticket, all is working fine and stable
thnx again @lucacalcaterra

Thanks

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

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?

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

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

ETA is july! ;-)


[WIP] - Converted the syntax to Swift 3 and updated the sdk method calls

The project builds and runs on XCode 8 Beta 3.
Still need to update Quick and Nimble.

Thanks for doing this! How do you feel about keeping this open until the GM release of Xcode 8?

I feel like that's the way to go @maxmeyers

Tests are passing @maxmeyers. Hopefully Apple won't change anything for the GM.

GM is out. Would be great to get this applied.

I think there might be some applicable changes in the README for Swift 3 as well.
Also, I'd like to use official Quick & Nimble releases before merging this.

@maxmeyers I think there were only 2 function signatures on the README that needed to be changed.


Remoting-Agent (Docker): Release Images lack CallbackHandler functionality/code.

Reporter
E2E Deployment at ZF (Rohit Kumar)
Affects
Release 1.9.8 of Remoting Agent (Digest 35c74a1d5560)
https://hub.docker.com/layers/tractusx/remoting-agent/1.9/images/sha256-35c74a1d556002df128f5d1fc971e749ac2ccb2d658b5d237305e1cd886bde89?context=explore
Observation
When setting up a remoting repository which requires asynchronous callback, the following exception appears
06:57:25.702 [http-nio-8081-exec-4] WARN  o.s.w.c.s.XmlWebApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'rdf4jCallbackUrlMapping' defined in ServletContext resource [/WEB-INF/callback.xml]: Initialization of bean failed; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.eclipse.tractusx.agents.remoting.callback.CallbackController] for bean with name 'rdf4jCallbackController' defined in ServletContext resource [/WEB-INF/callback.xml]; nested exception is java.lang.ClassNotFoundException: org.eclipse.tractusx.agents.remoting.callback.CallbackController
As a result, the repository will not accept any SPARQL calls.
Wanted Behaviour
The repository should be created without any exception and process incoming SPARQL requests.

The problem can be tracked down to the line
https://github.com/eclipse-tractusx/knowledge-agents/blob/cc19b06ea20c03b98bd4d1645658afa640cc22a0/remoting/src/main/docker/Dockerfile#L24
The copy line "forgets" to add a compiled library to the docker runtime in case that we deal with a release (non-SNAPSHOT) jar.


Refactor BWS launch script

Coverage remained the same at 92.76% when pulling a116c871ae32e311230e925221a7365f4556bd03 on isocolsky:ref/launcher into bef20234f1ba577fc04cc6f62b10d516ebb3ad0b on bitpay:master.

Coverage remained the same at 92.76% when pulling b39e719fceda66de353eefa548ca0b16fccd0194 on isocolsky:ref/launcher into 0cbff651100921efc211311ab2555d1d2b169377 on bitpay:master.

much better :)


Testing if a user has already reviewed an item.

Excellent app, works flawlessly for me.
Perhaps I have missed something obvious, is there a template tag or some other method for testing if a user has already reviewed an item so that I can hide the form?

Yes. General logic is:
{% if request.user.is_authenticated %}
  {% get_review_by_user for item as user_review %}
  {% if user_review %}
    ... user has reviewed this item, may be let him change the review ...
  {% else %}
    ... show blank review form for user ...
  {% endif %}
{% else %}
  ... ask user to login to be able to add reviews ...
{% endif %}

Thanks.


Set different, undeleteable default rate for container image chargeback

Setting a different, editable, undeleteable fallback rate for Container Image chargeback as suggested by @Loicavenel
cc @simon3z @bazulay
Im adding this to #13030 as well
@miq-bot add_label chargeback, providers/containers, euwe/yes

Default Container Image Rate being the new fallback rate and My Rate being a rate I set on a docker label

@isimluk @lpichler @gtanzillo Please review

@zeari is there a BZ for this?

@zeari is there a BZ for this?

https://bugzilla.redhat.com/show_bug.cgi?id=1396477
This was backported as a part of https://github.com/ManageIQ/manageiq/pull/13030


0.5.1 does not work on FreeBSD-9

but master does (with nocrypto-inhibit-modernity).
uname -r is 9.3-RELEASE-p25
cc --version is
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd9.3
Thread model: posix

@avsm does master work on your OpenBSD as well?

This looks weird. Could you please ask the original source of the bug to provide the full compiler error? The thing is, master makes a difference for the current OpenBSD, because gcc-4.2. It could also make a difference for FreeBSD-9 because that comes with gcc-4.2 too. But it should not make a difference for clang-3.4.1.
So I'd like to get to the bottom of this.

to solve the mystery, it was a gcc 4.2.1, and the problem was (as expected):
In file included from src/native/misc.c:1:
src/native/nocrypto.h:15:23: error: x86intrin.h: No such file or directory
cc1: warnings being treated as errors
src/native/misc.c: In function 'xor_into':
src/native/misc.c:9: warning: implicit declaration of function '_mm_storeu_si128'
src/native/misc.c:10: error: '__m128i' undeclared (first use in this function)
src/native/misc.c:10: error: (Each undeclared identifier is reported only once
src/native/misc.c:10: error: for each function it appears in.)
src/native/misc.c:10: error: expected expression before ')' token

(closing since this is only a remark that master works well on FreeBSD-9, and there will hopefully be a release in the near future)


New Memory Manager

The following provides a new memory manager for the VMM. With
this memory manager, it is now possible to new / delete in
the VMM. Since we do not yet have the MDL work complete, as
this will require std::array and std::hash, the VMM launch
code has been disabled for the moment. Once this code has
been complete, we will re-enable the code.
Signed-off-by: Rian Quinn<EMAIL_ADDRESS>

Just a note that a large number of tests were commented out in this PR. Is there an expected culling of these tests or was it unintentional @rianquinn?

@brendank310, it was done on purpose as a lot of things have changed. Once the STL is in place, and we have the exit handler flushed out, we will have to go back to workout the unit tests for a lot of the VMM itself. Until then, since there is so much changing, it doesn't really make sense to worry about the unit tests as they are likely to change in the future.


Correctly map array type class name within same namespace for reused

builtin class names

Coverage remained the same at 99.857% when pulling 5171ef2f7cbd3f31ce86b88c98f0df8744dd62fc on Issue102-JsonMapperDoesntLookupClassNameCorrectlyInArrayMapping into f20f812d3feb04d6e558f9e219848f679d7dbe2a on develop.


Distributed training resnet50 using 4 nodes 32  TeslaV100 cards

I checked a lot of literature, but I didn't find the results. The questions are as follows:
How many hours can it converge？（Distributed training resnet50 using 4 nodes 32 TeslaV100 cards）
Do you have internal test results that can be displayed to better understand the performance of your distributed training.

There are lot of resource like this on benchmark performance of tensorflow.
This is not Build/Installation or Bug/Performance issue. Please post this kind of support questions at Stackoverflow. There is a big community to support and learn from your questions. GitHub is mainly for addressing bugs in installation and performance. Thanks!


extensions: csv error logging fix

Coverage decreased (-0.6%) to 92.225% when pulling 9947856c0fd96053468d69170d7b77b0d4277cc1 on lnielsen:rel-v1.0.0a5 into f4907949442dd3dc6b23d6a50da29affa2e33008 on inveniosoftware:master.

Coverage decreased (-0.3%) to 92.493% when pulling deaae3336fc6e5b0ee4e724464b3d66be8f54411 on lnielsen:rel-v1.0.0a5 into f4907949442dd3dc6b23d6a50da29affa2e33008 on inveniosoftware:master.


Fix broken ./configure on mac because of incorrect sed syntax

Running ./configure on mac complains with the following error:
sed: can't read /tf_configure/d: No such file or directory

According to this SO post the syntax to avoid creating backup files with sed on 10.9+ is without a space between -i ''.

I signed it!

Jenkins, test this please.

@gunan what version of OSX are the mac slaves running? If it's pre-10.9 that would explain why it's failing (and worked before). I can try to make the code more portable for this.

@JVillella our executors should be el capitan and sierra only, (all 10.11+).

Error seems invalid.
Jenkins, test this please.

The failure in mac cpu tests is caused by the changes in this PR.
@JVillella do you have any insight about the failure, or how to fix it?
If not, I recommend we close this PR

@gunan looking again now.

So I seem to be running gnu-sed 4.2.2 which was likely installed from coreutils at some point in time. It has a different syntax. MacOS's built-in sed wants the empty string, gsed doesn't which is why there is a check (though for platform, assuming if you're on mac you're not using gsed):
function sed_hyphen_i() {
  if is_macos; then
    sed -i '' "$@"
  else
    sed -i "$@"
  fi
}

Using backups seems to be more portable (e.x. sed -i '.bak' ...). No platform check is required either. We could do this and just remove the backup. If you guys are ok with this solution I can make the change. awk (not gawk) doesn't let us do it in place either.
This issue only affects someone running gsed in place of sed on mac. If this makes it not-a-concern we can close the ticket.

Sorry for leaving this hanging. I think using .bak is a fine solution, especially if you delete them afterwards. I'd like to avoid the if, which seems brittle.

@JVillella any updates?

Hey @martinwicke, @vrv. I've updated the PR with a more portable solution. The build is passing now as well. Let me know if this is okay with you guys.

Looks good to me.
Jenkins, test this please.


Generic too broad in 2.2?

Compared to 2.1, it handles the following new cases (possibly others?),
class C

Generic[C]
Generic[Array[String]] // This one in particular looks surprising

(Quickly asked you about it on gitter, better to discuss it here.)

class C is intended ... it's as case-class-like as case class C().
Generic[Array[...]], on the other hand, isn't intended and the current behaviour (yielding HNil as the representation type) is definitely a bug.

About class C, I understand it is intended, but... I find it still somewhat surprising in practice.
Most of the time, I would consider this kind of classes as blackboxes, that I wouldn't want to assimilate to a case class when deriving type classes (codecs, pretty-printers, ...). I'd prefer to see type class derivation just fail for them (and possibly allow their derivation explicitly via a non implicit method).
I may end up enforcing automatic type class derivation for generic products to apply only for real Products. For example,
implicit def instanceEncodeJson[F, G](implicit
  gen: LabelledGeneric.Aux[F, G],
  encode: Lazy[EncodeJson[G]]
): EncodeJson[F] = ...

would become
implicit def productInstanceEncodeJson[F <: Product, G](implicit // type constraint on F
  gen: LabelledGeneric.Aux[F, G],
  ev: HasProductGeneric[F],
  encode: Lazy[EncodeJson[G]]
): EncodeJson[F] = ...

implicit def coproductInstanceEncodeJson[F, G](implicit
  gen: LabelledGeneric.Aux[F, G],
  ev: HasCoproductGeneric[F],
  encode: Lazy[EncodeJson[G]]
): EncodeJson[F] = ...

FWIW I made this change to support @cvogt's Scalacheck examples ... if we revert the new behaviour then they'll no longer work as expected.

Most of the time, I would consider this kind of classes as blackboxes, that I wouldn't
want to assimilate to a case class when deriving type classes (codecs, pretty-printers, ...).
I'd prefer to see type class derivation just fail for them (and possibly allow their derivation
explicitly via a non implicit method).

Can you flesh out this argument a little ... what motivates that preference?
One of the things that this supports is, eg. non-case classes with lazy members ... needed for immutable cyclic structures ... do you really want to exclude them?
I guess what I really need is some fairly precise criteria for deciding whether a given type should have a generic representation or not. case classes only is too narrow IMO, you think the current implementation is too broad. How do we mark out the space in between?

Looking more closely at https://github.com/alexarchambault/scalacheck-shapeless/blob/master/src/test/scala/org/scalacheck/Definitions.scala#L55-L56, I didn't know at the time whether they should be considered case class-like those of https://github.com/milessabin/shapeless/blob/master/core/src/test/scala/shapeless/generic.scala#L96-L109. If this use case was the only motivation, they definitely shouldn't imo.
If you think it's ok to just revert that (I don't know the consequences for non case classes), let's just do that.
The fear I was having was type classes being automatically derived too broadly and unexpectedly. I ran into that in scalacheck-shapeless recently (https://github.com/alexarchambault/scalacheck-shapeless/blob/master/src/main/scala/org/scalacheck/Shapeless.scala#L100, List[T] was considered a coproduct instead of a collection), and I fear there may be others in scalacheck-shapeless/argonaut-shapeless. (I'm going to add more tests to check that.)
About the examples of the issue, I just ran into them when trying to quickly address https://github.com/lihaoyi/Ammonite/issues/47 with shapeless. But the more strict behaviour of Generic in 2.1 should be ok (haven't tested yet though).

List[T] being considered a coproduct is absolutely by design. I'm not going to revert that. Can you explain what the problem is here?

I think your problem with the Shrink instance is actually a issue with implicit prioritization for orphan type class instances in general. The generic instance is accessible without a prefix so it overrides the instance available in the implicit scope.
This is a problem (I'm trying to deal with it in shapeless-contrib at the moment), but the problem emphatically isn't the fact that List[T] can be viewed as a coproduct.

I agree with List[T] being a coproduct
Le mardi 14 avril 2015, Miles Sabin<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> a écrit :

I think your problem with the Shrink instance is actually a issue with
implicit prioritization for orphan type class instances in general. The
generic instance is accessible without a prefix so it overrides the
instance available in the implicit scope.
This is a problem (I'm trying to deal with it in shapeless-contrib at the
moment), but the problem emphatically isn't the fact that List[T] can be
viewed as a coproduct.
—
Reply to this email directly or view it on GitHub
https://github.com/milessabin/shapeless/issues/360#issuecomment-92770444
.

I used List just to illustrate sometimes surprising (but perfectly legit in this case) type class derivation. But it's less legit for Array[T], and possibly the classes of scalacheck-shapeless you were talking about.

The reason that @cvogts Bar didn't have a Generic instance is that it had no constructor arguments: I previously had a check for at least one val constructor argument ... adding a single constructor val argument would have made it case-class-like and it would have had a Generic instance. I decided that there wasn't a difference between 0 and 1 arg that was sufficient to motivate the exclusion of the former, so I removed the check.
Baz was excluded on two counts. First that it had multiple argument lists and second that it had non-val constructor arguments. The latter is well motivated (we need the constructor arguments to be accessible from constructed values, which is only possible if they're vals). The former isn't really, but since we probably do want to exclude case classes with multiple argument lists and that multiple argument lists are rare in non-case classes, I thought it wouldn't be too much of a loss to exclude this case as well.

I completely agree that Array[T] is a problem.
We want gen.from(gen.to(x)) == x but that's not something that we can guarantee in general, even for case classes. I went to some lengths to ensure that, eg. String didn't end up with a Generic representation, and I thought that would cover all but edge cases which could be worked around in a reasonably straightforward way. Array[T] is obviously not an edge case, so that needs fixing.

Hmm ... though now I come to think of it, maybe String does have a generic representation: HList ... which could then be refined via Typeable. And "foo".type could be represented as 'f'.type :: 'o'.type :: 'o'.type :: HNil. And I guess Array[T] could be handled similarly.
The issue is that we don't want strings and arrays to be represented as HNil (which is want would drop out of the current implementation by default unless blocked) because that's not information preserving (hence we don't get gen.from(gen.to(x)) == x).

For arrays, I agree that the problem lies more in the generic representation being HNil rather in having a Generic instance per se. But what generic representation would you give to arrays then?

That is wandering off topic for this ticket a little ... maybe on gitter?

Sure!

I agree with case class being too narrow and classes being too broad. Conceptually you want type classes to be derivable when the classes satisfy certain laws, right? We expect case classes to satisfy certain laws (even though some can be broken), but other classes may satisfy some laws as well. Maybe declaring which laws they satisfy would help, maybe again via type classes.

I was thinking of an opt-in mechanism, like an additional import, to allow some non-case classes to be seen case classes.

The "opt-in" mechanism could be a type-class that automatically whitelists certain sorts
of classes, i.e. single constructor argument list only vals ones. An alternative non-implicit import could allow selective whitelisting of classes instead.


Remove unnecessary variables.

fileSystemRoots and fileSystemScheme are already included in BuildInfo, remove the duplicates.
No test was added because no code was added.

Updated to make a copy of fileSystemRoots in DefaultResidentCompiler to fix the error since the default value is an unmodifiable list. PTAL, thanks!


Create REST endpoint for problem data logging

Setup endpoints related to data logging concepts

posting new data log to backend
fetching datalog for a problem/student

Done!


Dear contributors, Thanks for giving us your Valuable Time,We will Update and Assign issue to you ,After Mentors will be allotted to the project.

Appreciate the update and look forward to receiving further instructions once mentors are assigned to the project. I'm eager to contribute and excited to work with the team to make meaningful progress on the project.


Add support to Grafana cloud

Is your feature request related to a problem? Please describe.
We scrape the metrics using Grafana agent which sends data to Grafana cloud.
Describe the solution you'd like
It would be great if you could allow passing Grafana cloud Prometheus query endpoint with username and password.
something like below
krr -p https://prometheus-xxx.grafana.net/api/prom -u <username> -p <password>

Hey, @Pavaningithub !
Sorry for long waiting, just got time to investigate Grafana cloud
I think Grafana cloud actually should work with --prometheus-auth-header command. You should be able to use Bearer <API key> or Basic <user:password in base64> to authorize.
If someone can approve it - I will close the issue. If not - I will try to verify myself

Closing. See the above message for a solution

@pavangudiwada can you add documentation for this to the README?

@aantn @pavangudiwada I have been using krr with Grafana Cloud lately, and it works like a charm. I added the instructions to make krr work with Grafana Cloud on this MR. Hopefully, it can make it easier for Grafana Cloud and krr users.


KAFKA-10455: Ensure that probing rebalances always occur

Add data to subscriptionUserData to make sure that it's different each time a consumer rejoins
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ableegoldman ready for initial review

System tests: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/4204/

One test failing: testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

https://jenkins.confluent.io/job/system-test-kafka-branch-builder/4226/ system tests part 2

Why do we use a size-1 byte array instead of a single byte for this field?
@vvcephei There's a RecordsFieldType already created for byte[] but not one for byte so to get the subscriptionInfo.json to work I would've had to create a RecordsFieldType for byte and decided that leveraging the existing field type would be easier. If you're strongly opposed to this solution I can look into creating a new field type

Cherry-picked to 2.7 (cc @bbejeck )

Cherry-picked to 2.6