[APP][Pro] Sun Events (Update SDK3)

Interesting screenshot. Until a few hours ago I had version 2.1.2 installed, and the settings page looked similar:

After updating to v1.4.9, the setting for Noon Warmth and Sunset Warmth are gone:

Changing the values of the other parameter and restarting the app didn’t solved this issue.
Any suggestions?

Version 2 is a complete rewrite according the latest homey guidelines. I am still testing this and they are not 100 % compatible (yet).

1 Like

Hi why not showing tag data sun events app? How can fix this?


Sun event app 1.4.8. I use HP2023 I should upgrade 2…version? How can do that?

I have the same even with version 2.1.3

For any app, there’s 2 ways to install it.

At the app store page:
Hit “Changelog”
Hit the orange button ‘Test’

Now you can install the testversion v2.1.3

The 2nd way to do it:
Just add /test to the app store URL, like, https://homey.app/en-nl/app/com.cyclone-software.sunevents/Sun-Events/test

Now you can install the testversion (if available)

I know how can install test wersion thx, but I ask why not showing tag info sun events app, and 2. version is fix this issue? And one more 2. version is test version all released or not ?

bad news thanks

Hello,

Just added the App & I got this error code:

Device Unavailable

Cannot read properties of undefined (reading ‘12’)

Tried to uninstall the App, reboot Homey Pro (last version) & reinstall the App (last version), same problem.

Please install the test version.

Heyhey Marcel, am I right that there is no “Night end” event in the test version?

Guess I’m switching to this then.

By the way, do we know when the test version goes official?

Hi,

That’s depended on your location and summertime.

If enough people test it, I will put it live. Want to be certain that everything works well as it is a complete rewrite.

That’s depended on your location and summertime.
Yeah forgot that detail. It was 14.09 in the Netherlands

Anyway i switched over, happy to test.

Hi, me again @MarcelT .
It is clear to me now that my location has no night at all in the summer, only astronomical dawn, lol. In Spistbergen there are days that don’t see an end - how does your app handle this? (<-- Edit: hmm, they just never do trigger, I guess…)

Anyway, my seasonal flows are working fine now, no more night end problems.

I have another issue though. I am trying to find a trigger point that is around two to two and a half hours after sunrise in the summer. In the winter it is different, but that I can handle.
Sunrise ends plus offset doesn’t get me there, golden hour ends plus offset (especially in summer) doesn’t get me there. I cannot use any delay cards because I need to be able to check for the “seasonal state” and restore it if needed (edit 2: I fixed that by storing states on every change - better that way). I am a bit stuck. So a few questions.

  • Do you know of any of your events, other app’s events, or other methods I haven’t thought about to get to sunrise +2.5 hours as a trigger?
  • If I replace the offset with a number variable, can I get beyond 60 minutes?
  • If not, would you consider extending the offset limit to, say, 3 hours?

Any help would be appreciated! With my thanks in advance.

As further clarification: this is the type of shutter behaviour I am trying to achieve.

Hi, I am on holiday now an will be back half September. Hopefully I remember to take a look to this😊.

1 Like

Oh, I really appreciate that you let me know that. Have a good one!

I use Advanced Scheduler App für Homey | Homey for this.

Alternatively you could use a second flow and something like chronograph app to set a timer to 2.5h and use it to trigger your flow when the timer reaches 0.

2 Likes

Thanks, @sgo that is what I did for a while. It’s like dropping a little ticker to extend a point in time - once you have reached that point. But I have a flow where I want to check the seasonal/astronomical state of shutter, and a few things I have in mind that don’t allow me to wait for x hours :slight_smile:

Thinking of that, a card that would give me the time of an event instead of trigger off it when it happens would solve it as well. I could math my own day schedule and completely get away from triggering or comparing against events +nHours. that way. I could then also catch “non-existent” events (the night problem, earlier in this thread) and work around them.

I’ll see first what Marcel has to say when he gets back.

Did you consider using azimuth and altitude, I.e., the position of the sun, as trigger points?

Azimuth is equivalent with time (neglecting DST). Altitude-range changes with season.

Regards,
Paul

1 Like