No Astro Functions prior to to 18h

[Grothesk242]

When sunset is earlier than 18h, the adapter does show 18h as the earliest time.
There are no additional restrictions (e.g. Not Earlier than XY) set in the adapter.

[winnyschuster]

not sure if it should be like it is now but if you are only interested in real values you can set the Not Earlier fields to something real early, like 15::00 for sunset

[Grothesk242]

This is the workaround that I use for the moment. But it's still a bug from my view, at least it's an unexpected behaviour.

[winnyschuster]

its not a bug, these values are set intentionally in case fields are empty(== undefined). However, i fully agree that its an unexpected behaviour. At least fields should be filled with these default so the user knows they should'nt be left empty

[Grothesk242]

I would expect that in case of an empty field the real astro times would be considered.

[klein0r]

There are no additional restrictions (e.g. Not Earlier than XY) set in the adapter.

Please share your instance configuration - default is 18:00

[klein0r]

ioBroker.javascript/io-package.json

Line 297 in 3130e45

"sunsetLimitStart": "18:00",

Okay, this is the problem:

ioBroker.javascript/admin/index_m.html

Lines 238 to 240 in 3130e45

	if (settings.sunsetLimitStart === undefined) {
	settings.sunsetLimitStart = '18:00';
	}

[Grothesk242]

I'd recommend to set these defaults to times that are during bright daylight to avoid this unexpected behaviour. Or make these default settings visible.