Cloud message receive not working?

[hou...@gmail.com]

Hi,

Is it just me or receiving cloud messages not working?
Already tried regenerate new secret, reauthorize Automate on my google account and then re-add account to block, send message thru https://llamalab.com/automate/cloud/message and also directly from curl from my server. Also tested on latest Automate alpha.
I am using it in one profile more like a year without any problem and now the flow still waiting to receive message.

Thanks for any help.

[Henrik "The Developer" Lindqvist]

Servers restarted.

[hou...@gmail.com]

Can you confirm that messages are received by google?
I just tried it numerous time and still not working for me.

On Thursday, February 2, 2017 at 12:26:15 AM UTC+1, Henrik "The Developer" Lindqvist wrote:

Servers restarted.

[c...@taranis.org]

Not receiving messages either.

[c...@taranis.org]

Any luck restoring this functionality?

[Henrik "The Developer" Lindqvist]

Sure, it's been running ever since. Does now too. Try rebooting the device.

[Christophe Kalt]

Hm, still no luck.

My problem might have started earlier and/or be different

Not sure about timeing, as I have switched devices couple times last month and don't have old logs.

--
You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/lwGlAoCdvQc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-user+unsubscribe@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at https://groups.google.com/group/automate-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/9528db3d-99b0-44a6-98e9-d005531ac03b%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Henrik "The Developer" Lindqvist]

Try tapping an Google account field in any of the Cloud messaging block to re-register the account.

On Thursday, February 16, 2017 at 4:23:43 PM UTC+1, Christophe Kalt wrote:

Hm, still no luck.

My problem might have started earlier and/or be different

Not sure about timeing, as I have switched devices couple times last month and don't have old logs.

[Christophe Kalt]

That did it, thanks!

[daniel...@gmail.com]

Could it be, that a restart is required again? Notifications that did work yesterday don't work anymore today.

[Henrik "The Developer" Lindqvist]

Server restarted.

[daniel...@gmail.com]

That fixed it for a while. Stopped working though again. Paused my testing about half an hour ago and it worked until that after your restart. Now trying to continue and the messages don't arrive again.

[Henrik "The Developer" Lindqvist]

Restarted, again. I just noticed it myself.

I don't know what's going on. My server is still connected to Google and sending to them without error, but they just starts dropping upstream (server->GCM->device) messages until my server has reconnected (restarted).
Downstream messages (device->GCM->server) never has an issue. GCM isn't known for its reliability but this is ridiculous since there's no way of detecting it. I'll see what can be done.

[daniel...@gmail.com]

1. This is using the "old" cloud messaging, not firebase, right? Maybe an upgrade to firebase would improve stability?

2. Why not use the power of Automate? Have an old device you always have running send messages to itself, and if you haven't received a message for X hours or so, execute a POST request that triggers a scripted restart of the server.

[Henrik "The Developer" Lindqvist]

1. Yes. But from what i can see it's exactly the same API.
2. I do have an old device running an monitoring flow, but it currently can't restart the server. I'll rather fix the issue, if possible, that having to forcefully restart the server so often.

[daniel...@gmail.com]

1. The same API, but according to https://developers.google.com/cloud-messaging/android/android-migrate-fcm (all the way at the bottom), the endpoints have changed. Hence the firebase infrastructure may be in better shape if they just keep GCM running for legacy-users and don't spend much time on maintenance.

2. Of course fixing the issue would be the better way. But until the core of the issue is found, some workaround should be in place. And as long as the connection between your server and GCM is stable, there won't be any restarts. To reduce unnecessary restarts you could also delay the automatic restart to wait until three consecuitive messages failed to arrive.

And just out of curiosity: by server you refer to the process/application, not the whole machine, right? So there shouldn't be a long downtime.

[Henrik "The Developer" Lindqvist]

1. This issue was present from the beginning, before Firebase was even announced.
2. It's a somewhat "dangerous" workaround since it might be a temporary local issue on my monitoring device, and i would want to restart the service just because of that. But i'll investigate the possibility. I could also be an VPS issue, maybe my provider moves the instance and that affect open connections, i don't know. Yes, only the "Automate messaging service" is restarted, it only takes a few ms, but pending message aren't persisted so they would get lost, but they're lost by Google anyway so.
   

[danieljj...@gmail.com]

Hello.
How would I send and recieve a regular message with the cloud send blocks.

[Henrik "The Developer" Lindqvist]

On the sending device, use the Cloud message send block:
http://llamalab.com/automate/doc/block/cloud_message_send.html

On the receiving device, use the Cloud message receive block:
http://llamalab.com/automate/doc/block/cloud_message_receive.html

[Chris Lang]

Hello, I am not able to receive messages using the testing tool but can send/receive them using the cloud send block within the app.

[Chris Lang]

I should also say that I'm not able to send a message using PostMan either which is my ultimate goal. I get a 401 response for both http/https posting to the http://llamalab.com/automate/cloud/message endpoint

[Henrik "The Developer" Lindqvist]

401 likely means the "secret" has been invalidated, or that the Google JWT failed to be refreshed somehow. Try generating a new secret.

I just tested and the online endpoint works as expected for me.

[galaxy s2]

Still issues here? Trying to setp up cloud message recieve block but seems not working with online endpoint

[Henrik "The Developer" Lindqvist]

What's the error?

[Patrick Sullivan]

Is anyone else experiencing issues with Cloud Message today (16th Dec '21)?

Have tried muliple accounts and multiple devices (that were working yesterday), however can't seem to send/receive at all (even from the  https://llamalab.com/automate/cloud page). 

[Henrik "The Developer" Lindqvist]

Working as expected on my devices. Try rebooting the device, and re-authorize the accounts by clicking an Google Account field.