-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OnOff Schedule with midnight times causes 'Unknown Error' #284
Comments
John, i have tried to recreate the issue you describe and do see the first part if i set the schedule from 00:00 to on and then save it turns it to off. Will look into this. Cant seem to recreate the unknown error. Can you describe a little more step by step or post a video showing this. Can you also confirm (from my testing) if the time is anything but 00:00 then it doesn't have an issue. Thanks |
Dont worry, i miss read your explanaition. I have recreated both issues. Will look into this. As said above, seems if you dont use 00.00 hours it works ok. |
Thanks Mark - Totally understand this sort of schedule can cause an issue (especially at 00:00). I will re-adjust accordingly. |
John, v3.1.3 just released should solve your issue. |
Fantastic. Thank you so much! |
@msp1974 Just updated and can confirm the issue is fixed. Really appreciate this Mark. |
Hi Guys.
I was attempting to create an 'on-off' schedule to force a Wiser smartplug to be permanently on (i.e a single 'On' event at midnight or any other time). I was able to delete the standard on-off events until I was left with the single 'on' but on saving, the on changed to off! I then went back to the wiser app - it was showing the event as being 'on'.
I copied the schedule within the app to all days, then refreshed the HA dashboard, clicked on the schedule entry and it just displays an 'Unknown error'
It's a minor inconvenience but would be good if I could manage all schedules within HA.
Really appreciate your work on this integration - it really is first class :-)
Thanks, John
The text was updated successfully, but these errors were encountered: