Replies: 1 comment
-
This is a general HA issue. The integration has no influence over the UI for services. Since there is an available_tones method in the siren API, I would expect the HA UI to use it, but it must be missing for the service call case. The default tone is only used if you call siren.turn_on with no arguments, and the siren does not have a "switch" dp, so the only way of turning it on is to select a tone. Neo coolcam siren does have a separate "switch" dp, so I expect it should be able to use that to play the currently selected tone without changing anything. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This probably applies to most Siren devices, but the device I have is a Neo_Coolcam_Siren, see the corresponding yaml file in the device list.
I can control the siren via a service action request, eg.
However, the tone to be used must be entered manually, so unless to know exactly the tone title, it will not work.
Is there a way the a pull-down menu can be made visible to select from the available list?
Also, if a tone is set as default: true, I would have thought that the service action would also select that too, obviously not.
Any thoughts?
Is it as simple as changing the entity for this dp, from siren to select and add class: "enum"?
This is a totally different product, but shows that a pull-down menu is actually possible.
Also according HA, a siren tone entity should be controlled by either the key or the value, currently only the string seems to only work, not the integer.

Beta Was this translation helpful? Give feedback.
All reactions