Help with LaMetric configuration

Configuration
1

reading the Documentation I am confused on something.

the configuration example;

# Example configuration.yaml entry
notify:
  name: NOTIFIER_NAME
  platform: lametric

then the automation refers to;

action:
    service: notify.lametric

I read that the that the name: should be appended to the the notify

So do the two code example not go together, meaning the automation refers to a service not in the configuration, or am I missing how to stitch this together.

Thank You

2

figured this out, they are NOT part of a flow.

If the name: is NOTIFIER_NAME then the service: is notify.NOTIFIER_NAME

to an expert this probably was obvious for a novice the use of lametric was confusing, and I assume would work if there was no option name: in the configuration.yaml

For clarity, the automation.yaml for the configuration.yaml shown would be

action:
    service: notify.NOTIFIER_NAME
3

Except the docs say that upper case isn’t valid. Which will be why it’s used, to make it stand out as a thing to replace.

Generally speaking, after you create a new entity or service, you should look in Developer Tools -> States or Developer Tools -> Services to see what it’s actually called. HA will automatically “slugify” names to make them HA safe, which can cause things to change more than you expect.

4

Did not know the upper case rule, as it actually works with upper case, and furthers the ‘novice’ confusion.

I will try the developer tool section, Thank You for the TIP I was stumbling through trying to find them.

Issues like: The integration states that you use the name: to have multiple notifyers, but when I put two in the last one seems to usurp the others.

Tried it with two sections each starting with notify: changing definition and one notify: with two sections each starting with a different name:

I greatly appreciate the help. GREAT learning

5

You probably want to read this page too, on the fact that you can’t use notify: twice.