hassio-addons / addon-node-red

Node-RED - Home Assistant Community Add-ons
https://addons.community
MIT License
536 stars 125 forks source link

node red addon is missing in Home Assistant Community Add-ons #897

Closed tiger-seo closed 3 years ago

tiger-seo commented 3 years ago

Problem/Motivation

node red addon is missing, so cant be installed

Expected behavior

node red addon is available in Home Assistant Community Add-ons

Actual behavior

node red addon is missing in Home Assistant Community Add-ons

Steps to reproduce

open Add-on Store try to find Node Red in Home Assistant Community Add-ons

Proposed changes

(If you have a proposed change, workaround or fix, describe the rationale behind it)

frenck commented 3 years ago

Please list the installed repostories in the add-on store.

tiger-seo commented 3 years ago

i think it may be related to the fact that my local supervisor version is 2021.01.7 ( not Supervisor 2021.02.6 )

tiger-seo commented 3 years ago

or maybe it is also related to following actions: i did update of node red addon (and others), i did update of supervisor, then i've got a problem with supervisor 2021.02.6 , so i did downgrade of supervisor from 2021.02.6 to 2021.01.7, afterwards all addons are disappeared , so i have to reinstall them from addon store - everything except node-red, because it was missing

tiger-seo commented 3 years ago
repositories:
- maintainer: you
  name: Local add-ons
  slug: local
  source: local
  url: https://home-assistant.io/hassio
- maintainer: ESPHome <contact@esphome.io>
  name: ESPHome Home Assistant Add-Ons
  slug: 15ef4d2f
  source: https://github.com/esphome/hassio
  url: https://github.com/esphome/hassio
- maintainer: Daniel Welch <dwelch2102@gmail.com>
  name: 'Home Assistant Add-on: Zigbee2mqtt'
  slug: 7ad98f9c
  source: https://github.com/danielwelch/hassio-zigbee2mqtt
  url: https://www.zigbee2mqtt.io
- maintainer: Stephen Beechen <stephen@beechens.com>
  name: Home Assistant Google Drive Backup Repository
  slug: cebe7a76
  source: https://github.com/sabeechen/hassio-google-drive-backup
  url: https://github.com/sabeechen/hassio-google-drive-backup
- maintainer: Home Assistant
  name: Official add-ons
  slug: core
  source: core
  url: https://home-assistant.io/addons
- maintainer: Franck Nijhof <frenck@addons.community>
  name: Home Assistant Community Add-ons
  slug: a0d7b954
  source: https://github.com/hassio-addons/repository
  url: https://addons.community
frenck commented 3 years ago

You should not run an outdated Supervisor. It is not meant to be behind and manual interfered with.

Your system is not compatible.

RIP21 commented 3 years ago

I have had the same issue. Unfortunately, it's no way we can update to the latest Supervisor due to recent issues with Synology community installation and the latest Supervisor :(

More info is out there. https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559/1454?u=rip21

frenck commented 3 years ago

Synology isn't a supported system to run this ecosystem on. The supervisor has been warning you for ages. You choose to just ignore that. Not sure how that becomes my problem.

RIP21 commented 3 years ago

I'm just stating why it's not an option. And I wasn't rude at all. Although it's really sad that NASes are not the supported systems. They're perfect for such use case. Dunno, but some little clues with how to work around it (like installing addon manually at our own risk), knowing that you folks know this system in an out, would be nice. No one asks you to include those workarounds in official distributions. Around 1-2k people are using (at least 1500 comments in respective thread on community forum) it thorough Synology for sure and it's a bit sad you completely ignore them no even giving some clues.

Anyway, thanks a lot for all the work you're doing, just a bit frustrated :(

frenck commented 3 years ago

They're perfect for such use case.

They are not, really. Not in the way you guys are using them.

but some little clues with how to work around it

There isn't a workaround. Don't use that system to run this ecosystem. Your problem will get worse over time. It simply isn't fit for the job. If you want to use a NAS, use the Home Assistant Container, or, if your NAS supports it, use a VM. Those are supported use cases by the Home Assistant project as well.

Around 1-2k people are using (at least 1500 comments in respective thread on community forum) it thorough Synology for sure and it's a bit sad you completely ignore them no even giving some clues.

We have been putting a lot of effort into leaving clues and warnings, for a long time already. Don't say we ignore it (as we didn't). We don't put all these warnings and detections in place to be assholes, we do that to warn YOU about possible issues. YOU ignore them.

RIP21 commented 3 years ago

@frenck makes sense. So, you say that running Home Assistant OS in VM is a supported option. So, it means that if I can run, let say, some sort of VM on Windows would be with tool like VMware or on MacOS Parallels and similar, then it should be a supported env then. Can you give me a link which image is recommended in that case that I'll have to roll in such VM tool? (I have a spare laptop that definitely has Virtualization support, so will be a perfect use case of it)

Thanks, and sorry :) I'm new to ecosystem, so sorry if I sounded disrespectful :)

frenck commented 3 years ago

https://github.com/home-assistant/architecture/tree/master/adr

☝️ This is where the Home Assistant project stores architectural decision records for bigger decisions. ADR 0012...0016 all are related to supported installation methods, their conditions, requirements, target audience and goals.