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

Node-RED Add-on Not Functioning Inside Home Assistant #22462

Closed
3 of 4 tasks
1192410 opened this issue Oct 21, 2024 · 2 comments
Closed
3 of 4 tasks

Node-RED Add-on Not Functioning Inside Home Assistant #22462

1192410 opened this issue Oct 21, 2024 · 2 comments

Comments

@1192410
Copy link

1192410 commented Oct 21, 2024

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

This issue has already been filed here, but it seems no one is picking it up. Essentially, the Node-RED add-on is not functioning from within Home Assistant, although it does work when accessed directly via port 1880. Given that Node-RED is likely one of the most widely used add-ons, I believe this should be addressed promptly. If this message is in the wrong place, I apologize.

Many thanks,
Andreas

Describe the behavior you expected

I want a connection to Home assistant, but there is no connection, for example inject buttons are greyed out.

Steps to reproduce the issue

See here hassio-addons/addon-node-red#1971

What version of Home Assistant Core has the issue?

2024.10.3

What was the last working version of Home Assistant Core?

2024.10.3

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

Win11

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

@silamon
Copy link
Contributor

silamon commented Oct 21, 2024

There's nothing we can do about it in this repository.

@silamon silamon closed this as not planned Won't fix, can't repro, duplicate, stale Oct 21, 2024
@Dodoooh
Copy link

Dodoooh commented Oct 21, 2024

Hi @silamon Why not in this repository? can you explain this further?

Where should this be placed, is it rather Ingress? The error only occurs with the latest update of nodered and as soon as you go back in the backup it works.

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

3 participants