-
Notifications
You must be signed in to change notification settings - Fork 34
Mode Endpoint has Changed #92
Comments
Any progress in this issue? |
@Nicxe sorry I've been a little busy lately but hopefully, someone will take this issue. |
Has there been any movement on this - seems like its now affecting the front/back end performance as well |
I'm picking this up. I'd be keen to understand where you see the data posted @jwillaz. When I post that payload (with my deviceId and current timestamp) I get
|
@nzben |
Update of alarm_control_panel.arlo_t is taking over 10 seconds |
I am also very interested in the progress. Thank you in advance. |
Would love this to work so I could utilize some automation. View mode It is really hit or miss. Sometimes it will return 'none' as the new set mode. sometimes it will return the same mode as the current set mode, indicating it never got changed. Not sure it is the code as much as it is Arlo. |
I'm not sure if @jwillaz initial issue is correct, because as I posted back in November, I can't get any valid response, nor any valid mode change. |
Yeah, I may be in the wrong thread. However, there is an issue where the mode won't change. |
its not only the mode change that is broken, I added another camera yesterday and it doesnt show up either - I think the entire component needs reviewing - unfortunately it seems no one has the time or skill at the moment to address the issues ... |
When changing modes (Armed, Disarmed, etc), a POST is now made to a different endpoint:
https://arlo.netgear.com/hmsweb/users/devices/automation/active
with a payload similar to the following:
{
"activeAutomations":[
{
"deviceId":"xxxxxxxxxx",
"timestamp":1531211943092,
"activeModes":[
"mode1"
],
"activeSchedules":[
]
}
]
}
The text was updated successfully, but these errors were encountered: