meteohub.de

The current release log says 'All you need to make use of this service is to insert your MessageBird password', but presumably the Originator field should contain your MessageBird user name (ie rather than 'MeteoBridge') or am I misunderstanding how this service should work? But either way we still have a red cross showing against the Originator field.

Then, what does the Test SMS button do within the main Service configuration panel? The obvious guess is that it should send a generic test message, but at that stage it doesn't have a target phone number to send to.

Finally, would it be possible to add the build number into the messages on the release log - when 2 or more updates are released with the same date it would help clarify which version is the latest one.

Actually, the "password" you are supposed to insert on Meteobridge is NOT the password of your MessageBird account. Once you are logged in on MessageBird, go to "API", then click on "API access (REST)" and then click on "Add access key". When asked, select the creation of a "live" key. Once the key is created, you should click on "Show key". This is the key that you should add to the Meteobridge SMS "Password" field. Once you hit "save", the red cross should change to a green tick.

The "Originator" can be anything (I think). It does NOT have to be your MessageBird username. It is the name that will show up as the sender of the SMS (when you receive the SMS).

This is how I got my SMS service to work with MB Pro.

I hope this helps.

chrysnic

Thanks, making some progress in that the SMS access to MessageBird is validating now, but message-sending is still failing. Live Data shows an error:

Error: WARNING: cannot verify rest.messagebird.com's certificate, issued by '/C=US/O=DigiCert Inc/CN=DigiCert SHA2 Secure Server CA': Unable to locally verify the issuer's authority. Authorization failed. (no more tries)

This error message is now some 40 minutes old and a reboot fails to clear it. It's not obvious whether it's a genuinely fatal error or if the error isn't being cleared properly.

Any further ideas please?

Hi,

I have the problem too
See the log of the data log

SMS 2016-03-04 19:39:31 Error: WARNING: cannot verify rest.messagebird.com's certificate, issued by '/C=US/O=DigiCert Inc/CN=DigiCert SHA2 Secure Server CA': Unable to locally verify the issuer's authority. https://rest.messagebird.com/messages: 2016-03-04 19:39:35 ERROR 422: Unprocessable Entity. (no more tries)

MeteoOudkarspel wrote:https://rest.messagebird.com/messages: 2016-03-04 19:39:35 ERROR 422: Unprocessable Entity. (no more tries)

Please ignore the certificate stuff, that is something from wget which Meteobridge uses to push data to the https address of messagebird.
Error 422 is coming back from messagebird. Looking at error message from them (https://www.messagebird.com/de-de/developers#api-errors) this stands for "422 Unprocessable Entity: the resource couldn't be created". Unfortunately, this does not make it very clear either.

Digging deeper 422 is explained as:
The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415(Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions.

When does the error show up? When doing "Test SMS" in the "service definition" section at the bottom of "Services" tab or on "live data" tab when sms sending has been triggered? What does "Test SMS" in "service definition " section return?

BTW: the phone number to be called must be with country code but without leading "00" or "+".

chrysnic wrote:Actually, the "password" you are supposed to insert on Meteobridge is NOT the password of your MessageBird account. Once you are logged in on MessageBird, go to "API", then click on "API access (REST)" and then click on "Add access key". When asked, select the creation of a "live" key. Once the key is created, you should click on "Show key". This is the key that you should add to the Meteobridge SMS "Password" field. Once you hit "save", the red cross should change to a green tick.

The "Originator" can be anything (I think). It does NOT have to be your MessageBird username. It is the name that will show up as the sender of the SMS (when you receive the SMS).

This is how I got my SMS service to work with MB Pro.

I hope this helps.

chrysnic

Thanks, I still have to explain that in the wiki at the level of precision you just did. As you said, it is exactly working that way.

admin wrote:When does the error show up? When doing "Test SMS" in the "service definition" section at the bottom of "Services" tab or on "live data" tab when sms sending has been triggered? What does "Test SMS" in "service definition " section return?

My test setup is as follows:

In 'Event Definition' I simply have 'Test message' (but without any quotes) in the message textbox - just trying to keep it as simple as possible for initial testing. The phone number field has 447804740xxx - 44 being the UK country code and replacing the single 0 that would usually be used. Then clicking Test within the Event Definition section gives an immediate error in the Live Data section of:

2016-03-04 20:15:22 Error: WARNING: cannot verify rest.messagebird.com's certificate, issued by '/C=US/O=DigiCert Inc/CN=DigiCert SHA2 Secure Server CA': Unable to locally verify the issuer's authority. https://rest.messagebird.com/messages: 2016-03-04 20:15:23 ERROR 422: Unprocessable Entity. (no more tries)

and a red cross against SMS. No message is received on the phone. Maybe the test message is too simple or needs to be in quotes or ???

Are you using the API password which always begins with "live_"?

Yes. You have the remote login details which should be unchanged. You're welcome to take a look. But maybe time for a beer (I've had mine tonight!)!

Looking at our MessageBird account again today, there's a possibility that despite having paid the Paypal invoice yesterday, apparently successfully, the credits may not have been correctly applied to our account. Still trying to understand the MessageBird dashboard in detail and in the process of following up with them, but there's at least a possibility that the MB Pro SMS error messages simply aren't being very helpful in pinpointing the actual problem, which might just be a lack of credit (though I appreciate that MBP can only act on the error messages that it receives from MessageBird).

May be Monday before we're able to progress this further.

Update: Looking at the Access Log in MessageBird and clicking on the eyeball I can see that there have been 5 attempts to send a test SMS but they all seem to have been failing with the following error message:

{
"errors":[
{
"code":10,
"description":"no (correct) recipients found. Note: during your test period you can only send messages to yourself.",
"parameter":"recipient"
}
]
}

I was actually trying to send to a different phone number from our test number but that should have been OK since there should have been credit on the account. So right now it looks to me like MB Pro has been sending the SMS OK but there are two further issues:

1. MessageBird can be slow to credit new accounts with a payment (or maybe to convert from a test account to a live one) - it looks like it's still not happened for us after 24 hours.

2. MB Pro is either not receiving or is not displaying the full error message generated internally by MessageBird.

Further update: OK, since prodding MessageBird via email, just now received an email from them saying that payment has been processed (after 24 hours!). Tried the test message again and Hey Presto it now works! But I guess the two comments above still apply. And for anyone else having problems with the MessageBird service then it may well be worth delving into the detailed API logs inside your MessageBird account for further clues about the exact problem.

PWS wrote:1. MessageBird can be slow to credit new accounts with a payment (or maybe to convert from a test account to a live one) - it looks like it's still not happened for us after 24 hours.

2. MB Pro is either not receiving or is not displaying the full error message generated internally by MessageBird.

ad 1): yes, messagebird is a bit slow on activating your paid account. I sent them a message explaining that this is a bit unexpected when paying with paypal, where instant service activation is usually standard today. They replied that they need additional checking as there have been fraud incidents in the past. Therefore, it require additional financial checks to be performed first. I don't have details, but I guess they have a good reason to delay that for about 24 hours.

ad 2): the response does not include that detail. Good to know that messagebird itself is logging with more detail, so a user can lookup at his account, what was the reason of a failed transaction.

I was getting Error 422, also.
It was because my "originator" setting in Meteobridge did not match my login on Messagebird.
Once they matched I got my first SMS message.

And the only "identification" or originator info that came with the SMS message was a phone number from Los Angeles.