ASC_Time_Up_WE_Holiday not recognized after update #4

Closed
opened 2020-03-31 19:50:19 +00:00 by marko · 0 comments
Owner

Before the Update:
ASC_Time_Up_WE_Holiday was set to 9:00 and it was correctly shown in the readings on weekends or holidays.

After the recent update (around three days ago) the shutters drove up at 8:00 on saturday. The readings show now 8:00 for the next astro event, and I cannot change this time anymore. No matter what time for ASC_Time_Up_WE_Holiday I set, always 8:00 is used as next astro event time

Before the Update: ASC_Time_Up_WE_Holiday was set to 9:00 and it was correctly shown in the readings on weekends or holidays. After the recent update (around three days ago) the shutters drove up at 8:00 on saturday. The readings show now 8:00 for the next astro event, and I cannot change this time anymore. No matter what time for ASC_Time_Up_WE_Holiday I set, always 8:00 is used as next astro event time
marko added the
bug
label 2020-03-31 19:54:54 +00:00
marko closed this issue 2020-05-01 14:03:14 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FHEM/mod-AutoShuttersControl#4
No description provided.