Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Nodered API errors w/ HASS.IO
See original GitHub issueHass.io running 0.84.6, and node-red 1.2.3 on a pi B.
Node-red appears to connect just fine with the “events:state” node, and reflects the time they last changed. It also seems to have no issue with the “current state” node. However, the “call service” nodes do not work.
In the node-red GUI, the error is
"API Error at: (date/time)"
In the node-red module log, the error is:
7 Jan 13:07:42 - [warn] [api-call-service:Turn On Light] Error calling service, home assistant api error
7 Jan 13:07:42 - [error] [api-call-service:Turn On Light] Error calling service, home assistant api error
And in the system monitor, the following error:
19-01-07 21:07:39 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API error: Received message 8:0 is not WSMsgType.TEXT
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I found the issue. On publish, the connection to hassio is made. This takes about five seconds. However, the Inject node fires before this! Setting the Inject node to wat five seconds and then fire solves my problem
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.