Skip to content
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

Timed Zone Cleaning #4

Closed
nicedevil007 opened this issue Jul 9, 2019 · 13 comments
Closed

Timed Zone Cleaning #4

nicedevil007 opened this issue Jul 9, 2019 · 13 comments

Comments

@nicedevil007
Copy link

Hey rand256 :D Here I'm again! Thx first for support! Realy good job so far.

Today I added 2 testtimers for zoned cleaning.

image

And here is the result:

image

Is it even possible to change the time on this page as well?
The Timezonesetting doesn't help at all because it still uses GMT instead of GMT+1?

@rand256
Copy link
Owner

rand256 commented Jul 11, 2019

With 0b72a9c it should show cleaning time using timezone selected in the vacuum's settings.

@nicedevil007
Copy link
Author

I will test it. The time in CLI is correct on my S50.
But I think valetudo is using an other time. Will report back :)

@nicedevil007
Copy link
Author

nicedevil007 commented Jul 11, 2019

Ok tested. Set the robot to clean a test area at 17:35, it doesn't start.
I think it will start at 18:35 now.

image

Oh and an enhancement :D
What about an Edit button as you did for the Zones to change the timersettings or days etc, or even the name?

@rand256
Copy link
Owner

rand256 commented Jul 11, 2019

Please make sure you have correct timezone set in vacuum's firmware (that is used for normal clean timers as well). It's may be different from the timezone at onboard linux system.
It is set at "settings" -> "timers" -> "gear icon".

Editing zoned timers isn't nearly as easy as editing zones. I agree though it should be done some day.

@nicedevil007
Copy link
Author

nicedevil007 commented Jul 11, 2019

I double checked it again. The timezone is set to Europe/Berlin what's correct for me :)

image

and here CLI:

image

@nicedevil007
Copy link
Author

Ok, now it is 18:35 => S50 started Testzone cleaning...

@nicedevil007
Copy link
Author

Maybe it is a problem with summer/winter time?

@rand256
Copy link
Owner

rand256 commented Jul 12, 2019

Yes, node-cron module seems doesn't support Daylight Saving Time at all.

@nicedevil007
Copy link
Author

Ok, then we don't have a chance at all to fix that right? Isn't it possible to determine which time is set right now and substract 1 hour from that?

@rand256
Copy link
Owner

rand256 commented Jul 13, 2019

No it isn't since there's huge amount of timezones in the world and you won't be able to track them all.
So in cf15807 I've replaced cron module with the one supporting Daylight Saving Time. Probably should get better. In my country there's no DST now, though.

@nicedevil007
Copy link
Author

nicedevil007 commented Jul 13, 2019

The Winter/Summertime will be abandoned in europe in the near future :)
But isn't it easy to compare the time of the linux system with the setup timer for zoned cleaning?
The time in ubuntu should be always the right one, using my Sophos UTM as NTP server :)

oh forgot: will test the new release as always :) you can't imagine how much we (my girlfriend as well) like your version of valetudo!

@nicedevil007
Copy link
Author

Ok Rand256, my test was setup for 19:00... the robot started at exact 19:00 :)
My girlfriend is lucky now hehe.

One little improvement... a button to enable autorefresh of the map while the robot is running around the flat?

@rand256
Copy link
Owner

rand256 commented Jul 16, 2019

The thing is not everyone can setup required timezone in linux console. Setting it via the website is much easier.

Regarding refreshing the map, it should be refreshing automatically during the cleaning (and for me it surely does work fine). If it doesn't for you, please open another ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants