Test-Version 2.4.7 working fine
Version 2.4.7 not
When I search for the Sun Events app in the Homey App Store, v1.4.8 is displayed as the official/regular version:
And in the changelog history, only version 2.4.7 is listed as a test version:
So where did you get the âofficial/regularâ version 2.4.7?
Yes, that a stupid homey thing. The release notes if the test version will be shown on production??
Hm, donât understand you question⊠
Here you will find the test version: Sonnenereignisse | Homey
The offical version shows the changelog of the test version 
I know where to find the test version. I have already installed this test version. Only @owuerker seems to be using a 2.4.7 version as the âofficiallyâ released version.
So I donât have any problems in general.
But please check your mailbox, Marcel. I sent you a message about the test version 2.4.7 regarding the German translation.
But thatâs also the case with other apps. I think that was changed some time ago. And if you click on the orange âtestâ in the changelog, it even takes you to the link for the test version:
I will do check it. I am now going to a wedding and will do the rest asap.
1 Like
Hi! Itâs the guy from Github Issue here 
!
I just tested the latest test version at that solved the issues!
Thanks for the quick fix!
2 Likes
Based on the latest messages, I checked my Sun Events Homey app version. It shows 2.4.7 in Homey phone app details and no reference of experimental. Nor do I see the times in the WHEN events list. I have been using the 2.x test versions for more than a year. Iâve not done any manual installs for many months for this app. It did update 2 days ago to version 2.4.7 according to the timeline.
I do not have an issue with that, but wanted to inform other readers of this thread that this can somehow happen.
Has anyone experienced this issue? Over the last few days, a specific Flow Card automation, for example, the âandâ condition â60 minutes before sunsetâ, throws an error. While restarting the application sometimes resolves the issue temporarily, the automation consistently fails again after a few minutes or days.
Could you tell me the error? I have never seen this before.
Thanx Marcel! Just tried to recreate but it works right now. I can screenshot it when it appears again. To explain it:
Normally there are different indicators as icons on a flow card when started (âtrueâ, âfalseâ or âsomething went wrongâ), and that last one appears sometimes when itâs buggy and then the flow stalls (no âthen-actionâ).
Here is another bug, but I donât know if that has something in common with the above:
Negative numbers are sometimes seen as invalid
âInvalid valueâ is of course not a bug / error, itâs a userâs fault:
AFAIK it takes an offset max 120 (positive or negative).
When you need longer offsets, use other events closer to the desired time.
Unfortunately, the problem is back for me after the latest update (2.4.8)âŠ
Times in subtitles in the event dropdown are gone again.
And all my AND-cards like âIt is after Duskâ etc throws error âCannot read properties of undefined (reading âgetTimeâ)â.
Quite frustrating:/ Let me know if I can assist with logs etc..
Letâs see if it will be fixed overnight. If thatâs the case then I might know where look for solution. The wierd thing is that I dont have this.
Thanks Peter. sorry for the misunderstanding. Thatâs not the problem; it also occurs if I enter, for example, -/+60 (which is max in deed).
The main problem is that within one AND card âprior to or after sunset/sundownâ, sometimes it works and sometimes not when testing the flow a few times. That looks like a behavior to me that may occur for other users as well?
About the AND card, I canât tell.
This flow with many SE conditional cards works fine @ Pro 2019 with SE v2.4.7-test
I got issues with my flows including Sun Event cards, like Event Sunset/Sunrise with offset, Is before Sunset/Sunrise, after version 2.4.7 update. I set up some test flows in the new version, and they all worked fine. Finally, I replaced Sun Event cards in my regular (old) flows with the same card and now all flow works again. My conclusion is that something in version 2.4.7 is not working in flows created in earlier versions.
Have you installed the lastest test-Version?
I had similar experience with a 2.4.7, (non-test) after installing test 2.4.7 (now 2.4.8) everything worked again
with my sunset flows.
As you see post before, there was never a regular 2.4.7 published. But it was installed some how ;-).
