Tap on Push notification to connect automaticly
-
-
Hello Kl3m3n,
The latest version .62 doesn't work well with push notifications.
Most of the time they don't arrive, and everytime the device sends the notification, it freezes for a while, often even stops communicating and after a while resumes the MQTT connection.I haven't tested FCM notifications yet, but I'd like to know if Gui-O can support both?
At the moment, as it is, it is unusable.How can i get back to .61 version?
Thank you
Regards -
@Sato Hi.
Can you try again now? I have made some changes to the broker.
I don't see how the app can be the problem, since no major changes were made to IoT push notifications.
Do you have Mqtt clientId set or is it empty?
Yes, both types of push notifications can work (even simultaneously).
Regards,
Kl3m3n -
@Sato said in Tap on Push notification to connect automaticly:
Most of the time they don't arrive, and everytime the device sends the notification, it freezes for a while, often even stops communicating and after a while resumes the MQTT connection.
You mean when the microcontroller device sends a notification?
-
Hi @kl3m3n,
It's still not working properly. What I can see is that whenever Esp sends a notification, it freezes for about 5...10 seconds then it continues to communicate. I can see it on the led on the pcb board, which is always flashing as long as I have an internet connection.
With version 6.0 this didn't happen, it didn't freeze when sending a push notification.
Another issue is that the app now freezes so often that I have to force it to stop.
I haven't changed the App settings, the Mqtt clientid is still Not setRegards
-
Yes, right allways the Esp send the Push notification
-
@Sato What freezes? GUI-O app or ESP? Both?
Can you try setting the clientId to something unique and reconnect (disable and enable IoT notifications)? And see if the problem persists?
-
Hi @kl3m3n,
The problem perssist
Have set the client id to 1234, disable notification and enabled it again
Have reinitalize the Smartphone
The most notification don´t arriveThe Clear All continue not to clear the notifications buffer, but that is a other issue
that have nothing to do with the problem, i thinkIs it possible to update back to 6.0 to make tests again?
Regards
-
@Sato Hi.
I have tested (again) the IoT push notifications and I cannot reproduce none of the problems you are experiencing.
- I receive all notifications that I sent (with QOS level 1 or 2, I get them even if notifications are disabled and I enable them).
- It works if I set the clientId or keep it empty.
- The number of notifications shown corresponds to the setting "Notifications to show". When the set number of notifications are reached, the oldest is pushed out.
- If I press "CLEAR ALL", all notifications are cleared
I will try it on other Android devices and using ESP32.
If I remember correctly you've had some similar problems with notifications in the past and I as far as I remember I did not do any fixes then.
Can you try another Android device?
Regards.
Kl3m3n -
Hi @kl3m3n,
Tomorrow I'll test it with another Esp32 and another cell phone and give you feedback
Yes, when I press Clear All the notifications disappear, but when the next notification arrives the others that already existed before pressing Clear All appear again, shouldn't only the last one appear since I supposedly "deleted" the previous ones?
Regards
-
@Sato said in Tap on Push notification to connect automaticly:
Yes, when I press Clear All the notifications disappear, but when the next notification arrives the others that already existed before pressing Clear All appear again, shouldn't only the last one appear since I supposedly "deleted" the previous ones?
I cannot reproduce it. When I "CLEAR ALL" and send a new notification, only the new one appears.
Are you sure you are not storing and sending old notifications on ESP side?Can you give exact steps for this? So I will try to follow them with my tests? Also for other tests, can you give steps so I can try to reproduce the exact steps?
Best regards.
-
Hi @kl3m3n,
Strange, I'm shure that only one Push will be send every time.
I'll check it tomorrow on the serial monitor too
Regards
-
@Sato
FYI - I use this for testing MQTT:It's free and it's easy to setup. You can get the credentials from the example. Use 1883 port without SSL.
-
-
Hi @kl3m3n,
Sorry, sorry. The problem is solved, it was the Spiffs on my Esp32. Now it works.
Best regards
-
@Sato said in Tap on Push notification to connect automaticly:
Hi @kl3m3n,
Sorry, sorry. The problem is solved, it was the Spiffs on my Esp32. Now it works.
Best regards
Which problem is solved?
- The GUI-O application freezing?
- The "CLEAR ALL" button?
Can you briefly explain?
Thanks.
Regards,
Kl3m3n -
@Sato said in Tap on Push notification to connect automaticly:
Hi @kl3m3n,
Thank you
Im moment i not know how to use it with the esp.Regards
I meant for testing the GUI-O MQTT functionalities (e.g., IoT push notifications), before implementing your application on ESP.
You could of course also use this with ESP...
-
Hi @kl3m3n,
When Esp detects a fault on some of the selected pins, it appent the fault to a SPIFFS file and also sends a push notification. What was happening, I'm not sure why, was that writing to the file was taking so long that most of the time Mqtt communication would stop working during this period and when it was re-established Esp had already sent the notification and so I no longer received it on Gui-O. After reloading the virgin files back into SPIFFS, it worked again.
On the subject of Clear All, I've seen that it works after opening the App, so I think that's fine.
Again, I'm sorry to have been bothering you with this problem, which turned out to be on my end, but it coincided with the update of the App version and that led me to think that this problem came from there.
This has also served to learn a little more.Thanks for your support
Regards
-
-
@Sato Hi.
I cannot add the feature you suggested.
But I've implemented device filtering by name. This should help.
See version 1.0.66.
Best regards,
Klemen
