Failing to Push to Fire8 Tablets

Posted on
Tue Oct 08, 2019 10:55 am
Busta999 offline
User avatar
Posts: 672
Joined: Mar 30, 2016
Location: Wales UK

Failing to Push to Fire8 Tablets

Updating all the screens that have been using DomoPad for a couple of years.

So many thanks for that.

Looking at updating push notifications to the Amazon Tablets.

So far unable to get

Notifications
Speak Announcements
Send Control Page
Request Status
Example of error encounter with High Debugging on.

I am running 2.2.6 DomoPad Plugin. 7.4 Indigo. on MacOS 10.12.6.

Code: Select all
   Action Group                    Lounge Tablet - Test Action
   Domotics Pad Mobile Client Threaddebug Queuing push notification command for 1017838625
   Domotics Pad Mobile Client Threaddebug Plugin Command queue has 1 command(s) waiting
   Domotics Pad Mobile Client Threaddebug Push Notification Send Command: DevicePairID=2cLQwM5ZmGhGAIfeuNJm; Type=normal; Message=test
   Domotics Pad Mobile Client Threaddebug Push Notification Payload=action2Name=&action2Group=&notificationType=Alert&priority=normal&action1Group=&action1Name=&devicePairingId=2cLQwM5ZmGhGAIfeuNJm&message=test
   Domotics Pad Mobile Client Threaddebug Push notification Response: [503] {
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "backendError",
    "message": "com.google.android.gcm.server.InvalidRequestException: HTTP Status Code: 301"
   }
  ],
  "code": 503,
  "message": "com.google.android.gcm.server.InvalidRequestException: HTTP Status Code: 301"
 }
}
   Domotics Pad Mobile Client ErrorError sending push notification.


Is this a problem with Fire Tablets or is there something else going wrong here?

Any pointers welcome.

Thanks

Posted on
Tue Oct 08, 2019 3:25 pm
RogueProeliator offline
User avatar
Posts: 2333
Joined: Nov 13, 2012
Location: Baton Rouge, LA

Re: Failing to Push to Fire8 Tablets

Is this a problem with Fire Tablets or is there something else going wrong here?

That looks like your Fire tablets are holding on to an old push notification token that is no longer in use (Google depreciated that service). However, the latest versions of Domotics Pad (current is v1.9.2) are using the new servers. Try on just one tablet since it is a bit of a pain, but most users have succeeded in getting connected to the new server by uninstalling and re-installing the application. Note that this won't come back, this is just an artifact of the old library having been connected.

In the not-TOO-distant future I will have in-house direct connections available for push notifications (i.e. not going through Google's servers, it will talk directly to the IP). But that is a little bit off (in the planning and design phase now).

Posted on
Wed Oct 09, 2019 4:21 am
Busta999 offline
User avatar
Posts: 672
Joined: Mar 30, 2016
Location: Wales UK

Re: Failing to Push to Fire8 Tablets

Excellent !!!

Progress - thanks. Uninstalled, re-installed 1.9.2 - re-paired.

Sending a message to Speak is very cool and works.

Still running into some issues.

1. Request Device Status results in:-

Code: Select all
 
   Domotics Pad Mobile Client DebugPlugin preferences updated
   Domotics Pad Mobile Client      Debugging enabled... remember to turn off when done!
   Domotics Pad Mobile Client DebugCurrent IWS Plugin: v1.3
   Domotics Pad Mobile Client DebugIncluded IWS Plugin: v1.3
   Action Group                    Lounge Tablet - Test Action
   Domotics Pad Mobile Client ErrorError in plugin execution ExecuteAction:

Traceback (most recent call last):
  File "plugin.py", line 322, in processRequestDeviceStatusNotification
NameError: global name 'requestDeviceStatusNotification' is not defined

 


2. Send Notification - with button actions
Code: Select all
Domotics Pad Mobile Client Threaddebug Call to validate action: sendPushNotification
   Action Group                    Lounge Tablet - Test Action
   Domotics Pad Mobile Client Threaddebug Queuing push notification command for 97002777
   Domotics Pad Mobile Client Threaddebug Plugin Command queue has 1 command(s) waiting
   Domotics Pad Mobile Client Threaddebug Push Notification Send Command: DevicePairID=s8KAAQcpoouubzmbanZ4; Type=normal; Message=test test
   Domotics Pad Mobile Client Threaddebug Push Notification Send Action 1: Lounge Lights On => 376660060
   Domotics Pad Mobile Client Threaddebug Push Notification Send Action 2: Lounge Lights Off => 546891607
   Domotics Pad Mobile Client Threaddebug Push Notification Payload=action2Name=Lounge+Lights+Off&action2Group=546891607&notificationType=ActionAlert&priority=normal&action1Group=376660060&action1Name=Lounge+Lights+On&devicePairingId=s8KAAQcpoouubzmbanZ4&message=test+test
   Domotics Pad Mobile Client Threaddebug Push notification Response: [204]
   Domotics Pad Mobile Client DebugPush notification sent successfully

This is probably because I don't understand how this should operate/does Fire Tablet Support - i.e. I'll keep playing with it, but in the tests I have done Notifications sometimes just don't get through or have a very significant delay (5 or more mins) also when two buttons are shown in the notification only the second one performs the action even if you press the 1st .
Indigo - Domopad - Notification.jpeg
Indigo - Domopad - Notification.jpeg (183.1 KiB) Viewed 1217 times

Not an issue at all and most probably user error :-)

3. Send Control Page

Code: Select all
 Action Group                    Lounge Tablet - Test Action
   Domotics Pad Mobile Client Threaddebug Queuing control page display request notification command for 97002777
   Domotics Pad Mobile Client Threaddebug Plugin Command queue has 1 command(s) waiting
   Domotics Pad Mobile Client Threaddebug Control Page Display Notification Send Command: DevicePairID=s8KAAQcpoouubzmbanZ4; Page=441807091
   Domotics Pad Mobile Client Threaddebug Push Notification Payload=pageName=Heating%2FHot+Water+%26+Radiator+Demand&pageRequested=441807091&devicePairingId=s8KAAQcpoouubzmbanZ4
   Domotics Pad Mobile Client Threaddebug Control page display notification response: [204]
   Domotics Pad Mobile Client DebugControl page display notification sent successfully
   Domotics Pad Mobile Client      Process command: updateMobileDeviceStates


Nothing changed on the Fire8 tablet it did not change Control Page

None of which are issues I can't work around and are most likely User Error

Posted on
Wed Nov 13, 2019 2:19 pm
MR_ROBOT_ offline
Posts: 22
Joined: Feb 11, 2019
Location: Lancashire, UK

Re: Failing to Push to Fire8 Tablets

Hi, from reading this thread it seems that v1.9.2 is out, however I can't seem to find this in google play store (only v1.9.1)?

Im having the same issue with lack of ability to push CPs to Fire8 Tablet.

I get the following error in indigo log when trying to push a CP
Domotics Pad Mobile Client ErrorError sending control page display notification.


Am I missing something in order to get v1.9.2?

Thanks
MR_ROBOT_

Posted on
Wed Nov 13, 2019 3:17 pm
MR_ROBOT_ offline
Posts: 22
Joined: Feb 11, 2019
Location: Lancashire, UK

Re: Failing to Push to Fire8 Tablets

Right, seems like maybe I'd missed a setting in Domopad to allow Control Page control so I set it to Always Allow. Therefore I now don't get the previous Client Error message.

Now it seems to send the request to change the CP however nothing happens.
I turned on high debugging option and this is what it outputs.


Schedule Push Blank CP to Domopad
Domotics Pad Mobile Client Threaddebug Queuing control page display request notification command for 1999544136
Domotics Pad Mobile Client Threaddebug Plugin Command queue has 1 command(s) waiting
Domotics Pad Mobile Client Threaddebug Control Page Display Notification Send Command: DevicePairID=(removed this bit here in case private); Page=444625441
Domotics Pad Mobile Client Threaddebug Push Notification Payload=pageName=T_Blank&pageRequested=444625441&devicePairingId=ceGZ3DcSL4nB9HSyRfMQ
Domotics Pad Mobile Client Threaddebug Control page display notification response: [204]
Domotics Pad Mobile Client DebugControl page display notification sent successfully



Any idea why it isn't being actioned by Domopad Android Client?

Pairing all went smoothly so am stumped.

Hope you can help
MR_ROBOT_

Posted on
Sat Nov 16, 2019 8:04 pm
haychess offline
Posts: 16
Joined: Dec 21, 2015

Re: Failing to Push to Fire8 Tablets

Hey MR_ROBOT_

Apparently you have to sign up as a beta tester in order to get 1.9.2

Would have been nice if they actually explained that to you

Posted on
Sat Nov 16, 2019 11:19 pm
RogueProeliator offline
User avatar
Posts: 2333
Joined: Nov 13, 2012
Location: Baton Rouge, LA

Re: Failing to Push to Fire8 Tablets

This is probably because I don't understand how this should operate/does Fire Tablet Support - i.e. I'll keep playing with it, but in the tests I have done Notifications sometimes just don't get through or have a very significant delay (5 or more mins) also when two buttons are shown in the notification only the second one performs the action even if you press the 1st .

I just did a few tests and the second action button does seem to execute the push notification action... but I don't have a Fire setup to test this on, doing this on a standard Android device (well, tested two of them just to be sure). I'll see if I can commandeer my son's Fire and test it there. :-) In theory, though, it should work the same. Is there anything in the Indigo logs that indicates that the action group attempted to execute and failed maybe?

Nothing changed on the Fire8 tablet it did not change Control Page

The message from the logs indicates that Google accepted the Control Page change... are these always showing Domotics Pad, even when receiving the notification? And what setting do you have set for the Allow Control Page Request?

Adam

Posted on
Sat Nov 16, 2019 11:23 pm
RogueProeliator offline
User avatar
Posts: 2333
Joined: Nov 13, 2012
Location: Baton Rouge, LA

Re: Failing to Push to Fire8 Tablets

Any idea why it isn't being actioned by Domopad Android Client?
Pairing all went smoothly so am stumped.

It seems several are having issues on the fires as per this thread, which makes me start to wonder if the Fire is missing a library that is required or something. To be clear, you can still receive standard (message) push notifications, right?

Posted on
Sun Nov 17, 2019 2:37 pm
MR_ROBOT_ offline
Posts: 22
Joined: Feb 11, 2019
Location: Lancashire, UK

Re: Failing to Push to Fire8 Tablets

RogueProeliator wrote:
Any idea why it isn't being actioned by Domopad Android Client?
Pairing all went smoothly so am stumped.

It seems several are having issues on the fires as per this thread, which makes me start to wonder if the Fire is missing a library that is required or something. To be clear, you can still receive standard (message) push notifications, right?



Hi Adam,

Just installed v1.9.2 and seem to be having same problem with lack of control page change request not being actioned.
Logs state same as before with successful sent message but no change on Domopad app.

I have also just tried to send a push notification to Domopad to test that part and I cant seem to get them to work either. Iv’e gone through all the settings on domopad android client and I don’t think I’m missing anything.

:(

With High debugging on I get a “Push notification sent successfully” which seems to suggest it got sent correctly but still nothing on Domopad.

I’m not sure if this is normal or not but on both notifications and control page requests I get a log entry ending with ...response: [204]

Is this to be expected?
E.g. Control page notification response: [204]

Cheers
Andy

Posted on
Sun Nov 17, 2019 9:43 pm
RogueProeliator offline
User avatar
Posts: 2333
Joined: Nov 13, 2012
Location: Baton Rouge, LA

Re: Failing to Push to Fire8 Tablets

Just installed v1.9.2 and seem to be having same problem with lack of control page change request not being actioned.
Logs state same as before with successful sent message but no change on Domopad app.

Yeah, that version did not make any changes to push notifications so I wouldn't have expected it to really, unless the act of updating cleared something out (which was unlikely).

Is this to be expected?
E.g. Control page notification response: [204]

Yes, that indicates that the push notification request was accepted by Google's server for delivery to your device... that is an indication of success from the plugin -> Google server route.

Google relatively recently depreciated some services and my fear is that the Fire tablets are not able to connect to the new one. Can you send me your pairing ID (a PM is fine) for the tablet? This is the one that can be found in the device ID on Indigo for the paired tablet. I can use that to see if the device is at least connecting to the push notification server.

Adam

Posted on
Mon Nov 18, 2019 2:37 am
MR_ROBOT_ offline
Posts: 22
Joined: Feb 11, 2019
Location: Lancashire, UK

Re: Failing to Push to Fire8 Tablets

Hi Adam,

PM sent.

:)

Posted on
Thu Nov 21, 2019 9:24 pm
RogueProeliator offline
User avatar
Posts: 2333
Joined: Nov 13, 2012
Location: Baton Rouge, LA

Re: Failing to Push to Fire8 Tablets

