Remote Alerts, somewhat unexpectedly

[naive drift]

I was away from home this past week, and somewhat unexpectedly got some alerts.

At home, I have a 'water leak' sensor, that is in a wet part of my basement and has been working pretty well.

Without having my Nabu Casa Account active(was active for a trial period previously), I was a bit puzzled to see some 'alerts' of a water leak detected while I was away from home.. wondering how this may have worked?

I thought I would come home to my sensor in water, and it was.. any possible explanation? would it maybe have something to do with webhooks (i dont fully understand them yet)?

[marble shore]

Those go through services provided by whoever makes your phone os

[deft stump]

seems like u have two separate things u are trying to figure out here..?

• how did I get an alert when I wasnt on my local lan and my nabu casa account was epxired
• why did my sensor trigger when it seems like it shouldn't

is that right?

[naive drift]

just the top one, i got an alert when I wasnt on my local lan...

I believe the sensor did trigger when I was away, was water detected upon my arrival home..

[deft stump]

how is your automation set up to send an alert?

[naive drift]

seems pretty standard, if this is enough info

one other thing of note, was i didnt get an individual 'first alert', i may have opened the app and got a queue of many alerts at once...

[deft stump]

hit the triple dots in the top right corner and choose the "edit inyaml" then paste that yaml in here...

also when pasting yamnl use the triple tick and the letters yaml to cause it to format correctly 🙂

like this:

alias: Switch Toggle Garage Interior Lights
description: toggle switch relay to turn on garage lights
triggers:
  - entity_id:
      - binary_sensor.us_ss13_main_button
    from: "off"
    to: "on"
    trigger: state

[naive drift]

alias: Leak alert

description: ""
triggers:
  - type: moist
    device_id: 24fca7bdd4028758d6ffac40de75dc88
    entity_id: 1daac2095886788c6de7b1870a3688db
    domain: binary_sensor
    trigger: device
conditions: []
actions:
  - action: notify.notify
    metadata: {}
    data:
      message: Leak detected
      title: Leak detected
mode: single

[deft stump]

the tick is the one on the tilde key.. the "back tick"

u have to put the ending three ticks to end the phrase

there we go! 👍🙂

Hmm.. that doesn't look like the entire automation.. for example, I have an automation to ping my cell phone if the garage door is open. it looks like this:

alias: Watchdog Garage Door left open
description: ""
triggers:
  - trigger: state
    entity_id:
      - cover.ratgdo_garage
    to: open
    for:
      hours: 0
      minutes: 15
      seconds: 0
conditions:
  - condition: state
    entity_id: binary_sensor.zone_10
    state: "off"
    for:
      hours: 0
      minutes: 0
      seconds: 0
    enabled: false
  - condition: state
    entity_id: binary_sensor.none_motion_2
    state: "off"
    for:
      hours: 0
      minutes: 0
      seconds: 0
    enabled: false
actions:
  - action: chime_tts.say
    target:
      entity_id: media_player.esp_announce_boxes
    data:
      chime_path: toast
      offset: -500
      message: The garage door has been open for 15 minutes.
      tts_platform: cloud
      volume_level: 1
      cache: true
      join_players: false
      unjoin_players: false
      announce: true
      fade_audio: true
  - action: notify.mobile_app_verns_s23u_sm_s918u
    data:
      title: Othello Alert
      message: Garage door has been open for 30 minutes.
mode: single

there is an - action: notify.<my cell phne>

is that your entire automation? 🤔

I guess it could just be notify.notify but I've not seen that before 🤔

(disclaimer- I am just learing stuff myself so I'm not an expert like jessie or ssieb is)

[naive drift]

i think so! no worries, thanks for thinking about it with me

[deft stump]

there maybe some one that can focus on the issue better than me is what I'm saying ¯_(ツ)_/¯

lol.. I can be a rubber duck- no prob lol

did u look in the logbook for the event ..?

[naive drift]

not yet--

[deft stump]

oh- one other thing- I was told that it is best practice to not use device ID's but instead to use entity id. The reason is a device Id is specific to a specific device, not the role it is playing. So if you use a devicve id for a lightbulb,then that bulb dies and you replace it, even if you name the new one the same name, the automation will fail because the old device ID is still there... does that make sense?

essntially, this is a "don't"

triggers:
  - type: moist
    device_id: 24fca7bdd4028758d6ffac40de75dc88
    entity_id: 1daac2095886788c6de7b1870a3688db

and this is a "do"

triggers:
  - trigger: state
    entity_id:
      - cover.ratgdo_garage

it also makes troubleshooting and reading the code easier as the device or entity id is cryptic

[naive drift]

just checked the logbook and see some expected entries --

i also just turned my phones wifi off, and hit run action to 'Send Notification' -- and it seemed to go through to my phone surprisingly --

[deft stump]

are you sure your nabu casa isn't SendInputing stuff anyways..? I'm not sure what they do when the trial is over- they may have a grace period or something?

it would seem that nabu casa is still engaged for you.. unless u have gone to the trouble of seeting up your own vpn solution

like tailscale or wireguard or something with nginx and reverse proxy and all that

[vestal marsh]

#1343633932415144098 message