Inari Blue Notifier - app to make the Inari Blue logo react to calls and notifications

Thank you so much!!

I shall piggyback on your daemon and expand LaDitDah (morse app) to use it!

1 Like

The favourites are done, you can select a different pattern.

5 Likes

Oh and I recently make ‘Inari Knock’, but that’s a bit hackish.
Would you accept a PR to incorporate it into your app?

https://forum.sailfishos.org/t/34668

It would mainly be about enabling/disabling the socket service.

2 Likes

Sure, why not, send the PR! Or I can do it myself if you’re not used to Go.

2 Likes

Here’s the D-Bus method: harbour-inari-blue-notifier/src/daemoncontroller.cpp at master · RikudouSage/harbour-inari-blue-notifier · GitHub

And here the JSON pattern which needs to be sent over: harbour-inari-blue-notifier/qml/pages/EditPatternPage.qml at master · RikudouSage/harbour-inari-blue-notifier · GitHub

Edit: The stop method is in the same cpp file, you will need it if you’re gonna do morse, it can only do a simple pattern.

If you need some signal for playing finished, let me know.

5 Likes

Thanks a lot for the help!

I figured put so much, my problem now is that dbus "PlayPattern" expects a STRUCT ("(sxxxxxyy)"). As I’m trying to send that from Nemo.DBus, I can t call it, because that can’t contruct the correct message - it cannot marshal a STRUCT.

I can successfully construct a plain "sxxxxxyy", or of course the JSON itself as an a{sv} message from QML.

Any possibility to have a PlayPattern version supporting one of those two signatures?

Sure, I’ll add “PlayPatternAllChannels” method when I’m home.

4 Likes

@nephros Well, I instead added PlayPatternJSON which accepts a single parameter, a string with the JSON. Feels simpler than supporting two structs and more future proof.

4 Likes

Woohoo, it works! Now I have to redo some timing logic in LaDitDah, but it looks great! :slight_smile:

https://build.sailfishos.org/package/show/sailfishos:chum:testing/laditdah

^^^ if you want to try :slight_smile:

7 Likes

How do I download from there? Really confusing UI.

switch Chum to testing repo
or https://repo.sailfishos.org/obs/sailfishos:/chum:/testing/5.2_aarch64/noarch/harbour-laditdah-0.9.7+inari.blue.notifier.20261012153813.20.ga85a67f-1.9.1.bso.noarch.rpm

1 Like

I did, the app does not seem to use toh, though.

right, status build: broken :|)
updated link in my previous post

Sorry, fixes underway and rebuilds happening.

Should be stable to use soon :slight_smile:

https://repo.sailfishos.org/obs/sailfishos:/chum:/testing/5.0_aarch64/noarch/harbour-laditdah-0.9.7+inari.blue.notifier.20261012153813.20.ga85a67f-1.9.1.bso.noarch.rpm

Or whatever’s latest in Index of /obs/sailfishos:/chum:/testing/5.2_aarch64/noarch

FWIW, I try to soft-depend (Recommends) on the inari-notifications-daemon. So the app shall work with and without it installed, and depending how it is installed, may pull in the daemon package or not.

Why are there this app and toh-notify? Where toh-notify comes from?

Looks like a different developer. At least to me.

No idea, not mine. They seem to do a similar thing as I do, but I’d say my app is better on the tech side - nothing runs as root so nothing can use any bugs in my code to gain a system wide access.

4 Likes

Added support for notifications! You can also toggle which events you want to trigger the TOH on (calls, favourite contacts calls, notifications). Notifications are disabled by default cause it might get too noisy.

Next I’ll tackle custom patterns per notification type (email, sms, general notification).

13 Likes

A time interval to disabled it at night would be cool

2 Likes

It was on my mind as well, will do :slight_smile:

5 Likes