Hello Marcel,
FYI, about update v2.2.2 test
Fix refresh timezone issue
This issue is fixed (Pro 19)
The error of “it is after sunrise (0)” was:
Cannot read properties of undefined (reading 'getTime')
Thanks!
Good morning, since yesterday morning my morning routines are not working anymore, the check to see if it is still before end of golden hour fails (seems reversed). Anyone else experiencing issues?
To be precise, the conditional card “Het is voor Einde Ochtend Gouden Uur” (it is before Morning End of Golden Hour?) gives the wrong (opposite) result since 2 days. Other conditional cards like “Gebeurtenis Einde Ochtend Gouden uur is na 6:30” gives the correct result.
My flows are also not triggering anymore. Also don’t see them in settings. @MarcelT
Only four events are shown in the flows.
And the latest version is 1.4.8 but when you open the changelog there are a lot more versions.
Do you also use the test version? I noticed I still use the test version, started using that a long time ago due to an earlier issue, but did not revert to the regular version.
The test version was updated on January 8, which is the time my issues started.
This is from the logging:
1 Like
Ive just reverted to 1.4.8 and that seems to solve it for now.
Test version was always working fine.
On github this issue is reported yesterday i noticed. 
Yes, I also just reverted back to 1.4.8 and it seems to function properly.
@MarcelT could this pose an issue? Lately alot of cards not triggering anymore or triggering unreliable - how to debug? - #2 by Takie
I’m on v2.2.2, same phenomenon…
I decided to just adjust all the SunEvent cards events to one of these 4 to get things going again.
You can install the newer test version by:
- tapping 'Change log", and then tapping the orange “test” button, or,
- altering the app store URL by adding
test, like this:
https://homey.app/en-nl/app/com.cyclone-software.sunevents/Sun-Events/test and hit enter; now a warning should’ve appeared.
This means you can install the test version now.
To revert:
Just remove the trailing test from the URL, and hit enter; the warning should’ve vanished, you can install the stable version now.
For both installs, don’t remove the app from Homey prior to it. The app just gets replaced.
Just to prevent any other question, the developer is aware and hopefully will find time to fix this issue.
mmh, Damm DST / UTC. I will try to fix it.
2 Likes
Thanks, yeah I am working it. I have hopefully a solution and will try this overnight. If it is working I will update it on Sunday. It had all to do with local time and UTC time 
5 Likes
It should be fixed in this release:
Please test everything carefully. I have changed quite a lot.
1 Like
I have some flows based on sunset that didn’t trigger this evening. This on 2.3.0
Edit: might be relevant to mention this is all with offsets
I cannot do anything based on this. Please create an issue on github, supply the flow, logging country where you live as much info as possible.
1 Like
Edit:
@MarcelT Jan 13th @ 2100hrs: As far as I can see, all related flows ran fine, with app v2.3.0
All events seem correct now, all available flow trigger events and tags as well.
But tomorrow night I know if my flows worked.
Pro 2019, Netherlands (UTC +1)
1 Like
@Peter_Kawa Do you think the Solar Noon and the Nadir will work?
After all, both are shown at 12:50 PM and 12:50 AM. And that doesn’t normally exist.
In the logging, the Solar Noon does show correctly.
Edit. Translate to English.
In the tags I think it’s right, Mike,
12:50 and 0:50
12:50 AM and 12:50 PM do seem like valid 12-hour clock times:
My Homey is set to English language, hence the mix of 12h AM/PM clock, and 24h clock times I guess.
1 Like
@Peter_Kawa yes, you are right.
I was to much thinking.
Hi, is it safe to install the v2.3.3 test version?
I’ve noticed that several updates have been released in a short period of time over the last few days.
It should be safe now. You can always back to production version. The reason was that the app was totally rewritten so that maintenance is easier and and a number of new features.
1 Like
Theoretically yes. But the productive version v1.4.8 is already about 1 1/2 years old. And many test versions have been released in the meantime.
The version I currently have installed is the test version v2.1.5. So There is no way for me to switch back to this version.
