search

domoticz / domoticz-android

Domoticz Client Application for Android Devices
104 stars 69 forks source link

Android UUID not valid anymore with newer androids? #669

Closed Olifant1990 closed 1 year ago

Olifant1990 commented 1 year ago

Describe the bug I have switched to a new Android phone, the Nokia X20 with Android 12. When is connected the Domoticz app with my Domoticz server, I saw a new user under Setup -> More options -> Mobile Devices. That user has type "Android31". But, the UUID seems odd and I cannot send a test push notification, it doesn't arrive. It seems the token is not correct anymore on new Android versions?

Screenshots !!! afbeelding

Smartphone (please complete the following information):

galadril commented 1 year ago

The UUID mechanism is indeed changed, its not really a phone id anymore but an unique id assigned for the Domoticz app. But this should all still work.. sometimes i just get a new id and then register the phone again as a new phone (cant remove the old as i dont have that id anymore..)

Just filter on 'Last seen' and test the latest UUID for your phone.

image

Please try and close this issue if that works

Olifant1990 commented 1 year ago

Indeed I got it to work, but only after going to notification settings in the app and press Google Cloud Messaging-ID (to send to Domoticz). Nothing changed in the mobile user overview, but test button sends a test messages and it is being received at my phone.

Will see how much my UUID is changing, hope not much. I have a lot notifications which are depending on a specific phone. So a new phone registration should not be a right solution when an UUID changes.

galadril commented 1 year ago

Closing the issue for now. I've tested this locally with a new device.. and after Android OS update and my UUID was pushed correctly