-
Notifications
You must be signed in to change notification settings - Fork 64
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
Unable to make a call to node-red on the same host #53
Comments
Dasshio performs an HTTP Post request to the url indicated with the body and hraders provided. I see in your curl command traces a GET request. Could this be the issue? Thanks for commenting ans sorry for my delayed response. |
@JamesValero is this still an issue or can it be closed? |
Could you point me to how to properly setup the post call? Would like to
use it for testing purposes.
Thanks
…On Wed, Oct 31, 2018 at 8:41 AM Daniel ***@***.***> wrote:
@JamesValero <https://github.com/JamesValero> is this still an issue or
can it be closed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#53 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AJ0H_JybJcIfItdWD3VlwVoH-rEeSzZyks5uqcSSgaJpZM4V5DTY>
.
|
See the example at https://developers.home-assistant.io/docs/en/external_api_rest.html |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have Hassio with the dashio and node-red addons. Dashio is working fine with a physical Amazon Dash when sending a RESTful call to the hassio api URL.
Triggering the workflow via curl on the pi and/or hassio (using the community ssh addon) also works fine.
The trouble comes when trying to do the same to a node-red URL. Now when trying to trigger the node-red URL via the Dash button, dashio logs shows it's getting a 404. Again, a basic curl to the same node-red URL works fine.
Below is the dashio setup (node-red is on port 1880)
Seems like the dashio docker is getting to the endpoint but for some reason it's getting back a 404
Showing how it works fine by doing a simple curl from the hass.io terminal to the same URL
The text was updated successfully, but these errors were encountered: