Just tested, the action buttons are implemented in the testflight app, and are working! @digitaldan thanks for this implementation, it works great so far, also on the apple watch (which I was hoping for)
!
2 Likes
That’s great news, is there any document on how to use the action buttons?
See openHAB Cloud Connector - System Integrations | openHAB
I’m using this as test, but it’s not error free (icons are not working yet, I’m debugging my rules):
sendBroadcastNotification("Testmessage with text", "Title", "Motion Tag", "Motion Detected", "motion-id-1234", null, null, "OK=command:SWI_TestNotification:OFF", "Again=command:SWI_TestNotification:ON", null)
Wonderful, will try something with my charging automations, so I can select when to charge with action buttons
I use the latest TestFlight version of the App and notifications are working fine. What stopped working however is the hiding of notifications which was working earlier. I have a rule that notifies me when the washing is done and I try to hide this notification when someone switched off the device. This was working fine for a while but it stopped working at some point. Since I had the rule untouched I assume that it could be related to an app upgrade but I’m not entirely sure that there was an update that was causing this.
By the way: I was a bit confused that the notificationBuilder requires a message also when you just want to hide a notification. I just used the same message I display for showing the notification but I guess it could be anything, correct?
I can also confirm icon doesn’t work for me - whether just icon name or with <>.
Actions are working which is great, so I can now send notification when I plugin charging cable to my el car and choose what period I want it to charge, thanks a lot to @digitaldan for the great work and look forward to the release
I also confirm the test version 3.04 solves the issue for me.
It would be great to have an official release with the fix.
Thanks guys!
It is unrelated to issue, but maybe my case will help you debug information.
I was once asked to assist maintenance of nodejs app which dispatched notifications to IOS and Android devices. Due to appstore policy we had to update mobile application, as a result we lost push notifications on Apple. It took a bit until I realized where issue was coming from. In my case it was caused by change of IOS registration token. Not sure if that was IOS or azure event hub library, effectively APNS device tokens were changed. There is a bit of dance with push notifications on device end, but effectively due to that little move, old mapping between nodejs app subscription tag and APNS tag become stale.
Situation was quite similar to what you see - events dispatched by nodejs app reached APNS, but they did not find a valid target. There was no single sign of error anywhere. It just didn’t work.
I think similar case to above was already addressed with one of recent openHAB mobile app updates, but I’d put extra attention to a fact if notifications stopped working all of sudden, or after mobile app update.
Hi all,
I’ve been testing 3.04 through testflight for 2 days and unfortunately I’m seeing mixed results getting notifications on Apple devices.
For instance, I open my garage door and I do get the notification right away.15s after I close this exact same door and no notification gets fired. If I open the Notifications panel in the App I do see both notifications (The Open + the Close). So it seems to be better compared to the official app release but not perfect… Not sure why we observe random results now whereas it was ok or ko before…
@digitaldan, is there anything I could do to help troubleshoot this issue ?
Thanks all!
It would be helpful if you showed the actual line of the rule sending the message so we can see what params there are, screen shots of the notifications in the app or cloud service, and screenshots of the notifications on your phone. There are no known issues with the newer IOS apps and delivery, so I’m guessing this is something else. As much detailed information as you can give would be helpful.
Hi @digitaldan,
Thanks for your response.
Sure! I can do that.
First of all, here is a rule script that I use to reproduce the issue (script that sometimes fires iphone or ipad notifications and sometimes doesn’t).
As you can see, this is actually a very simple one that simply returns when a door gets opened or closed.
Today I went back home after a run and I opened the garage door at 2:28PM to get in my house. I closed the door right away (15s) after I was in.
Here is my iphone lock screen: As you can see, I did get the notification for the OPEN action but not for the CLOSE one:
Note that it is yet 2:29PM on my iphone lock screen and the CLOSED notification was supposed to show up at 2:28:28PM.
However, when I opened the app (3.04), I was able to see both notifications. The close one 14s after the Open one. See below :
The same applies after I I connected to myopenhab.org. I can see both notifications:
As a result, I doubt it has anything to do with this particular script because I’m able to reproduce this with many other scripts that trigger notifications. Similarly, I doubt it is related to my own setup because we see that the application notifications panel and myOpenhab.org do show the notification that I didn’t get on my apple devices. So it is likely an issue on the server side or at the app level. My 2cts…
Notifications (outside of the problem discussed earlier in this thread) have been very reliable so far. It is actually the first time I see they randomly fail.
As many people in this community, I do use them quite a lot. The fact that those randomly fail now make me a bit nervous: Especially because of my alarm since I can react to any intrusion before the siren gets fired.
So I’ll do my best to help you with this! Do not hesitate to request more info !
Thanks a lot!
Cheers.
Jerome.
I have the same experience with my installation. Notifications are send to myopenhab (you can see them online), but they are not always pushed to my iPhone, although they appear in the notification section in the app.
Sometimes it works with a “ping”, sometimes it doesn’t. It’s very random.
Thanks Jerome for the detailed information. I was able to track this down pretty quickly, the code was using a deprecated Google firebase function to send broadcast messages. Google started disabling this by purposely making a % of calls using this API fail, similar to some other API’s they have depreciated in the past. Its a one line fix, so i’ll push that out shortly.
This is deployed, let hope that does it 
2 Likes
Many thanks @digitaldan
I’m very glad you’ve been able to narrow it down so quickly! thanks a lot for all your actions! This is so helpful!
I’ll continue to monitor this in the next couple of days and I’ll let you know !
Thanks once again and you have a great week end ahead !
Jerome.
I’m curious how do you implement the systemStarting? Would like something similar to void running rules during start up…
Dan,
the App Store provides v3.0.1 whereas testflight is already on v3.0.4
I saw that v3.0.5 is released but not yet available on App Store. Is it about to be available shortly?
Just as a side note to all others that the App Store version is not the latest.
The version on the app store is the latest release, there is no functional difference between them other then the version number that the app store shows. I believe if you actually go into the app, you will see another version number in the settings. The only version we published is the latest build.
Yes, the app shows v3.0.5 (11)
Hi @digitaldan :
I tried to use icon but didn’t manage to get it work, is it just passing the icon name as string without <>?