You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to save nodes by node-red-contrib-home-assistant-websocket, I get the following problem:
Flows stopped due to missing node types.
* server
* api-call-service
To Reproduce
Steps to reproduce the behavior:
Install node-red-contrib-home-assistant-websocket
Add Call Service node and add settings
Save
Try using HTTP Request
Expected behavior
Allow me to save, or explain why it's failing.
Screenshots
Package
Not sure what's going on here.
Settings
What's strange is that the Base URL and Access Token disappears after save, regardless if using http://<host ip>:8123 or https://homeassistant.domain.tld which is proxied.
Environment (please complete the following information):
Node Red Version: 0.19.5
NR Home Assistant Plugin Version: e.g. 0.5.0
Is Node Red running in Docker: yes
Have you searched previous issues for duplicates?:
Yes
The text was updated successfully, but these errors were encountered:
Describe the bug
When trying to save nodes by
node-red-contrib-home-assistant-websocket
, I get the following problem:To Reproduce
Steps to reproduce the behavior:
Install
node-red-contrib-home-assistant-websocket
Add
Call Service
node and add settingsSave
Try using HTTP Request
Expected behavior
Allow me to save, or explain why it's failing.
Screenshots
Package
Not sure what's going on here.
Settings
What's strange is that the
Base URL
andAccess Token
disappears after save, regardless if usinghttp://<host ip>:8123
orhttps://homeassistant.domain.tld
which is proxied.Environment (please complete the following information):
Node Red Version: 0.19.5
NR Home Assistant Plugin Version: e.g. 0.5.0
Is Node Red running in Docker: yes
Have you searched previous issues for duplicates?:
Yes
The text was updated successfully, but these errors were encountered: