Node-Red does not seem to recognise the piper add-on as a tts sercive. Home Assistant itself does list it as a tts service. If I add a call service node and choose tts as domain piper will not be listed as a service.
Debug log
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 14.1.5
You are running the latest version of this add-on.
System: Home Assistant OS 10.1 (amd64 / qemux86-64)
Home Assistant Core: 2023.5.0
Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
up to date in 7s
24 packages are looking for funding
run `npm fund` for details
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[18:15:28] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
4 May 18:15:29 - [info]
Welcome to Node-RED
===================
4 May 18:15:29 - [info] Node-RED version: v3.0.2
4 May 18:15:29 - [info] Node.js version: v18.14.2
4 May 18:15:29 - [info] Linux 6.1.25 x64 LE
4 May 18:15:30 - [info] Loading palette nodes
4 May 18:15:32 - [info] Dashboard version 3.4.0 started at /endpoint/ui
4 May 18:15:32 - [info] Settings file : /etc/node-red/config.js
4 May 18:15:32 - [info] Context store : 'memoryOnly' [module=memory]
4 May 18:15:32 - [info] Context store : 'MACAdressenNetzwerk' [module=localfilesystem]
4 May 18:15:32 - [info] Context store : 'minBenzinpreise' [module=localfilesystem]
4 May 18:15:32 - [info] User directory : /config/node-red/
4 May 18:15:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 May 18:15:32 - [info] Flows file : /config/node-red/flows.json
4 May 18:15:32 - [info] Server now running at http://127.0.0.1:46836/
[18:15:32] INFO: Starting NGinx...
4 May 18:15:32 - [info] Starting flows
4 May 18:15:34 - [info] Started flows
4 May 18:15:34 - [info] [server:Home Assistant] Connecting to http://supervisor/core
4 May 18:15:34 - [info] [mqtt-broker:Mosqitto - Addon] Connected to broker: mqtt://X.X.X.X:1883
4 May 18:15:34 - [info] [server:Home Assistant] Connected to http://supervisor/core
4 May 18:15:45 - [info] [ping:91e5ac98c60c96e3] ping - Host 'X.X.X.X' process timeout - sending SIGINT
4 May 18:15:45 - [info] [ping:5372c1b088303915] ping - Host 'X.X.X.X' process timeout - sending SIGINT
4 May 18:15:46 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
4 May 18:15:46 - [info] [server:Home Assistant] Connecting to http://supervisor/core
4 May 18:15:51 - [info] [server:Home Assistant] Connecting to http://supervisor/core
4 May 18:15:56 - [info] [server:Home Assistant] Connecting to http://supervisor/core
I am not sure that I enabled the debug log. I was unable to find a reference how node-red has to be called in the config. I tried homeassistant.compenents.node_red: debug and homeassistant.compenents.nodered: debug, but with no difference.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Version of the custom_component
14.1.5
Configuration
Describe the bug
Node-Red does not seem to recognise the piper add-on as a tts sercive. Home Assistant itself does list it as a tts service. If I add a call service node and choose tts as domain piper will not be listed as a service.
Debug log
I am not sure that I enabled the debug log. I was unable to find a reference how node-red has to be called in the config. I tried
homeassistant.compenents.node_red: debug
andhomeassistant.compenents.nodered: debug
, but with no difference.