-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error when retrievable turned off #34
Comments
I think Amazon needs to whitelist your account before it will actually work. Try contacting your Amazon representative to ask to be whitelisted. And yes, I think it's supposed to be One thing I noticed, is that unless there is a real big error, the server always responds with a 201. |
hi,metoo,Have you solved it |
The docs should say proactivelyReported. There was a few places where this was incorrect, and I've fixed this and the fix should be live in a few minutes. |
ok, great. that removes the ambiguity from the specs. the feature itself, proactive reporting, seems to be broken however. |
We're having issues with proactive reporting (if we turn off retrievable, and send an proactive report the amazon app indicates that an error occured).
So, I guess the first question would be, is the property called "proactivelyReported", as most docs indicate, or "proactivelyReportable", as stated in the v3 migration guide here: https://developer.amazon.com/de/docs/smarthome/smart-home-skill-migration-guide.htm
though it's almost a moot point, neither seems to work for us.
any hints as to how to debug issues with proactive reporting? the server response is 201, seemingly there is no error. the json we send looks fine.
The text was updated successfully, but these errors were encountered: