
0
Fixed
Sun Mode not changed
Jérôme Carannante Carannante 9 years ago
in bOS Server
•
updated by Ricardo Pinto | visiontech pt 3 weeks ago •
17
Since this morning the mode is fix. The value at this time is Night.
How can I do a refresh of values?
Customer support service by UserEcho
Did you change any settings in Windows? Try to reload server.
Regards
No I didn't change any settings. I already reload server.
it did not change anything
Ok, check the location settings and try to change them.
When i change the location the hours change but not the mode.
Can you please send me bOS backup on e-mail support@comfortclick.com
With the version 4.0.8 the problem is resolved. just after the update this morning the mode has changed.
Regards
hitting this same issue since a week or so without updates in the jigsaw OS version
Hello,
Try to do a Reload, and check again.
I've been using the Sun Mode every single day to close my shutters at sunset during the winter, and it never failed so far. Once in a while, if I make lots of changes on my Jigsaw, I usually do a Reload, as it helps refreshing the system. Don't know if it was the case.
Anyway, please do a Reload under the Configurator, and test it out again, and keep us posted if not.
Best regards
Hi Ricardo, I did a reinstall of the same OS version, as well as reboot and hard reboot (cutting power and restoring).
As 'Reload' you mean to restore the same configuration it has currently working?
Thanks,
Pablo
Hello,
I mean, under the Configurator, on the top right, you have the menu to logout, etc, and you an option there called Reload.
Most of the times I had some trouble, usually a Reload helped. But it might not be the case, test it out first.
Best regards
Hi,
I did the whole process and no change, still azimuth and altitude change, but nott he values for dawn, day, dusk and night
I've found the issue in the way that 'Sun' module calculates the 'name' of the day 'phase'.
I've an offset of 300 minutes to night, so that I can keep lights turned on until bed time... that offset makes 'night' to start at 00:04 in my screenshot.
apparently the comparison made is hour > dawn, hour > day, hour > dusk, hour > night... but when night is "0", hour will always be bigger, so it's always night...
Hello,
So apparently you found the culprit. I usually don't mess around with the offset, unless I need just a little adjustment.
Instead of messing around with the offset, can you leave it on standard and create a routine / timer to actually turn off the lights on bed time?
Best regards
I have it solved by setting a lower offset, so that it doesn't pass the boundary of 00:00, so I have it 'solved' on my end, but still I feel that the way it's calculated should get reviewed to avoid this kind of corner cases :-)
I honestly never had any trouble with this, and I don't think that the way it's projected is wrong.
It's not supposed to have such a big offset. And if you mess with the offset, then you know that Dawn, Day, Dusk, Night will be affected. Those values come from your location, and the offset is only there if you need a little bit of fine tunning. So if you're messing with the offset by setting 300 minutes, it's obvious that something will go wrong somewhere.
Needless to say that under the offset it's quite forward:
Dawn Offset must be lower than Day Offset
Day Offset must be higher than Dawn Offset
Dusk Offset must be lower than Night Offset
Night Offset must be higher than Disk Offset
The standard values come with -15 and 15, and it's not supposed to have such a big number, because as you already stated it will mess with something, so you have to use the offset in a way that the times don't overlap. Also when you change the offset, you can see on the time that they are changed according to the offset you changed.
Other than this, I can only think of an extra information showing on the offset menu, refereeing to be careful with the overlaps, etc.
But I'm glad that you found the problem and it was easy fix :) ComfortClick gives us the tools, and we have to adapt them to our needs :)
Best regards