HA sets time on DSC alarm to UTC via envisalink integration

[autumnwalker]

The problem

I've noticed the time on my alarm panel (physical) is frequently changed to UTC. I opened a ticket with Eyez-On and they have indicated other users have reported the same issue who are using Home Assistant and that HA is changing the time via the TPI.

Environment

• Home Assistant Core release with the issue: 0.108.3
• Last working Home Assistant Core release (if known): N/A
• Operating environment (Home Assistant/Supervised/Docker/venv): Docker
• Integration causing this issue: envisalink
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/envisalink/

Problem-relevant configuration.yaml

envisalink:
  host: [ip]
  panel_type: DSC
  user_name: [user]
  password: [pass]
  code: '[code]'
  port: 4025
  evl_version: 3
  keepalive_interval: 60
  zones: [redacted]

Traceback/Error logs

N/A

Additional information

I looked at the component code and don't see anything that would be causing this ... opening an issue in hopes someone has an idea and can remediate.

[dolenec]

I have other kind problem with ENV4. My network settings is that I completly block ENV4 card from in/out internet and can communicate only inside my network for security meaning..

The only problem is that after some time the time is not correct and is off course not updated via internet. How to fix that time would be updated via HA or via my NAS NTP as I did for all other blocked devices.

If I disable firewall for this specific ENV4 IP then time is correctly updated within 5 minutes or right away if I make ENV4 restart..

[autumnwalker]

Hey @dolenec - that sounds like a completely different issue than I have outlined here. Your best bet is to open a new thread to have your issue addressed.

It sounds like you have an Envisalink issue though, not a HA issue. I did some reading about what you are describing when searching for a solution to my issue. Eyez On indicated that it is not possible to provide your own NTP server (as you have requested) and that the EVL modules are designed to run with internet connectivity.

[autumnwalker]

Following up. Seems to occur whenever HA is restarted. At some point Envisalink will sync with its NTP and correct. Next time HA is restarted the time is off again.

[dolenec]

If I am correct time of ENV4 is set based on DSC alarm settings and not via ENV4 card itself. Do you have own NTP server on HA? Did you somehow set DSC alarm to get time from HA?

[autumnwalker]

I'm running an EVL3 card, but the 4 is the same in this regard according to Eyez-on.

The EVL3 is capable of setting the time of the DSC system based on the time zone settings of the Eyez-on account. This is the default behavior of the EVL. The EVL3 / 4 call home to the Eyez-on NTP for time. There is no option to change the NTP server on the EVL cards.

Something in HA is causing the EVL to set the time to UTC via the TPI. Eyez-on confirms this. There are other users who have also submit tickets with Eyez-on about this issue. Common thread between all of us is that we are using HA via the TPI.

[dolenec]

Do you maybe know the IP address to which EVL check NTP time so that I can reroute it on router to my personal NTP time server on QNAP...

[stale]

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.