-
Notifications
You must be signed in to change notification settings - Fork 187
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
Sentence node not outputting an event #327
Comments
I just started messing around with Sentence Nodes and getting the same behaviour as above |
Home Assistant 2024.12.0 introduced breaking changes with this pull request, which affects the custom component. The component needs to be updated to accommodate these changes. Transferring this issue to the Node-RED companion repository, as it is the appropriate location for addressing it. |
Is there any progress? |
I'm joining in on this question. Living has become less comfortable. |
Describe the bug
I have created a sentence node and when saying the sentence that it is configured for, the default response is always returned but the node never outputs an event. This comes along with an error in the Home Assistant logs. I have replicated this with the "Basic Usage" example from https://zachowj.github.io/node-red-contrib-home-assistant-websocket/node/sentence.html#basic-usage as well. Here is the Home Assistant error when clicking the "hello world" inject node:
And here is the error log when triggering my custom sentence ("Let's go to sleep"):
To Reproduce
Expected behavior
The sentence node should successfully output an event for other nodes to receive when the sentence is stated
Screenshots
No response
Example Flow
Environment Information
Version: 0.74.2
Home Assistant version: 2024.12.0
Companion version: 4.1.1
Node-RED version: 4.0.3
Docker: yes
Add-on: 18.1.1
Node.js version: v18.20.4 x64 linux
OS: Linux 6.6.63-haos x64
Additional context
I also tried updating the pallet to the latest version (0.74.2 at the time of writing this issue) and was still able to replicate this issue
The text was updated successfully, but these errors were encountered: