-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timezones #49
Comments
Is the posix code for Europe/Berlin |
|
Thanks I added it to the tz list and will come in the next release that I will post this week. |
v1.6.0 now supports the Europe/Berlin timezone. |
Could you please also add America/Sao_Paulo (Etc/GMT-3)? TIA |
It will show up on the next release. Btw the posix code for the timezone is |
Many Thanks!
Have a nice weekend.
Cesar
From: rstrouse ***@***.***>
Date: Friday, 19 May 2023 17:10
To: rstrouse/ESPSomfy-RTS ***@***.***>
Cc: cesarvoggithub ***@***.***>, Comment ***@***.***>
Subject: Re: [rstrouse/ESPSomfy-RTS] Timezones (Issue #49)
It will show up on the next release. Btw the posix code for the timezone is <-03>3
—
Reply to this email directly, view it on GitHub<#49 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AW7LWCPAKS4X7DNCK5XJWULXG7HSRANCNFSM6AAAAAAYBELC4I>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Update to v1.6.1 I added the Sao Paulo timezone. |
Thanks for the update. I'm afraid the Application is still 1.6.0. I first tried updating by uploading the firmware first (worked as the frmware "took" and changed to 1.6.1) and then the application (did not "take" as it remained 1.6.0). Then I decided I would start from scratch by reloading the original ESPhome firmware (worked as everything went back to default) and then by installing the newonboard file (worked, but firmware showed 1.6.1 and application remained 1.6.0). And since the application did not "take", America/Sao_Paulo is still not an available choice in the dropdown list. |
Scratch the above. I tried re-downloading the SomfyController.littlefs.bin file and this time it worked! |
Unfortunately you probably caught it before I changed the release token. A hard refresh of the browser would have fixed the issue. I am doing some browser tricks to clear the cache on for the app and unfortunately I missed one spot on the release files earlier. |
|
|
Can you please add Asia/Dubai UTC+4 (no daylight saving)? |
That is the same timezone as Unfortunately, I am not smart enough to gather which duplicates are the more logical selection. |
Cool - I did spend an hour looking at options before posting, honest. Appreciate the quick response and the great work - this is the third option I've tried to automate my Somfy and it worked like a charm. Not willing to pay the $230 Somfy want for their bridge for something that contains $20 worth of hardware! |
Instead of for example
|
OR (preferably) where there is overlap, i.e. US and Canada, you could do "Pacific", "Central", "Eastern", etc. |
Good idea. Generic time zones would be a good approach as I appreciate the need to keep it as light as possible. Happy to help define for this region if needed. |
Yeah the entire posix database is around 500 entries. To make sure we get valid log times it seemed pretty expensive to use the whole thing. Below is a link to one of the myriad of databases for them. I probably should have started with the Etc/GMT+- and eliminated those first. I am keying on the code (right hand column) and not the city for that very reason. You may be surprised at how weird all of this DST stuff is when trying to keep track of the 4th dimension. I'll take a stab at reworking tags to generalize them. https://github.com/nayarsystems/posix_tz_db/blob/master/zones.csv
To add to that I don't want any more cloud stuff in my house. 10 years from now folks are going to look around at their home automation battlefield to see many soldiers that worked for a couple of years but couldn't keep up the fight. Imagine the carnage and blown out rusted relics littering the scene. |
The new time zone data will be posted in v1.7.1 in the next couple of days. |
v1.7.1 has been released with the timezone changes discussed. |
Hey! There are timezones not considered in the index.js, e.g. "Europe/Berlin" (that's where I am ;)). Is definitely not a pressing issue though. I could add some and open a PR if you want, would take less important work from you 😀
Thanks!
The text was updated successfully, but these errors were encountered: