LaMetric: No sound when trying to do a custom sound
The problem
The problem The API docs from LaMetric indicate that their API supports custom MP3 URLs for notification sounds. When attempting this via notify.<device_name>, an unknown error occurs.
Diagnostics information config_entry-lametric-72e5f4e7d6428d441abd74912cbfaf07.json.txt
Additional information No response
What version of Home Assistant Core has the issue?
latest
What was the last working version of Home Assistant Core?
none
What type of installation are you running?
Home Assistant OS
Integration causing the issue
LaMetric
Link to integration documentation on our website
https://www.home-assistant.io/integrations/lametric
Diagnostics information
No response
Example YAML snippet
action:
service: notify.my_lametric
data:
message: "Er staat iemand voor de deur!"
data:
icon_type: "none"
sound:
category: "custom"
id: "https://home.deds.nl/~jacobshomepage/ding-dong-bell-doorbell.mp3"
repeat: 1
cycles: 1
priority: "warning"
icon: "i555" # Voeg het gewenste icoon toe
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @robbiet480, @frenck, @bachya, mind taking a look at this issue as it has been labeled with an integration (lametric) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of lametric can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign lametricRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
lametric documentation lametric source (message by IssueLinks)
any update on this ?
What I get is a non-allowed ID when entering an URL. So this is not a bug as such, but a feature that has to be implemented for the "new" Lametric API.
What I get is a non-allowed ID when entering an URL. So this is not a bug as such, but a feature that has to be implemented for the "new" Lametric API.
Oh wow! Is that something big? Having my LaMatric function as a doorbell is a gamechanger for me personally and replaces the need of dedicated speaker for that
What I get is a non-allowed ID when entering an URL. So this is not a bug as such, but a feature that has to be implemented for the "new" Lametric API.
Oh wow! Is that something big? Having my LaMatric function as a doorbell is a gamechanger for me personally and replaces the need of dedicated speaker for that
Not sure, I haven't looked at the code at all. But already now you can play different types of pre-defined alarm sounds on the Lametric. Just not pointing to a URL.
What I get is a non-allowed ID when entering an URL. So this is not a bug as such, but a feature that has to be implemented for the "new" Lametric API.
Oh wow! Is that something big? Having my LaMatric function as a doorbell is a gamechanger for me personally and replaces the need of dedicated speaker for that
Not sure, I haven't looked at the code at all. But already now you can play different types of pre-defined alarm sounds on the Lametric. Just not pointing to a URL.
yeah i know that, but my wife is never going to accept a different doorbell tone haha
Hi there @joeblack2k, thanks for raising an issue. Unfortunately, this is not a bug but a feature request.
The supported values by the integration are documented here: https://www.home-assistant.io/integrations/lametric#sound
Custom sounds are supported by the newer APIs, but not implemented in the integration or library the integration uses.
../Frenck