Blocking Error requires EXCEPTIONS but example shows SUCCESS [333408166]

Fixed

Customer Issue

Status Update

No update yet.

Description

ja...@securenettech.com

created issue #1

Apr 8, 2024 06:31PM

On this page: https://developers.home.google.com/cloud-to-cloud/guides/securitysystem#response

There is a note: Blocking exceptions reported with an "EXCEPTIONS" status indicate that arming or disarming was stopped because of these exceptions.

But the sample response shows a SUCCESS:

{ "requestId": "ff36a3cc-ec34-11e6-b1a0-64510650abcf", "payload": { "commands": [ { "ids": [ "123" ], "status": "SUCCESS", "states": { "online": true, "isArmed": false, "currentArmLevel": "L2", "currentStatusReport": [ { "blocking": true, "priority": 0, "statusCode": "windowOpen", "deviceTarget": "sensor_id1" } ] } } ] } }

Comments

cy...@google.com <cy...@google.com> Apr 9, 2024 01:35AM

Assigned to cy...@google.com.

ja...@securenettech.com <ja...@securenettech.com> #2Apr 10, 2024 02:57PM

Thanks for the report! It looks like the lint check in ParcelChecker.java has to be updated to account for the new behavior on sealed classes. Right now the checker just looks for @Parcelize annotations on the current class. It should also check whether there's a direct seelad superclasses that is annotated with @Parcelize.

cy...@google.com <cy...@google.com> #3Apr 12, 2024 06:02AM

Assigned to ja...@securenettech.com.

Dear Developer,

Thank you for raising this issue. I've passed this issue to our internal team and will continue to share updates on this issue thread. Thanks!

ja...@securenettech.com <ja...@securenettech.com> #4Apr 12, 2024 03:20PM

In the ticket that I mentioned above, I was able to get it working by adding the challengeNeeded: type: ack. But that panel will need to support bypass arm.

cy...@google.com <cy...@google.com> #5Apr 16, 2024 09:35AM

Dear developer,

Thanks for the update! Glad to hear that the issue resolved by adding the challengeNeeded: type: ack. If you have any further questions, please feel free to reach out to us. Thank you.

cy...@google.com <cy...@google.com> #6Jun 6, 2024 02:13AM

Marked as fixed.

Dear developer,

The sample response that mistakenly showed SUCCESS on Example: Blocking exception has been corrected to EXCEPTIONS.

It appears that the issue has been resolved. Should you have any additional questions or concerns regarding this matter, please don't hesitate to reach out. Thank you.

Stay up-to-date on the latest news, features, and requirements from Google Home, subscribe here: https://services.google.com/fb/forms/GoogleSmartHomeSignup/

Issue 333408166