Page 1 of 2

Identical amazon fire - no notifications on one

PostPosted: Mon Aug 27, 2018 5:35 am
by mat
Adam,

I wonder if you can help. I have two amazon fire 7's, with the same settings on each, each paired as separate devices, each with different pairing keys,, however only one is allowing me to push control pages.

First is working.
Second is not receiving notifications.

I think the problem is no notifications being received by the not working, second fire 7. There are no notifications in the second fire notification tab, whereas the first I can see a list of page requests.

Both have the "Allow control page requests to "at any time".

Neither fire's have notifications blocked in the android settings.

Both can show control pages through normal operation and everything else appears to be working.

Here are the log device details for each:

Working fire

Code: Select all
Domotics Pad Mobile Client      Dumping details for DeviceID: 161908139
   Domotics Pad Mobile Client      address :
batteryLevel : 0
buttonGroupCount : 0
configured : True
description :
deviceTypeId : domoPadAndroidClient
displayStateId : isPaired
displayStateImageSel : SensorOn
displayStateValRaw : True
displayStateValUi : Paired
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState :
folderId : 1449619012
globalProps : MetaProps : (dict)
     com.duncanware.domoPadMobileClient : (dict)
          SupportsBatteryLevel : true (bool)
          address :  (string)
          deviceRegistrationId : 2tkVXVxhyW1CVxTeUB12 (string)
id : 161908139
lastChanged : 2018-08-26 19:14:04
lastSuccessfulComm : 2018-08-26 19:14:04
model : Android Remote Client
name : Domo Cinema 1
ownerProps : com.duncanware.domoPadMobileClient : (dict)
     SupportsBatteryLevel : true (bool)
     address :  (string)
     deviceRegistrationId : 2tkVXVxhyW1CVxTeUB12 (string)
pluginId : com.duncanware.domoPadMobileClient
pluginProps : com.duncanware.domoPadMobileClient : (dict)
     SupportsBatteryLevel : true (bool)
     address :  (string)
     deviceRegistrationId : 2tkVXVxhyW1CVxTeUB12 (string)
protocol : Plugin
remoteDisplay : True
states : States : (dict)
     batteryLevel : 0 (integer)
     batteryStatus :  (string)
     isPaired : true (bool)
     isPaired.ui : Paired (string)
     latitude :  (string)
     locationFixTime :  (string)
     longitude :  (string)
     modelName :  (string)
subModel :
supportsAllLightsOnOff : False
supportsAllOff : False
supportsStatusRequest : False
version : None


Second, not working

Code: Select all
 Domotics Pad Mobile Client      Dumping details for DeviceID: 1689403653
   Domotics Pad Mobile Client      address :
batteryLevel : 0
buttonGroupCount : 0
configured : True
description :
deviceTypeId : domoPadAndroidClient
displayStateId : isPaired
displayStateImageSel : SensorOn
displayStateValRaw : True
displayStateValUi : Paired
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState :
folderId : 1449619012
globalProps : MetaProps : (dict)
     com.duncanware.domoPadMobileClient : (dict)
          SupportsBatteryLevel : true (bool)
          address :  (string)
          deviceRegistrationId : zw8YGr171TrYTUsdWkT3 (string)
id : 1689403653
lastChanged : 2018-08-27 14:57:33
lastSuccessfulComm : 2018-08-27 14:57:33
model : Android Remote Client
name : Domo Front row
ownerProps : com.duncanware.domoPadMobileClient : (dict)
     SupportsBatteryLevel : true (bool)
     address :  (string)
     deviceRegistrationId : zw8YGr171TrYTUsdWkT3 (string)
pluginId : com.duncanware.domoPadMobileClient
pluginProps : com.duncanware.domoPadMobileClient : (dict)
     SupportsBatteryLevel : true (bool)
     address :  (string)
     deviceRegistrationId : zw8YGr171TrYTUsdWkT3 (string)
protocol : Plugin
remoteDisplay : True
states : States : (dict)
     batteryLevel : 0 (integer)
     batteryStatus :  (string)
     isPaired : true (bool)
     isPaired.ui : Paired (string)
     latitude :  (string)
     locationFixTime :  (string)
     longitude :  (string)
     modelName :  (string)
subModel :
supportsAllLightsOnOff : False
supportsAllOff : False
supportsStatusRequest : False
version : None



Both fires have a schedule set to "send control page.." every 5 minutes. The first works, the second doesnt - i put this down to the lack of notifications received by the second. I've checked the schedule for "dumb" factor by switching the schedule for the first fire to the second - this doesn't work. Both are on the same network, both have internet access, so shouldn't be a network issue.

Tried a reboot on both devices.

Debug log shows the following


Schedule Domo cinema 1
Schedule Domo cinema 2
Domotics Pad Mobile Client DebugControl page display notification sent successfully
Domotics Pad Mobile Client DebugControl page display notification sent successfully


Deleted app on the second fire, along with the device/schedule - reinstalled app, recreated the device and added a new schedule - verbos logging as follows (and above device dump updated):

Code: Select all
   
   Domotics Pad Mobile Client Threaddebug Queuing control page display request notification command for 161908139
   Domotics Pad Mobile Client Threaddebug Queuing control page display request notification command for 1689403653
   Domotics Pad Mobile Client Threaddebug Plugin Command queue has 2 command(s) waiting
   Domotics Pad Mobile Client Threaddebug Control Page Display Notification Send Command: DevicePairID=2tkVXVxhyW1CVxTeUB12; Page=417439771
   Domotics Pad Mobile Client Threaddebug Push Notification Payload=pageName=Cinema+Intergrated+control&pageRequested=417439771&devicePairingId=2tkVXVxhyW1CVxTeUB12
   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 Threaddebug Plugin Command queue has 1 command(s) waiting
   Domotics Pad Mobile Client Threaddebug Control Page Display Notification Send Command: DevicePairID=zw8YGr171TrYTUsdWkT3; Page=417439771
   Domotics Pad Mobile Client Threaddebug Push Notification Payload=pageName=Cinema+Intergrated+control&pageRequested=417439771&devicePairingId=zw8YGr171TrYTUsdWkT3
   Domotics Pad Mobile Client Threaddebug Control page display notification response: [204]
   Domotics Pad Mobile Client DebugControl page display notification sent successfully


Any help would be greatly appreciated.

Loving these cheap tablets and thanks for the hard work in allowing their use!

Cheers


Mat

Edited to update of further testing...

Re: Identical amazon fire - no notifications on one

PostPosted: Mon Aug 27, 2018 10:05 am
by RogueProeliator
Hmm, so based on the snippet from the event log, I believe the plugin is sending the push notification to the server successfully -- that process is disconnected so the plugin will get a success message as long as the GCM server accepts the message successfully (it doesn't mean it can be delivered). This leads me to look at the device itself.

Let's start with a simpler test -- try sending a standard push notification message (not a control page action, rather just a standard message). Two things to check -- first, obviously, you should get the push notification on the device... but also can check the push notification messages within the application for these messages in the even it doesn't appear.

Let's see how that test goes and move forward from there; it may point us in a particular direction to investigate.

Adam

Re: Identical amazon fire - no notifications on one

PostPosted: Mon Aug 27, 2018 10:23 am
by mat
Thanks Adam,

sent a hello world notification from an action:

Code: Select all
   Action Group                    test front row
   Domotics Pad Mobile Client Threaddebug Queuing push notification command for 1689403653
   Domotics Pad Mobile Client Threaddebug Plugin Command queue has 1 command(s) waiting
   Domotics Pad Mobile Client Threaddebug Push Notification Send Command: DevicePairID=zw8YGr171TrYTUsdWkT3; Type=normal; Message=hello world
   Domotics Pad Mobile Client Threaddebug Push Notification Payload=action2Name=&action2Group=&notificationType=Alert&priority=normal&action1Group=&action1Name=&devicePairingId=zw8YGr171TrYTUsdWkT3&message=hello+world
   Domotics Pad Mobile Client Threaddebug Push notification Response: [204]
   Domotics Pad Mobile Client DebugPush notification sent successfully


Nothing on the troublesome fire - ether in the notifications or the app. Repeated the same action with the first fire selected and the message appears on the first fire as it should.

I agree my suspicions are something with the the device itself. I have cross checked all of the settings between the two and they are the same. Not sure if it could be blamed on the fact that i restored from the first fire's backup!

Is it easiest for me to factory re-set it and go through the process again?

Thanks again

Mat

Re: Identical amazon fire - no notifications on one

PostPosted: Mon Aug 27, 2018 10:58 am
by RogueProeliator
Not sure if it could be blamed on the fact that i restored from the first fire's backup!

I don't think that would affect anything on the DomoPad side of things, but I'm not really sure on the Google Play side -- especially given how this is side loaded onto the device.

Is it easiest for me to factory re-set it and go through the process again?

I hate to tell you to do that, but it is probably the best option. You might could get away with removing the Google account and re-adding it? Maybe... If not a factory reset and setting it up again fresh should get you going.

Adam

Re: Identical amazon fire - no notifications on one

PostPosted: Mon Aug 27, 2018 11:26 am
by mat
Adam,

Happy to try the factory reset - it didn't take long. Was just asking in case it was something simple! :)

Will let you know either way.

Cheers

Mat

Re: Identical amazon fire - no notifications on one

PostPosted: Thu Oct 04, 2018 6:55 pm
by Decker
Were you able to get your second fire working? I just installed on my second fire and I'm unable to get push notifications and control page pushes working as well. Any tips if you were able to get them working?

Re: Identical amazon fire - no notifications on one

PostPosted: Thu Oct 04, 2018 10:00 pm
by RogueProeliator
Though it sounds simplistic, double check that all your versions - Google Services & Domotics Pad especially - match up between the two tablets.

If you haven't already, unpair it with Indigo and re-pair it.

Re: Identical amazon fire - no notifications on one

PostPosted: Fri Oct 05, 2018 3:24 pm
by mat
Not had a chance yet, work got busy - its on my to-do list and I was hoping to get to it on Sunday, but looks like we now have other plans.

I'll repost here as soon as I have some results.

Re: Identical amazon fire - no notifications on one

PostPosted: Fri Mar 15, 2019 1:04 pm
by whmoorejr
Following....

Having a similar issue. I just upgraded my kids' fire tables.... So I've added four 2015 Fire7s and one 2018 Fire8 to my ecosystem. The Fire8 doesn't want to receive control pages or standard notifications..

Re: Identical amazon fire - no notifications on one

PostPosted: Thu Mar 28, 2019 3:22 pm
by whmoorejr
mat wrote:
I have two amazon fire 7's, with the same settings on each....


Are both of your 7's the same year?

I know there have been issues with the recent generation changes of the echo and dot line working (or not working) with the indigo Alexa-Hue Bridge plugin... wondering if we are hitting a similar wall here. In my setup, 4 out of 4 2015 fire 7's are running domopad without issue. The one 2018 fire 8 is the wonky one of the group that seems to be having communication issues.

Re: Identical amazon fire - no notifications on one

PostPosted: Sat May 11, 2019 7:34 pm
by RogueProeliator
Have any of you made any progress on the issue with your latest Fires? Just curious... My son just inherited a Fire 8 that is only a couple of months old and I can install the app and try it out there if you guys are still having issues.

Re: Identical amazon fire - no notifications on one

PostPosted: Sat May 11, 2019 7:46 pm
by whmoorejr
No change on my end. My 7s have no issue with pushing out a control page change. The 8 won't change. All settings are the same between devices.

Re: Identical amazon fire - no notifications on one

PostPosted: Sat May 11, 2019 7:50 pm
by RogueProeliator
No change on my end. My 7s have no issue with pushing out a control page change. The 8 won't change. All settings are the same between devices.

Two questions for you... First, what setting do you have set in the Settings -> Control Page -> Allow Control Page Request? Second, what is shown when you attempt to push out the CP page -- is it showing another CP or is some other application in the foreground?

Re: Identical amazon fire - no notifications on one

PostPosted: Mon May 13, 2019 7:46 am
by whmoorejr
Settings -> Control Page -> Allow Control Page Request? "At Any Time"

Second, what is shown when you attempt to push out the CP page -- is it showing another CP or is some other application in the foreground? There is no change on the device. I leave a default CP on at all times set as the launch page (User Interface). With or without domopad in the foreground makes no difference. The call to change the page on the device does nothing and there is nothing I see in the log to indicate any sort of error. It's like the 8 just chooses to ignore the command.

Re: Identical amazon fire - no notifications on one

PostPosted: Mon May 13, 2019 10:58 am
by RogueProeliator
With or without domopad in the foreground makes no difference. The call to change the page on the device does nothing and there is nothing I see in the log to indicate any sort of error. It's like the 8 just chooses to ignore the command.

With DP showing another control page, we should be able to make it work... unless that device or maybe Fire OS version is doing/sending something unexpected in terms of the notification and DP can't read the data.

If you were NOT in DP at the time, I would suspect that the Fire OS had implemented a feature that is coming to Android Q which *might* prevent switching to DP when it is not already in the foreground. But that clearly isn't the issue when DP is already in the foreground...

Let me add some additional logging into the next beta around this issue and we can see if we can determine anything more.