search

niklaswall / node-red-contrib-light-scheduler

Light Scheduler is a node-red node that provides a weekly schedule mainly focused on controlling light in home automation scenarios.
Apache License 2.0
41 stars 15 forks source link

schedule #60

Closed vlak6613 closed 4 years ago

vlak6613 commented 4 years ago

Dear niklaswall, i am trying to make a schematic in the node you made. I must honestly say that I get no further than a point and a colored box. I'm sure I'll do something wrong but just don't know what.

Knipsel

elrogalo commented 4 years ago

Hi there.

I am having the same issue with LS node.

I noticed today, that it is impossible to add new or modify existing scheules in Light Scheduler (LS) nodes in my flows. There seem to be display / edit error of the graphs inside the scheduler table.

All of my LS nodes contain a schedule for whole week, which should be displayed as bars. Instead of them I can only see the bar for Monday, and a dot in place of the Tuesdays bar.

grafik

When I click on the Monday bar it "jumps" over to the Tuesdays schedule, the dot also moves also one place. That goes all the way to the end of the schedule table.

grafik

grafik

That goes for all existing nodes. Drawing new schedule bars deos not work as well, well it seems to work, but the coloured bar is drawn in opaque color and dissapears after releasing mouse button. Clicking and drawing in place where a bar is supposedly present (although not visible) is causing the cursor to change to crossed circle (couldn't register than on screen capture).

Despite the display and editing problems all scheduler nodes that I have in flows are still working properly and react to override commands. I am using Home Assistant 0.113.3 on HassOS 4.11 with Supervisor version 229 on Raspberry Pi 4B.

Hoping to find a solution for this problem. Cheers. Marcin

elrogalo commented 4 years ago

So, I will answer my own post, maybe it will help someone with same issue - updating the node to version 0.0.16 (from 0.0.15) solved the problem. I shoud have checked for the updates in the first place. This issue can be closed, I guess.

Cheers Marcin

niklaswall commented 4 years ago

Sorry for not answering this in time, but you are right. This was an issue with newer node-red versions and version 0.0.15 of the scheduler.

//Niklas