Incorrect event message "Alarm has been tripped by undefined"

akasma74 / Hass-Custom-Alarm

It is a fork of "Yet another take on a home assistant custom alarm" that will exist until its author is back to our Earth

79 stars 29 forks source link

Incorrect event message "Alarm has been tripped by undefined" #41

Closed golfvert closed 4 years ago

golfvert commented 5 years ago

When I am using an API call to change the state of a sensor and if the new state of this sensor triggers the alarm, the event shown on the log page is: Alarm has been tripped by undefined So the entity_id of the sensor responsible is not listed. Thanks!

akasma74 commented 5 years ago

I need more details to be able to reproduce the issue, i.e what API call you use, what change do you do etc - as much as possible.

golfvert commented 5 years ago

The API call: http://192.168.x.y:8123/api/states/sensor.eye_presence

and I POST:

{"state": on}

With the sensor being defined as:

sensor:

platform: template sensors: eye_presence: friendly_name: "Eye Presence" value_template: "{{ value }}"

I am moving from my old home automation system to HA. I am using this to transfer sensors from the old system to the new one.

Thanks,

PS: github is screwing the yaml... But in my config it is correct

akasma74 commented 5 years ago

And HOW do you POST?

golfvert commented 5 years ago

Either using "postman" in chrome or http node in nodered. Both give the same result.

akasma74 commented 5 years ago

Well, I can't test it then because I have no NodeRed and "postman" in chrome is deprecated.. any ideas?

akasma74 commented 4 years ago

I'm closing this issue now because there was no response. Feel free to reopen it or create a new one if you need.