Not deleting/recreating the modes, just the instance of mode manager that’s controlling the transitions, then re-doing the automation logic in a newly installed instance of the app.
@bravenel stated last month that deleting and redoing mode manager should not be necessary. I made the same recommendation (based on personal experience and previous comments that I have read) to some one and kinda got told that I was wrong to be suggesting it.
Without some more detailed info from OP, or the thread you mention, hard to say if they’re related at all, or whether any potential solutions are “wrong.”
I suspect the issue here is related to how the hub is handling sunset offsets, rather than something inherent to this instance of mode manager, hence my initial question.
Recreating mode manager triggers would probably take no more than a few minutes though, so perhaps it’s worth trying. Or perhaps I’m wrong.
Regardless, more info is needed to effectively troubleshoot.
As far as I can see, time is correct and it's accurately reporting sun set and sunrise, however Mode Manager doesn't seem to be picking that up and still using an old sunset and sunrise it's it's cache or whatever. It thinks sunset -30. Is 3pm when the sun set and sunrise settings state 5:40 (or later now) latitude and longitude is all working, my location is still the same it seems to be purely with mode manager