I have an application thats send around 150+ KB to the Chromecast Dongle using the sample HelloText app from GitHub, however on the onReceive callback, I receive a Unknown Status Code 2001.
What does this status code imply since it's not documented anywhere in the official SDK documentation?
Are you breaking your data into smaller pieces and send or you are trying to send everything in one shot? I believe there is a limit of 64K per message (I might be wrong on the exact number though, but it is < 150K). 2001 error code means it is an invalid requests.
Related
I have multiple live streams to YouTube being pushed 24/7 from IP cameras. In YouTube studio live stream interface, there is a column per live stream showing health of inbound connection & data.
(see snip below).
This shows for each currently 'live' live stream if the inbound data rate is 'excellent', 'good', 'poor', or 'no data'. I have to believe if the YouTube studio live interface is able to poll and display this, it should be available in the YouTube live v3 API.
However, I can't find anything on it. My need is I want to create automation to query status every 15 min or so and alert me if one of my camera sources goes down. Does anyone have insights on where to get this from the YouTube v3 API?
The answer to your question is straightforward:
Use the LiveStreams.list API endpoint, queried with the request parameter mine set to true and look for the following property of the JSON response:
status.healthStatus (string)
The status code of this stream.
Valid values for this property are:
good – There are no configuration issues for which the severity is warning or worse.
ok – There are no configuration issues for which the severity is error.
bad – The stream has some issues for which the severity is error.
noData – YouTube's live streaming backend servers do not have any information about the stream's health status.
Also, don't forget to pass status to the request parameter part too.
I'm using YouTube Data API v3 to retrieve a video info (title, description, thumb) when a user pasted the URL into my internal system. I started getting an 403 error about quota.
When I open Console Developers Dashboard, it shows 45 requests in the last 30 days (that system is not used all the time).
When I click to get an overview from that API, under Quotas, my queries per day shows 0 without possibility of change that limit.
I got a message at the top of the page to request more quota limit but when I follow that link the form tells my current limit is 0 and to require a new limit - which is 0! Can't proceed without any number greater than 0.
Does anyone knows if that is a bug?
This is intended behavior see issue #211012781
Hi. If you're seeing Queries per day quota set to 0 and the API is indeed enabled, then this means that your project’s access to YouTube Data API Service has been disabled.
You should’ve received a notice via email regarding this action, which also contains the steps that need to be taken to regain the project’s access. But just in case you missed it, please fill out and submit the exceptions form below:
https://support.google.com/youtube/contact/yt_api_form?hl=en
I had ported Widevine CDM to cobalt RELEASE_9 branch. Playback of purchased video very well in beginning of 5 minutes. After 5 minutes, decrypt failed, the reason is key expiration.
After review DRM related API in starboard, I have two questions:
1.How to handle "renewal" message from CDM? how to inform upper layer when such message existed?
2.If key/license expired, how to reflect such status to upper layer?
Thanks
You can call SbDrmSessionUpdateRequestFunc with kSbDrmTicketInvalid if the update request was generated by the DRM system (Widevine CDM in this case).
Cobalt will pass these messages to server to get new license.
Check the comment in Drm.h and you also need SB_API_VERSION >= 4 in your platform.
I send the message via SparkPost API with option sandbox=true.
I get error "Fatal SparkPostError: Exceed Sending Limit"
I can't find description of the error in DOCs, Google or stackoverflow.
Anybody know what issues with sandbox of SparkPost? How much is limit for sandbox? When does it refresh?
The sandbox options allows you to send using the #sparkpostbox.com domain. It is currently limited to 50 sends for the lifetime of the account. At this time you should have a verified sending domain to use going forward. If you are looking for information on testing using SparkPost, take a look at this support document: https://support.sparkpost.com/customer/portal/articles/2361300.
I have recently converted a trial account into a paid starter package and, since I've been assigned a long number, my attempts to send messages via the HTTP API have failed with the following messages in the Message Reports console:
An error occurred while attempting to route the message
Routing error (status 9)
I have confirmed that my username, password, and api id are entered correctly and that the long number has been matched to the active API. I've tried the "Valid Sample Code" provided on the API management console, all with the same result. Below are a few failed message ids if that's helpful for anyone on the Clickatell team.
6d7868662782cfd7d1708996bca066b1
4f837467ed535521ef39d9d885f121f9
2be08f4663a3d9d7cf2e5b9e9cad2d5f
For what it's worth, my trial account worked fine and as expected, so I'm fairly certain that this is not (obvious) user error on my part. I also upgraded a few hours ago; I'm not sure if there is a wait period between account activation and functional service. Thanks for any help on this.
Have you tried setting mo=1 and using your long number as your sender id from=123456789?
make sure you dont add any programming symbols in the text message. i had an exclamation mark and it gave me a status 9 error.
http://api.clickatell.com/http/sendmsg?api_id=xxxx&user=xxxx&from=13055140341&mo=1&password=xxxx&to=xxxx&text=xxxx
For what it's worth, I encountered a very similar problem with the REST API. It also requires the undocumented "mo=1" and "from=[your long number]" fields to be included.
Also, in the FAQ, they have "MO=1" but in actuality, it has to be a lower-case.
From OP:
Clickatell support responded with the following advice that resolved my problem. I also changed the password on my API key during the process which seemed to be part of the issue.
http://api.clickatell.com/http/sendmsg?api_id=xxxx&user=xxxx&from=13055140341&mo=1&password=xxxx&to=xxxx&text=xxxx
"from" is your long number, and because I'm using 2 way messaging , mo=1 needed to be set also. It would have been helpful if this were in the exemplary code provided on the api info and help section, but alas, I had to go through support to get my answer. It took about 2 business days for the response, but they were helpful