Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

missing node type after update from 1.1.3 to 1.2.x

Open
#206 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker
Domain
devops

Research direction

Start by reproducing the Watchtower upgrade from Node-RED 1.1.3 to 1.2.0 and inspect how the listed node types are installed and retained. Done means documenting the cause, a recovery path, and a way to prevent missing node types during future upgrades.

Written by the indexing model from the issue text.

Description

nodered stoppen working after watchtower upgraded nodered to 1.2.0 due to missing node types.

Example:

Flows stopped due to missing node types.

hue-bridge
light-scheduler-settings
influxdb
harmonyws-server
hb-conf
nuki-bridge
zigbee2mqtt-server
hue-group
hue-bridge-node
cron
hue-light
influxdb in
influxdb out
harmonyws-observer
nuki-bridge-control
nuki-lock-control
harmonyws-command
stoptimer
hue-magic
light-scheduler-filter
shelly-switch
harmonyws-activity
door-sensor
zigbee2mqtt-bridge
zigbee2mqtt-get
zigbee2mqtt-out

Why did it happen?
How can it get fix?
How can it be prevented in the future?

Dominant language
Shell
Stars
540
Forks
434
Avg merge
24m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from node-red/node-red-docker

All issues in node-red/node-red-docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.