I couldn't find any indication of a device with that pairing ID as having registered with the service. However, I do see others that I believe are Fire devices and running v1.9.+ as registering. My initial thoughts, then, is that something is going wrong with the Google registration so it is not making it to contact the server. Things that initially come to mind:

  • The device is somehow hanging on to an old connection that Google depreciated. With a full uninstall of the app then I would like to think it would grab a new connection... So while this remains a possibility, I don't think it is the most likely
  • The Google services on the device need updating -- these should auto-update BUT, things could go wrong. You should be able to test this by manually updating / install the latest version of the Google APKs that you initially installed to setup the Play store on the Fire.
The ultimate fix will be the next version of the application where by it will support WiFi communication, bypassing the Google servers and staying completely local. However, I suspect this feature is several months off for v2 as I am finishing up Geofencing test code.

If you have time to troubleshoot, try uninstalling the app, doing those updates, re-installing and testing. The notifications need to come through as messages before the control push notifications ever will come through.

Adam

Posted on
Fri Nov 29, 2019 5:24 am
MR_ROBOT_ offline
Posts: 22
Joined: Feb 11, 2019
Location: Lancashire, UK

Re: Failing to Push to Fire8 Tablets

RogueProeliator wrote:
I couldn't find any indication of a device with that pairing ID as having registered with the service. However, I do see others that I believe are Fire devices and running v1.9.+ as registering. My initial thoughts, then, is that something is going wrong with the Google registration so it is not making it to contact the server. Things that initially come to mind:

  • The device is somehow hanging on to an old connection that Google depreciated. With a full uninstall of the app then I would like to think it would grab a new connection... So while this remains a possibility, I don't think it is the most likely
  • The Google services on the device need updating -- these should auto-update BUT, things could go wrong. You should be able to test this by manually updating / install the latest version of the Google APKs that you initially installed to setup the Play store on the Fire.
The ultimate fix will be the next version of the application where by it will support WiFi communication, bypassing the Google servers and staying completely local. However, I suspect this feature is several months off for v2 as I am finishing up Geofencing test code.

If you have time to troubleshoot, try uninstalling the app, doing those updates, re-installing and testing. The notifications need to come through as messages before the control push notifications ever will come through.

Adam


Hi Adam,

Thought i'd post back and let you know how i got on.
It's starnge that you can't see my device ID as registered. I wonder whats ahppening there.
I tried your suggestions and completly removed all google services from Fire HD7 and also removed Domopad app. Re-installed everything and tried again but still no joy in getting either Notifications or Control Pages to push to my Fire HD7 device.
I think I'll just wait now for v2 as and when its available to get this part working for me.
Thanks for all your supoprt so far and suggestions.

MR_ROBOT_

Posted on
Thu Dec 19, 2019 3:40 pm
durosity offline
User avatar
Posts: 3944
Joined: May 10, 2012
Location: Newcastle Upon Tyne, Ye Ol' England.

Re: Failing to Push to Fire8 Tablets

Howdy

So I've actually been having what I believe to be the exact same issue as this myself, also with a current gen fire 8 tablet. Do you have any time estimates on v2 appearing? (Also even with these issues it's a wonderful app you've created.. it's what I wish M&J had time to do with Indigo touch on iOS.. I've bought the ultimate version of the app to show my appreciation for you efforts :D ).

Computer says no.

Posted on
Fri Dec 20, 2019 2:43 pm
RogueProeliator offline
User avatar
Posts: 2333
Joined: Nov 13, 2012
Location: Baton Rouge, LA

Re: Failing to Push to Fire8 Tablets

Do you have any time estimates on v2 appearing? (Also even with these issues it's a wonderful app you've created.. it's what I wish M&J had time to do with Indigo touch on iOS.. I've bought the ultimate version of the app to show my appreciation for you efforts :D ).

I tried to post an estimate, but the forums kept saying "Your post has been blocked due to no ETAs allowed on the forums. Sorry." :-)

So I had hoped to have a test out for the geofencing changes last month but the latest versions of Android were fighting me; ironically not on the geofence triggering, on it showing a simple freaking notification that it fired. :-| Anyway, I should know better time-wise after the holidays.

I am going to TRY to get it to the Amazon App Store for those of you with Fire tablets, but not promises; it depends on how far apart the APIs really are... but I am committing to giving it a shot this go-around.

Adam

Who is online

Users browsing this forum: No registered users and 1 guest