Skip to content

blind-control ignores month restrictions in time rules after update #562

Description

@McWuragu

Describe the bug
The blind-control node seems to ignore configured month restrictions in time rules.

After recent updates, my blind-control node started selecting rules that should not be active for the current month. The time condition seems to be evaluated, but the month restriction appears to be ignored.

Observed behavior:

  • Current date: 2026-07-04
  • I have several blind-control rules for different seasons: winter, spring/autumn and summer.
  • At first, the summer rule matched, which was expected for July.
  • Then I removed June and July from the summer rule.
  • After deploy/restart/trigger, the same summer rule was still selected, although July was no longer configured for this rule.
  • It looks like the last rule matching by time wins, even if the configured month does not match.

Additional observation:
The node status shows unresolved labels like:

__timeOp__ __timeLocal__

Screenshots
I can provide screenshots showing:

  • the blind-control node status with __timeOp__ __timeLocal__
  • the rule configuration
  • the flow around the blind-control node

Expected behavior
A blind-control rule should not match when the current month is not included in the configured month restriction.

For example:
If the current date is 2026-07-04 and a rule is configured without July, this rule should not be selected, even if the time condition matches.

System information (please complete the following information):

  • Node Version: node-red-contrib-sun-position 3.0.1
  • Node-Red Version: v5.0.0

Additional context
Home Assistant environment:

  • Installation method: Home Assistant OS
  • Home Assistant Core: 2026.7.1
  • Home Assistant Supervisor: 2026.06.2
  • Home Assistant Operating System: 18.1
  • Home Assistant Frontend: 20260624.4

Runtime from Node-RED log:

  • Node.js version: v24.16.0
  • Linux: 6.18.37-haos x64 LE

Other related Node-RED package:

  • node-red-contrib-home-assistant-websocket: 0.80.3

Workaround:
I disabled the other seasonal rules for now to prevent the wrong rule from being selected.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions