Announcing IoT push notifications
-
Please check out the instructions and example code at:
https://www.gui-o.com/examples
or
https://www.gui-o.com/examples#h.m32xlxsbye05
BR,
kl3m3n -
Hi @kl3m3n,
First of all, congratulations for the good work, it is very useful
I am doing tests, the ESP32 sends a notification every 20 seconds, it works fine, but after a while it stops working, my phone freezes as well as the Gui-O, that one, then doesn't open and shows the screen in black
What could I be doing wrong?
Another question is, in real operation, after receiving a notification, do I need through Gui-O, inform the ESP32 that the notification arrived successfully?
Best regards
-
@sato try with version 1.0.4. Do you still experience problems?
You should also disable all battery and related optimizations for the GUI-O app or the OS will kill the service...
BR,
kl3m3n -
Hi @kl3m3n,
Updated to 1.0.4
All Batterie and other permissions deactivedProblem the same.
Now i have disconnect the ESP32 to stop sending notificationsTo deactivate Push Notifications in Gui-O, I have to restart the cell phone
Best regards
-
Hi @kl3m3n,
Attached the screenshot. If i actived the Push Notifications on the Gui-O, with the 1.0.4 i can't open the Gui-O App anymore
Regards
-
@sato could you please also post the Android version and phone model?
-
-
Now i use the other Samsung A30s with the 1.0.4.1, it receive the Push notifications but can't open the Gui-O anymore
Regards
Fernando Santos -
@sato can you please send me the Android version (not GUI-O version)?
-
Now, with your example code, the Samsung Galaxy A30s works the Push notifications, on that is Android10
On my other Samsung Galaxy M22, the notifications no work more with the same example code "changed obvious the Application UUID", this phone have Android11
Regards
-
@sato Hello, I see the crash reports from the M22... I am making a call on null value (although Android API says the value I am calling cannot be null in this case). I will add a null check and upload the app to beta testers (I believe you are a beta tester? You can check this on Google Play Store, GUI-O listing...).
BR,
kl3m3n -
-
Hi @kl3m3n,
The current situation!
I added in your example code the sending of notifications automatically every 60 seconds via the milis function
The cell phone with Android10 gets the notifications with the App closed, but if I try to open GUI-O, it freezes with a black screen
The cell phone with Android11 gets the notifications only if the App is open, i.e. it doesn't need to is connected, it only needs to be with the GUI-O logo Connect . Create . Control, but when it receives the Notification this does not overlap the image that is on the screen, I do not know if it is so and I can not compare with what Androi10 has because it does not open the Gui-O
Hope this helps
Regards
-
@sato hello, thank you for the update... I am reading that Samsung is killing services like crazy (especially newer devices).
They have very aggressive battery optimization techniques that break the concept of foreground services. Please see:
https://dontkillmyapp.com/samsung
Try following the instructions to (at least) paritially fix this. Please keep me informed.I have an older Samsung phone (Android 7) and newer Xiaomi phone (Android 11) and I do not experience the issues that you have.
I will also try to find a solution for this.
BR,
kl3m3n -
Ok, Thank You
When you have some global solution, that is, independent of the manufacturer of the cell phone would be ideal.
It is complicated that to use this great GUI-O functionality you have to use some specific equipment.When have news, please informe us.
Regards
-
Hi @kl3m3n,
Sorry, i again with questions.
I can send message from ESP32 to Whatsapp or Signal trough a Bot, on my both Samsung Mobiles, this Apps works with background service too, or it's diferent?
Another questions is, how can get this Text "OF4321" like the attached Scrennshot, to a String variable
-
@sato
I have been running the push notification service for approx. 10h (Android 7, Samsung Galaxy S6), without any problems sending the notification every 30 seconds. Everything still works ok. So, I am convinced that the service works ok. I will try it on my Xiaomi device also (Android 11) for prolonged duration, but I also don't see any problems here...Regarding Whatsapp - OEMs (e.g., Samsung) probably keep some list of whitelisted applications that the OS is not allowed to kill, so there is definitely some difference here.
This is (in my opininon) one of the few drawbacks of Android systems (comapring to Apple devices) - due to open sourceness, the OEMs can do what they want, often breaking some core functionalities.
Regarding your second question - when creating a device, specify the optional user name. This is then sent in the usr: parameter. So:
Quick pair -> IoT devices -> add a new device -> specify device and user name.BR,
kl3m3n -
Hi @kl3m3n,
I will try to explain
When I supply the pcb with ESP, I create a device on my phone, with for example, New_987 and no username, from there, I have the In and Out topics that i put in the code to compile in the ESP, the client can later change this name New_987 and it continues working.
Now, if I also use the username and the client makes changes, it stops working.
That is why I ask how to read this device name that appears in the sub-menu of Quick connect, to a String variable, as I sent in the post with the screenshot, so I don't need the username. Please test what I am mentioning.Regards
-
@sato Why don't you specify the user name also? You will then be able to filter incoming messages based on user name also (not just device name, which can be the same on different Android devices).
Let's continue this topic here:
https://forum.gui-o.com/topic/65/add-the-iot-name-to-init/7BR,
kl3m3n -
@kl3m3n said in Announcing IoT push notifications:
@sato
I have been running the push notification service for approx. 10h (Android 7, Samsung Galaxy S6), without any problems sending the notification every 30 seconds. Everything still works ok. So, I am convinced that the service works ok. I will try it on my Xiaomi device also (Android 11) for prolonged duration, but I also don't see any problems here...Regarding Whatsapp - OEMs (e.g., Samsung) probably keep some list of whitelisted applications that the OS is not allowed to kill, so there is definitely some difference here.
This is (in my opininon) one of the few drawbacks of Android systems (comapring to Apple devices) - due to open sourceness, the OEMs can do what they want, often breaking some core functionalities.
Regarding your second question - when creating a device, specify the optional user name. This is then sent in the usr: parameter. So:
Quick pair -> IoT devices -> add a new device -> specify device and user name.BR,
kl3m3nRunning Xiaomi Mi 9 Lite for 5h, push notification every 30 s, everything works ok.
BR,
kl3m3n