Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
sendCommandToDevice MUST include subfolder otherwise error returned!
See original GitHub issueSpent numerous hours trying to figure out why the example code was not working, just to figure out that it was due to not having the subfolder specified!
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
projects.locations.registries.devices.sendCommandToDevice ...
Note that subscribing to specific subfolders is not supported. If the command could not be delivered to the device, this method returns an...
Read more >Google Cloud IoT sendCommandToDevice from cloud ...
The problem is that subfolder MUST be specified, and MUST not be an empty string. As I was using this in a Firebase...
Read more >com.google.cloud.iot.v1.DeviceManagerClient ... - Tabnine
Note that subscribing to specific subfolders is not supported. If the command could not be delivered to the device, this method will return...
Read more >cloudiot.projects.locations.registries.devices ... - Any API
sendCommandToDevice. Sends a command to the specified device. In order for a device to be able to receive commands, it must: 1) be...
Read more >Cloud IoT API v1 (revision 99) - Google Developers
Note that subscribing to specific subfolders is not supported. If the command could not be delivered to the device, this method will return...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@gguuss nope the only error I was seeing was in firebase console log showing that
503 Service Unavailablenothing was actually sent to the device as far as I could tell, and it was connected and subscribed to wildcard topic. I’ve basically just created a “firebase” subfolder for any commands I send from firebase functions nowOK, this seems to be an issue with Firebase and not with the samples themselves. I’ll follow up with the right folks from there but will be closing the issue here.