Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

calling assist satellite .announce action fails to handle apostrophe #2012

Closed
MikeGuest opened this issue Dec 28, 2024 · 1 comment
Closed

Comments

@MikeGuest
Copy link

Problem/Motivation

Want to call the service which sends TTS to the new HA voice satellite

Expected behavior

when you send a string containing an apostrophe, it should be spoken correctly

Actual behavior

I can't - becomes - "i can and hash 37 t"

Steps to reproduce

(How can someone else make/see it happen)

[{"id":"8b796bf90e1d17cf","type":"api-call-service","z":"46775644.dc7c28","name":"Send to Lounge Assist","server":"2080cbf9.e73504","version":7,"debugenabled":false,"action":"assist_satellite.announce","floorId":[],"areaId":[],"deviceId":[],"entityId":["assist_satellite.va_bedroom_assist_satellite"],"labelId":[],"data":"{"message":"{{payload}}"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","blockInputOverrides":true,"domain":"assist_satellite","service":"announce","x":691.6666259765625,"y":305.6666564941406,"wires":[["191fc7945fa4f314"]]},{"id":"8626e9cf55c0ed60","type":"inject","z":"46775644.dc7c28","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"This test isn't working","payloadType":"str","x":460,"y":300,"wires":[["8b796bf90e1d17cf"]]},{"id":"191fc7945fa4f314","type":"debug","z":"46775644.dc7c28","name":"debug 183","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":930,"y":280,"wires":[]},{"id":"2080cbf9.e73504","type":"server","name":"Home Assistant","version":5,"addon":true,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":false,"cacheJson":true,"heartbeat":false,"heartbeatInterval":"30","areaSelector":"friendlyName","deviceSelector":"friendlyName","entitySelector":"friendlyName","statusSeparator":"at: ","statusYear":"hidden","statusMonth":"short","statusDay":"numeric","statusHourCycle":"h23","statusTimeFormat":"h:m","enableGlobalContextStore":true}]

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Sorry, don't know enough to suggest a fix. I do know that calling the same service from the HA developer tools works as expected.

@frenck
Copy link
Member

frenck commented Jan 4, 2025

Hi there @MikeGuest 👋

I wish I could help, unfortunately, this is not an issue with the add-on, but an issue with the Node used. Please report it with the repository providing the Home Assistant WebSocket node instead.

../Frenck

@frenck frenck closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants