Gardena Bluetooth Controller 01889-20 gets wrong system tiime

[urss133]

The problem

HomeAssistant sets the controller always to UTC instead to local time. This leads to a 2h shift of the programed time table. As soon as I connect with the Gardena Bluetooth App the Controller is set back to local time by the app.

What version of Home Assistant Core has the issue?

2023.9.3

What was the last working version of Home Assistant Core?

none

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Gardena Bluetooth

Link to integration documentation on our website

https://www.home-assistant.io/integrations/gardena_bluetooth/

Diagnostics information

not possible

Example YAML snippet

none

Anything in the logs that might be useful for us?

no

Additional information

No response

[home-assistant[bot]]

Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration (gardena_bluetooth) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `gardena_bluetooth` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign gardena_bluetooth` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

gardena_bluetooth documentation gardena_bluetooth source _{^{(message by IssueLinks)}}

[urss133]

I have to add that I use an ESP32 Bluetooth relay, maybe the time is taken from the ESP instead of the HA Core…

[elupus]

Nope from core. Have you set the timezone on your home assistant install?

[urss133]

yes timezone is set to GMT+1 Zürich (see prtscr). It looks like a wrong sign for the zone shift, -1 instead of +1 = 2 hours failure. therefore to timetable of the controller starts the sprinkler 2 hours later.

Am 05.10.2023 um 09:16 schrieb Joakim Plate @.***>:

Nope from core. Have you set the timezone on your home assistant install?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/101450#issuecomment-1748228507, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7SBNLQITWKYMJ5FCM5RZVTX5ZNFRAVCNFSM6AAAAAA5TYI2RSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYGIZDQNJQG4. You are receiving this because you authored the thread.



[elupus]

Seems screenshot is lost. Just want to make sure your HAOS timezone is set correctly. The code does rely on the python system timezone.

[urss133]

HOAS timezone is set to:Zeitzone(GMT+01:00) ZurichAm 08.10.2023 um 12:52 schrieb Joakim Plate @.***>: Seems screenshot is lost. Just want to make sure your HAOS timezone is set correctly. The code does rely on the python system timezone.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[urss133]

attached the missing screenshot:

[urss133]

Good news, after udating to release 2023.10.0 HOAS seems either stopped to set the time or does it now correctly. Since the update to 2013.10.0 a reconnection via Gardena App does no more trigger a time update, this means time of HOAS and Gardena Bluetooth device are now the same. A configured timetable is now executed on time as intended.

[elupus]

Ok. That is a bit weird. The issue seem to have stemmed from that core timezone and os level timezone not matching

[urss133]

yep. However integration works now as expected. Thx for your help and your contribution!

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.