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

Cannot save flow because of server and api-call-service #63

Closed
jeliasson opened this issue Dec 27, 2018 · 2 comments
Closed

Cannot save flow because of server and api-call-service #63

jeliasson opened this issue Dec 27, 2018 · 2 comments

Comments

@jeliasson
Copy link

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:

  1. Install node-red-contrib-home-assistant-websocket

  2. Add Call Service node and add settings

  3. Save

  4. Try using HTTP Request

Expected behavior
Allow me to save, or explain why it's failing.

Screenshots

Trying to save

Package

Not sure what's going on here.

Image

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.

Settings

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

@jeliasson
Copy link
Author

I seem to have the same problem in node-red-contrib-home-assistant. Not sure what that tells.

@jeliasson
Copy link
Author

The problem was solved by changing the docker image from nodered/node-red-docker to nodered/node-red-docker:v8.

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

1 participant