Errors after updating to MQTTController build 25139

[Andr]

Hi everyone

I'm about to set up notifications from MSR and would like input on what works best.
Quick and reliable delivery to Android devices is the goal.

(Tried to set up pushover last night, but probably missed something because it doesn't work. Succeed thru homeassistant, but not with MSR.)

Is pushover worth its money?
what do you use and why?

Greatly appreciate your thoughts

[toggledbits]

I use Pushover. I'm a fan. I've never missed a message. I additionally use email, as my wife is a hawk for her email accounts and give me good assurance that if Pushover ever misses, a SpouseNet notification is not far behind.

[tunnus]

@andr Telegram. No regrets

[therealdb]

Telegram here as well. I’ve deeply customized with a bot, pushing videos from my cams and accepting commands with wizards as well.

[Andr]

@therealdb said in What notification system is best?:

Telegram here as well. I’ve deeply customized with a bot, pushing videos from my cams and accepting commands with wizards as well.

Do you mean a "chatbot" that you can respond to? That sounds cool, could you give som example of what you use it for?

Right now I struggle with Pushover. Can't find out why it doesn't work.
From reactor.log:
default:null Module NotifyPushover v21195
Engine:ERR Engine#1 reaction re-kud4t99t step 0 notification (Pushover) failed: Error: Pushover user and token could not be determined

From notification.yaml

  # Pushover
  Pushover:
    profiles:
      default:
        # description - A friendly description of this profile (for menus)
        description: Andre
        #
        # user - (required) user key from Pushover. Refer to the Reactor docs for
        #        the Notify action for info on how to get your user key.
        #user: u4cXXXXXXXXXXXXXXXXXXXXXtkv1d
        #
        # token - (required) token from Pushover site. Again, see the Reactor docs
        #         for info. This is the default token used for this profile if a
        #         token is not specified in the notification parameters.
        #token: amwXXXXXXXXXXXXXXXXXXXXXn7if
        #
        # default_device - (optional) name of the default device to receive not-
        #                  ifications. You can leave this blank, and the default
        #                  device will be whatever the Pushover API determines. If
        #                  set here, it's the default for this profile, when no
        #                  device is specified in the Notify action itself.
        #default_device: ""
        #
        # default_title - (optional) default notification title to use for this
        #                 profile. It will be used when no title is specified in
        #                 the Notify action. If no title is specified at all, the
        #                 system default title "Reactor" will be used.
        #default_title: "Reactor Notification"

The Reaction

I have tried to put user id & token between citation marks " "
Same user id & token work from pushover site and when sending notification from Homeassistant.

[Crille]

@andr Remove the “#” in front of user id and token

[Andr]

@crille
THANKS!!

Now Pushover works.
Time to take a look at that Telegrambot

[Crille]

I use pushover for all my notifications and have been doing so since 2013. A really good and stable service. Started using it before it became a subscription service so was upgraded to “free for life” when they introduced that.
Telegram is looking very interesting though

Edit: I see it’s a one-time fee per platform now, not a subscription.

[Andr]

@crille
Yes, 5usd per platform. Not much to discuss if it is a good service.
Will use the 30-day trial period for now to test it.

But the telegram bot seems intresting, I got it up and running but i dont think i can manage to make good use of it.
Me: Hey bot, heat up my car so its ready 07:45
Bot: After consulting with MSR i found the outside temperature is -5 degrees, so I start the heater at 07:00.

Thanks everyone for your thoughts, very helpful!

[wmarcolin]

Telegram

[tunnus]

@andr interactive bot might be a bit too much for starters, but Telegram is excellent in providing different status messages set up in MSR

[therealdb]

The chat bot is used to control lights and run scenes, if necessary. I’m still on my Vera but it’s decoupled, so this is the only way to interact when outside the house.

I’ve also integrated my ECOVAC deebots, and opensprinkler. But we’re mainly using it to open doors and garage doors, since everything else is automated and we rarely mess with this stuff. But it was fun. It’s not parsing natural language, but it’s doable (part of my job is dedicated to this stuff, so this was a sort of research project for me back in the days).

[gwp1]

Dipped my toe with Prowl, saw Pushover and haven't looked back. I like the ability to "personalize" the notifications both textually and audibly.

[CatmanV2]

Telegram. Zero maintenance.

C

[Pabla]

@therealdb said in What notification system is best?:

The chat bot is used to control lights and run scenes, if necessary. I’m still on my Vera but it’s decoupled, so this is the only way to interact when outside the house.

I’ve also integrated my ECOVAC deebots, and opensprinkler. But we’re mainly using it to open doors and garage doors, since everything else is automated and we rarely mess with this stuff. But it was fun. It’s not parsing natural language, but it’s doable (part of my job is dedicated to this stuff, so this was a sort of research project for me back in the days).

This chat bot sounds interesting, if I am reading this correctly in the Telegram group chat you can basically tell the bot to do certain things that are preconfigured?

[therealdb]

@pabla yep. It’s not a product, but very specific to my needs, so I’ve not released it. I’ll see if I could post some screenshot to be of inspiration to others. AFAIK home assistant has something like this built in (or, maybe, it’s open hab)