Having an issue with smoke alarm announcements

Third party integrations AppDaemon
21

Yeah and when I put it that way I get the None

2018-11-01 17:17:57.304728 INFO smoke_alarms: I got an unknown state
2018-11-01 17:18:02.330111 INFO smoke_alarms: None is in state Idle
2018-11-01 17:18:02.332590 INFO smoke_alarms: The None has gone back to Idle
2018-11-01 17:18:24.826052 INFO smoke_alarms: None is in state Idle
2018-11-01 17:18:24.827132 INFO smoke_alarms: The None has gone back to Idle

BTW the unknown state is intentional

22

i guess there is no attribute friendly_name for the template sensors.
or at least not the way you did set it.
it might be that you need to set that in the customise part from HA

23

Yeah that seems to be whats going on, odd thing is in the customization part of the UI there isn’t a friendly_name attribute in there. So there is def something weird going on here.

24

in the customize part from HA there is friendly_name just like:

homeassistant:
  customize:
    sensor.your_sensorname:
      friendly_name: anything you like
25

Oh I thought you were referring to this

image
image696×776 30.9 KB

Let me go give it a whirl in the customize.yaml :slight_smile:

EDIT: Its weird, I had to restart HA and during the startup it picked up the Friendly_Name

2018-11-01 17:39:24.430067 INFO smoke_alarms: Kitchen Smoke Alarm is in state Idle
2018-11-01 17:39:24.965908 INFO smoke_alarms: Upstairs Smoke Alarm is in state Idle
2018-11-01 17:40:11.791472 INFO smoke_alarms: sensor.upstairs_smoke is in state Junk

Then as you can see it went back to using the entity name. So not sure if I found a bug or what.

26

did you delete the friendly_name lines in your template sensor configuration?

because that can cause trouble and delete the attribute.

but you could also add friendlynames in your apps.yaml :wink:

27

I will give that a whirl and let you know what happens. Thanks for the tip :slight_smile:

28

if all fails then just use your apps.yaml to set friendly names :wink: