I updated to 4.2.1 yesterday evening and after that I noticed that the notifications were broken again. Remote access was working fine all the time.
I tried stopping OH, cache clearing, starting OH. No effect. Restarting the whole Raspberry Pi also didn’t change anything.
I tried again this evening with a full Raspberry shutdown (instead of a reboot), then powering it on again. After an additional reboot (to fix issues with access to a virtual USB COM port), the notifications suddenly worked again.
I was planning to get the Debug logs if those restarts wouldn’t have worked. Therefore I don’t have them now, but during the first reboot after the update I noticed only the log entry of the successful connection to the cloud service and no sign of a connection drop afterwards.
I’m not sure if something in general is messed up with my openhabian installation, if a normal update is able to break it
I think I should try to find some time to reinstall the whole system in the next weeks…
If there’s any way I can support with this topic, let me know - but I don’t yet know how to trigger the problem
Same here the original issue we had last year is back I think. No error in OH log, all messages delivered to cloud, test notification works on cloud, but nothing is pushed to my iPhone and iPad since about 2-3days ago
I’m having the same problem on Android (Pixel 6a) since upgrading my OH to 4.2 over the weekend.
Push Notifications via Rules very hit and miss - almost like they’re being throttled in some way.
With Debug Log enabled I can see my local instance sending them, but with an approximate 20% failure rate in delivery.
As a simple test, I created a Rule that sends a specific User a test message every 30s, 5 times. Roughly only 2/3 of those messages are received as a Push Notification. The OH Cloud shows them as being sent, but I never receive them.
I get the same failure rate when doing directly from OH Cloud, so the Cloud instance appears to be sending but they are not received on the phone.
This would suggest its not a local instance issue as OH Cloud exhibits the same, but I’m not sure.