search

Blackymas / NSPanel_HA_Blueprint

This allows you to configure your complete NSPanel via Blueprint with UI and without changing anything in the code
1.44k stars 258 forks source link

`Bug` Time displayed on NSPanel 6hs ahead of Home Assistant #2363

Open nachobazz opened 2 days ago

nachobazz commented 2 days ago

TFT Version

4.3.11

Firmware Version

4.3.11 (ESPHome 2024.10.2)

Blueprint Version

4.3.11

Panel Model

US

What is the bug?

I installed and everything works fine, except the time is 6hs ahead of NSPanel.

I checked the timezones and they match on both devices. Interestingly changing the timezone settings on the panel leaves the time unaffected (it will always display the "real" time on HomeAssistant + 6hs.

I tried the solution recommended on this issue with no luck.

Steps to Reproduce

Install, flash and look at the panel. SCR-20241103-o3p

SCR-20241103-o49

Your Panel's YAML

substitutions:
  # Settings - Editable values
  device_name: "nspanel-living"
  friendly_name: "NSPanel Living"
  wifi_ssid: !secret wifi_ssid
  wifi_password: !secret wifi_password
  nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/blob/main/hmi/nspanel_us.tft"  # Optional
  # Add-on configuration (if needed)
  # heater_relay: "1"  # Possible values: "1" or "2"

# Customization area
##### My customization - Start #####

# Encrypt the communication between ESPHome and Home Assistant
api:
  encryption:
    key: "REDACTED"

# Add captive portal
captive_portal:

##### My customization - End #####

# Core and optional configurations
packages:
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: main
    files:
      - nspanel_esphome.yaml # Core package
      # Optional advanced and add-on configurations
      # - advanced/esphome/nspanel_esphome_advanced.yaml
      # - nspanel_esphome_addon_climate_cool.yaml
      - nspanel_esphome_addon_climate_heat.yaml
      # - nspanel_esphome_addon_climate_dual.yaml
    refresh: 300s

esp32:
  framework:
    type: esp-idf

ESPHome Logs

INFO ESPHome 2024.10.2 INFO Reading configuration /config/esphome/nspanel-living.yaml... INFO Updating https://github.com/Blackymas/NSPanel_HA_Blueprint@v4.3.11 INFO Detected timezone 'America/Montevideo' INFO Starting log output from 192.168.3.107 using esphome API INFO Successfully connected to nspanel-living @ 192.168.3.107 in 0.076s INFO Successful handshake with nspanel-living @ 192.168.3.107 in 0.096s [17:16:16][I][app:100]: ESPHome version 2024.10.2 compiled on Nov 3 2024, 11:33:33 [17:16:16][I][app:102]: Project esphome.NSPanel_HA_Blueprint version 4.3.11

[17:16:16][C][wifi:428]: Local MAC: C0:49:EF:60:AF:8C [17:16:16][C][wifi:433]: SSID: [redacted] [17:16:16][C][wifi:436]: IP Address: 192.168.3.107 [17:16:16][C][wifi:440]: BSSID: [redacted]

[17:16:16][C][wifi:443]: Signal strength: -60 dB ▂▄▆█ [17:16:16][C][wifi:447]: Channel: 10 [17:16:16][C][wifi:448]: Subnet: 255.255.255.0 [17:16:16][C][wifi:449]: Gateway: 192.168.3.1 [17:16:16][C][wifi:450]: DNS1: 1.1.1.1 [17:16:16][C][wifi:451]: DNS2: 8.8.8.8

[17:16:16][C][logger:186]: Level: DEBUG [17:16:16][C][logger:188]: Log Baud Rate: 0 [17:16:16][C][logger:189]: Hardware UART: UART0 [17:16:16][C][uart.idf:159]: UART Bus 0: [17:16:16][C][uart.idf:160]: TX Pin: GPIO16 [17:16:16][C][uart.idf:161]: RX Pin: GPIO17 [17:16:16][C][uart.idf:163]: RX Buffer Size: 256 [17:16:16][C][uart.idf:165]: Baud Rate: 115200 baud [17:16:16][C][uart.idf:166]: Data Bits: 8 [17:16:16][C][uart.idf:167]: Parity: NONE [17:16:16][C][uart.idf:168]: Stop bits: 1 [17:16:16][C][ledc.output:180]: LEDC Output: [17:16:16][C][ledc.output:181]: Pin GPIO21 [17:16:16][C][ledc.output:182]: LEDC Channel: 0 [17:16:16][C][ledc.output:183]: PWM Frequency: 1000.0 Hz [17:16:16][C][ledc.output:184]: Phase angle: 0.0° [17:16:16][C][ledc.output:185]: Bit depth: 16 [17:16:16][C][template.binary_sensor:028]: Template Binary Sensor 'Nextion display' [17:16:16][C][template.binary_sensor:028]: Device Class: 'connectivity' [17:16:16][C][template.number:050]: Template Number 'Display Brightness' [17:16:16][C][template.number:050]: Unit of Measurement: '%' [17:16:16][C][template.number:051]: Optimistic: YES [17:16:16][C][template.number:052]: Update Interval: 60.0s [17:16:16][C][template.number:050]: Template Number 'Display Brightness Dimdown' [17:16:16][C][template.number:050]: Unit of Measurement: '%' [17:16:16][C][template.number:051]: Optimistic: YES [17:16:16][C][template.number:052]: Update Interval: 60.0s [17:16:16][C][template.number:050]: Template Number 'Display Brightness Sleep' [17:16:16][C][template.number:050]: Unit of Measurement: '%' [17:16:16][C][template.number:051]: Optimistic: YES [17:16:16][C][template.number:052]: Update Interval: 60.0s [17:16:16][C][template.number:050]: Template Number 'Temperature Correction' [17:16:16][C][template.number:050]: Unit of Measurement: '°C' [17:16:16][C][template.number:051]: Optimistic: YES [17:16:16][C][template.number:052]: Update Interval: 60.0s [17:16:16][C][template.number:050]: Template Number 'Timeout Page'

[17:16:16][C][template.number:050]: Unit of Measurement: 's' [17:16:16][C][template.number:051]: Optimistic: YES [17:16:16][C][template.number:052]: Update Interval: 60.0s [17:16:16][C][template.number:050]: Template Number 'Timeout Dimming'

[17:16:16][C][template.number:050]: Unit of Measurement: 's' [17:16:16][C][template.number:051]: Optimistic: YES [17:16:16][C][template.number:052]: Update Interval: 60.0s [17:16:16][C][template.number:050]: Template Number 'Timeout Sleep'

[17:16:16][C][template.number:050]: Unit of Measurement: 's' [17:16:16][C][template.number:051]: Optimistic: YES [17:16:16][C][template.number:052]: Update Interval: 60.0s [17:16:16][C][template.select:065]: Template Select 'Baud rate'

[17:16:16][C][template.select:066]: Update Interval: 60.0s [17:16:16][C][template.select:069]: Optimistic: YES [17:16:16][C][template.select:070]: Initial Option: 115200 [17:16:16][C][template.select:071]: Restore Value: YES [17:16:16][C][template.select:065]: Template Select 'Wake-up page'

[17:16:16][C][template.select:066]: Update Interval: 60.0s [17:16:16][C][template.select:069]: Optimistic: YES [17:16:16][C][template.select:070]: Initial Option: home [17:16:16][C][template.select:071]: Restore Value: YES [17:16:17][C][template.select:065]: Template Select 'Update TFT display - Model'

[17:16:17][C][template.select:066]: Update Interval: 60.0s [17:16:17][C][template.select:069]: Optimistic: YES [17:16:17][C][template.select:070]: Initial Option: NSPanel EU [17:16:17][C][template.select:071]: Restore Value: YES [17:16:17][C][template.select:065]: Template Select 'Update TFT display - Baud rate'

[17:16:17][C][template.select:066]: Update Interval: 60.0s [17:16:17][C][template.select:069]: Optimistic: YES [17:16:17][C][template.select:070]: Initial Option: 921600 [17:16:17][C][template.select:071]: Restore Value: YES [17:16:17][C][switch.gpio:068]: GPIO Switch 'Nextion display - Power' [17:16:17][C][switch.gpio:091]: Restore Mode: always ON [17:16:17][C][switch.gpio:031]: Pin: GPIO4 [17:16:17][C][template.text_sensor:020]: Template Sensor 'Device Name'

[17:16:17][C][template.text_sensor:020]: Template Sensor 'Detailed Entity'

[17:16:17][C][template.text_sensor:020]: Template Sensor 'Notification Label' [17:16:17][C][template.text_sensor:020]: Template Sensor 'Notification Text' [17:16:17][C][template.text_sensor:020]: Template Sensor 'Version Blueprint'

[17:16:17][C][template.text_sensor:020]: Template Sensor 'Version ESPHome'

[17:16:17][C][template.sensor:022]: Template Sensor 'Blueprint' [17:16:17][C][template.sensor:022]: State Class: '' [17:16:17][C][template.sensor:022]: Unit of Measurement: '%' [17:16:17][C][template.sensor:022]: Accuracy Decimals: 1

[17:16:17][C][template.sensor:023]: Update Interval: 60.0s [17:16:17][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Left Button' [17:16:17][C][gpio.binary_sensor:016]: Pin: GPIO14 [17:16:17][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Right Button' [17:16:17][C][gpio.binary_sensor:016]: Pin: GPIO27 [17:16:17][C][switch.gpio:068]: GPIO Switch 'Relay 1' [17:16:17][C][switch.gpio:091]: Restore Mode: restore defaults to OFF [17:16:17][C][switch.gpio:031]: Pin: GPIO22 [17:16:17][C][switch.gpio:068]: GPIO Switch 'Relay 2' [17:16:17][C][switch.gpio:091]: Restore Mode: restore defaults to OFF [17:16:17][C][switch.gpio:031]: Pin: GPIO19 [17:16:17][C][template.switch:068]: Template Switch 'Notification unread' [17:16:17][C][template.switch:091]: Restore Mode: always OFF [17:16:17][C][template.switch:057]: Optimistic: YES [17:16:17][C][template.switch:068]: Template Switch 'Notification sound' [17:16:17][C][template.switch:091]: Restore Mode: restore defaults to OFF [17:16:17][C][template.switch:057]: Optimistic: YES [17:16:17][C][template.switch:068]: Template Switch 'Relay 0 (dummy)' [17:16:17][C][template.switch:091]: Restore Mode: always OFF [17:16:17][C][template.switch:057]: Optimistic: YES

[17:16:17][C][psram:021]: Available: YES [17:16:17][C][psram:024]: Size: 2036 KB

[17:16:17][C][nextion:142]: Device Model: NX4832F035_011C [17:16:17][C][nextion:143]: Firmware Version: 72 [17:16:17][C][nextion:144]: Serial Number: DDAF340132BA155B [17:16:17][C][nextion:145]: Flash Size: 16777216 [17:16:17][C][nextion:147]: Wake On Touch: YES [17:16:17][C][nextion:148]: Exit reparse: YES [17:16:17][C][factory_reset.button:011]: Factory Reset Button 'Factory reset'

[17:16:17][C][restart.button:017]: Restart Button 'Restart'

[17:16:17][C][adc:097]: ADC Sensor 'ntc_source' [17:16:17][C][adc:097]: Device Class: 'voltage' [17:16:17][C][adc:097]: State Class: 'measurement' [17:16:17][C][adc:097]: Unit of Measurement: 'V' [17:16:17][C][adc:097]: Accuracy Decimals: 2 [17:16:17][C][adc:107]: Pin: GPIO38 [17:16:17][C][adc:122]: Attenuation: 12db [17:16:17][C][adc:141]: Samples: 4 [17:16:17][C][adc:142]: Update Interval: 10.0s [17:16:17][C][resistance:010]: Resistance Sensor 'resistance_sensor' [17:16:17][C][resistance:010]: State Class: 'measurement' [17:16:17][C][resistance:010]: Unit of Measurement: 'Ω' [17:16:17][C][resistance:010]: Accuracy Decimals: 1

[17:16:17][C][resistance:011]: Configuration: DOWNSTREAM [17:16:17][C][resistance:012]: Resistor: 11200.00Ω [17:16:17][C][resistance:013]: Reference Voltage: 3.3V [17:16:17][C][ntc:014]: NTC Sensor 'Temperature' [17:16:17][C][ntc:014]: Device Class: 'temperature' [17:16:17][C][ntc:014]: State Class: 'measurement' [17:16:17][C][ntc:014]: Unit of Measurement: '°C' [17:16:17][C][ntc:014]: Accuracy Decimals: 1

[17:16:17][C][thermostat.climate:1301]: Start-up Delay Enabled: NO [17:16:17][C][thermostat.climate:1317]: Heating Parameters: [17:16:17][C][thermostat.climate:1318]: Deadband: 0.5°C [17:16:17][C][thermostat.climate:1319]: Overrun: 0.5°C [17:16:17][C][thermostat.climate:1326]: Minimum Off Time: 300s [17:16:17][C][thermostat.climate:1328]: Minimum Run Time: 300s [17:16:17][C][thermostat.climate:1343]: Minimum Idle Time: 30s [17:16:17][C][thermostat.climate:1344]: Supports AUTO: NO [17:16:17][C][thermostat.climate:1345]: Supports HEAT/COOL: NO [17:16:17][C][thermostat.climate:1346]: Supports COOL: NO [17:16:17][C][thermostat.climate:1347]: Supports DRY: NO [17:16:17][C][thermostat.climate:1348]: Supports FAN_ONLY: NO [17:16:17][C][thermostat.climate:1350]: Supports FAN_ONLY_ACTION_USES_FAN_MODE_TIMER: NO [17:16:17][C][thermostat.climate:1351]: Supports FAN_ONLY_COOLING: NO [17:16:17][C][thermostat.climate:1356]: Supports FAN_WITH_HEATING: NO [17:16:17][C][thermostat.climate:1358]: Supports HEAT: YES [17:16:17][C][thermostat.climate:1359]: Supports FAN MODE ON: NO [17:16:17][C][thermostat.climate:1360]: Supports FAN MODE OFF: NO [17:16:17][C][thermostat.climate:1361]: Supports FAN MODE AUTO: NO [17:16:17][C][thermostat.climate:1362]: Supports FAN MODE LOW: NO [17:16:17][C][thermostat.climate:1363]: Supports FAN MODE MEDIUM: NO [17:16:17][C][thermostat.climate:1364]: Supports FAN MODE HIGH: NO [17:16:17][C][thermostat.climate:1365]: Supports FAN MODE MIDDLE: NO [17:16:17][C][thermostat.climate:1366]: Supports FAN MODE FOCUS: NO [17:16:17][C][thermostat.climate:1367]: Supports FAN MODE DIFFUSE: NO [17:16:17][C][thermostat.climate:1368]: Supports FAN MODE QUIET: NO [17:16:17][C][thermostat.climate:1369]: Supports SWING MODE BOTH: NO [17:16:17][C][thermostat.climate:1370]: Supports SWING MODE OFF: NO [17:16:17][C][thermostat.climate:1371]: Supports SWING MODE HORIZONTAL: NO [17:16:17][C][thermostat.climate:1372]: Supports SWING MODE VERTICAL: NO [17:16:17][C][thermostat.climate:1373]: Supports TWO SET POINTS: NO [17:16:17][C][thermostat.climate:1375]: Supported PRESETS: [17:16:17][C][thermostat.climate:1379]: Supports HOME: YES [17:16:17][C][thermostat.climate:963]: HOME Is Default: NO [17:16:17][C][thermostat.climate:970]: HOME Default Target Temperature Low: 18.0°C [17:16:17][C][thermostat.climate:984]: HOME Default Mode: HEAT [17:16:17][C][thermostat.climate:1383]: Supported CUSTOM PRESETS: [17:16:17][C][thermostat.climate:1387]: Supports Off: YES [17:16:17][C][thermostat.climate:963]: Off Is Default: YES [17:16:17][C][thermostat.climate:970]: Off Default Target Temperature Low: 18.0°C [17:16:17][C][thermostat.climate:984]: Off Default Mode: OFF [17:16:17][C][thermostat.climate:1391]: On boot, restore from: MEMORY [17:16:17][C][homeassistant.time:010]: Home Assistant Time:

[17:16:18][C][captive_portal:089]: Captive Portal:

[17:16:18][C][mdns:117]: Hostname: nspanel-living [17:16:18][C][esphome.ota:073]: Over-The-Air updates: [17:16:18][C][esphome.ota:074]: Address: nspanel-living.local:3232 [17:16:18][C][esphome.ota:075]: Version: 2 [17:16:18][C][esphome.ota:078]: Password configured [17:16:18][C][safe_mode:018]: Safe Mode: [17:16:18][C][safe_mode:020]: Boot considered successful after 60 seconds [17:16:18][C][safe_mode:021]: Invoke after 3 boot attempts [17:16:18][C][safe_mode:023]: Remain in safe mode for 180 seconds [17:16:18][C][api:140]: API Server: [17:16:18][C][api:141]: Address: nspanel-living.local:6053 [17:16:18][C][api:143]: Using noise encryption: YES [17:16:18][C][wifi_signal.sensor:010]: WiFi Signal 'RSSI' [17:16:18][C][wifi_signal.sensor:010]: Device Class: 'signal_strength' [17:16:18][C][wifi_signal.sensor:010]: State Class: 'measurement' [17:16:18][C][wifi_signal.sensor:010]: Unit of Measurement: 'dBm' [17:16:18][C][wifi_signal.sensor:010]: Accuracy Decimals: 0

Home Assistant Logs

I see no issues in the logs that look related to the issue:

2024-11-03 11:27:54,537 INFO 304 GET /devices (0.0.0.0) 3.26ms 2024-11-03 11:27:59,549 INFO 304 GET /devices (0.0.0.0) 2.67ms 2024-11-03 11:28:04,536 INFO 304 GET /devices (0.0.0.0) 3.11ms 2024-11-03 11:28:09,551 INFO 304 GET /devices (0.0.0.0) 3.13ms 2024-11-03 11:28:14,547 INFO 304 GET /devices (0.0.0.0) 2.67ms 2024-11-03 11:28:19,555 INFO 304 GET /devices (0.0.0.0) 3.42ms 2024-11-03 11:28:24,558 INFO 304 GET /devices (0.0.0.0) 2.81ms 2024-11-03 11:28:29,566 INFO 304 GET /devices (0.0.0.0) 3.20ms 2024-11-03 11:28:34,563 INFO 304 GET /devices (0.0.0.0) 3.66ms 2024-11-03 11:28:39,588 INFO 304 GET /devices (0.0.0.0) 2.69ms 2024-11-03 11:28:44,569 INFO 304 GET /devices (0.0.0.0) 3.00ms 2024-11-03 11:28:49,588 INFO 304 GET /devices (0.0.0.0) 2.51ms 2024-11-03 11:28:54,573 INFO 304 GET /devices (0.0.0.0) 2.99ms 2024-11-03 11:28:59,584 INFO 304 GET /devices (0.0.0.0) 1.91ms 2024-11-03 11:29:04,582 INFO 304 GET /devices (0.0.0.0) 3.46ms 2024-11-03 11:29:09,603 INFO 304 GET /devices (0.0.0.0) 2.84ms 2024-11-03 11:29:14,591 INFO 304 GET /devices (0.0.0.0) 2.69ms 2024-11-03 11:29:19,597 INFO 304 GET /devices (0.0.0.0) 3.45ms 2024-11-03 11:29:24,598 INFO 304 GET /devices (0.0.0.0) 3.05ms 2024-11-03 11:29:29,627 INFO 304 GET /devices (0.0.0.0) 3.24ms 2024-11-03 11:29:34,607 INFO 304 GET /devices (0.0.0.0) 3.12ms 2024-11-03 11:29:40,057 INFO 304 GET /devices (0.0.0.0) 4.82ms 2024-11-03 11:29:46,012 INFO 304 GET /devices (0.0.0.0) 1.89ms 2024-11-03 11:29:52,017 INFO 304 GET /devices (0.0.0.0) 2.80ms 2024-11-03 11:29:58,017 INFO 304 GET /devices (0.0.0.0) 2.46ms 2024-11-03 11:30:04,044 INFO 304 GET /devices (0.0.0.0) 3.42ms 2024-11-03 11:30:10,010 INFO 304 GET /devices (0.0.0.0) 3.57ms 2024-11-03 11:30:16,053 INFO 304 GET /devices (0.0.0.0) 3.56ms 2024-11-03 11:30:22,025 INFO 304 GET /devices (0.0.0.0) 2.91ms 2024-11-03 11:30:28,016 INFO 304 GET /devices (0.0.0.0) 3.12ms 2024-11-03 11:30:34,014 INFO 304 GET /devices (0.0.0.0) 3.57ms 2024-11-03 11:30:40,131 INFO 304 GET /devices (0.0.0.0) 3.86ms 2024-11-03 11:30:46,024 INFO 304 GET /devices (0.0.0.0) 2.62ms 2024-11-03 11:30:51,023 INFO 304 GET /devices (0.0.0.0) 3.26ms 2024-11-03 11:30:56,026 INFO 304 GET /devices (0.0.0.0) 2.32ms 2024-11-03 11:31:01,018 INFO 304 GET /devices (0.0.0.0) 2.74ms 2024-11-03 11:31:06,027 INFO 304 GET /devices (0.0.0.0) 3.33ms 2024-11-03 11:31:11,047 INFO 304 GET /devices (0.0.0.0) 3.12ms 2024-11-03 11:31:16,015 INFO 304 GET /devices (0.0.0.0) 2.91ms 2024-11-03 11:31:21,028 INFO 304 GET /devices (0.0.0.0) 3.08ms 2024-11-03 11:31:26,025 INFO 304 GET /devices (0.0.0.0) 2.46ms 2024-11-03 11:31:31,081 INFO 304 GET /devices (0.0.0.0) 8.80ms 2024-11-03 11:31:36,055 INFO 304 GET /devices (0.0.0.0) 3.00ms 2024-11-03 11:31:41,034 INFO 304 GET /devices (0.0.0.0) 3.35ms 2024-11-03 11:31:41,598 INFO 200 GET /edit?configuration=nspanel-living.yaml (0.0.0.0) 2.64ms 2024-11-03 11:31:41,887 INFO 101 GET /ace (0.0.0.0) 1.01ms 2024-11-03 11:31:41,969 INFO Running command 'esphome --dashboard -q vscode --ace /config/esphome' 2024-11-03 11:33:07,943 INFO 200 POST /edit?configuration=nspanel-living.yaml (0.0.0.0) 6.16ms 2024-11-03 11:33:10,338 INFO 200 POST /edit?configuration=nspanel-living.yaml (0.0.0.0) 3.07ms 2024-11-03 11:33:10,479 INFO 304 GET /info?configuration=nspanel-living.yaml (0.0.0.0) 8.01ms 2024-11-03 11:33:11,704 INFO 101 GET /run (0.0.0.0) 1.28ms 2024-11-03 11:33:12,268 INFO Running command 'esphome --dashboard run /config/esphome/nspanel-living.yaml --device 192.168.3.107' 2024-11-03 11:39:39,209 INFO 304 GET /devices (0.0.0.0) 7.95ms 2024-11-03 15:51:42,370 INFO 200 GET / (0.0.0.0) 3.55ms 2024-11-03 15:51:42,812 INFO 304 GET /devices (0.0.0.0) 3.80ms 2024-11-03 15:51:47,280 INFO 101 GET /logs (0.0.0.0) 1.08ms 2024-11-03 15:51:47,805 INFO Running command 'esphome --dashboard logs /config/esphome/nspanel-living.yaml --device 192.168.3.107' 2024-11-03 15:51:48,027 INFO 304 GET /devices (0.0.0.0) 3.22ms 2024-11-03 15:51:52,809 INFO 304 GET /devices (0.0.0.0) 2.78ms 2024-11-03 15:51:57,823 INFO 304 GET /devices (0.0.0.0) 2.39ms 2024-11-03 15:52:02,818 INFO 304 GET /devices (0.0.0.0) 2.78ms 2024-11-03 15:52:07,834 INFO 304 GET /devices (0.0.0.0) 2.58ms 2024-11-03 15:52:12,834 INFO 304 GET /devices (0.0.0.0) 3.36ms 2024-11-03 15:52:18,822 INFO 304 GET /devices (0.0.0.0) 2.10ms 2024-11-03 15:52:24,840 INFO 304 GET /devices (0.0.0.0) 2.93ms 2024-11-03 15:52:30,829 INFO 304 GET /devices (0.0.0.0) 2.87ms 2024-11-03 15:52:36,708 INFO 304 GET /devices (0.0.0.0) 3.08ms 2024-11-03 15:52:42,772 INFO 304 GET /devices (0.0.0.0) 2.41ms 2024-11-03 15:52:48,727 INFO 304 GET /devices (0.0.0.0) 2.01ms 2024-11-03 15:52:54,733 INFO 304 GET /devices (0.0.0.0) 3.24ms 2024-11-03 15:53:00,716 INFO 304 GET /devices (0.0.0.0) 2.18ms 2024-11-03 15:53:06,711 INFO 304 GET /devices (0.0.0.0) 3.78ms 2024-11-03 15:53:12,710 INFO 304 GET /devices (0.0.0.0) 3.56ms 2024-11-03 15:53:18,713 INFO 304 GET /devices (0.0.0.0) 3.07ms 2024-11-03 15:53:24,716 INFO 304 GET /devices (0.0.0.0) 3.78ms 2024-11-03 15:53:30,716 INFO 304 GET /devices (0.0.0.0) 3.92ms 2024-11-03 15:53:36,711 INFO 304 GET /devices (0.0.0.0) 2.58ms 2024-11-03 15:53:42,779 INFO 304 GET /devices (0.0.0.0) 2.82ms 2024-11-03 15:53:47,715 INFO 304 GET /devices (0.0.0.0) 3.75ms 2024-11-03 15:54:55,194 INFO 200 GET / (0.0.0.0) 2.49ms 2024-11-03 15:54:55,335 INFO 304 GET /devices (0.0.0.0) 4.06ms 2024-11-03 17:15:20,560 INFO 200 GET / (0.0.0.0) 2.02ms 2024-11-03 17:15:20,733 INFO 304 GET /devices (0.0.0.0) 5.39ms 2024-11-03 17:15:21,895 INFO 200 GET /edit?configuration=nspanel-living.yaml (0.0.0.0) 3.72ms 2024-11-03 17:15:22,176 INFO 101 GET /ace (0.0.0.0) 1.20ms 2024-11-03 17:15:22,254 INFO Running command 'esphome --dashboard -q vscode --ace /config/esphome' 2024-11-03 17:16:09,899 INFO 304 GET /devices (0.0.0.0) 3.38ms 2024-11-03 17:16:12,324 INFO 101 GET /logs (0.0.0.0) 1.67ms 2024-11-03 17:16:12,843 INFO Running command 'esphome --dashboard logs /config/esphome/nspanel-living.yaml --device 192.168.3.107' 2024-11-03 17:16:14,899 INFO 304 GET /devices (0.0.0.0) 2.38ms 2024-11-03 17:16:19,900 INFO 304 GET /devices (0.0.0.0) 3.39ms 2024-11-03 17:16:25,779 INFO 304 GET /devices (0.0.0.0) 2.99ms 2024-11-03 17:16:31,774 INFO 304 GET /devices (0.0.0.0) 3.07ms 2024-11-03 17:16:37,782 INFO 304 GET /devices (0.0.0.0) 2.43ms 2024-11-03 17:16:43,794 INFO 304 GET /devices (0.0.0.0) 2.81ms 2024-11-03 17:16:49,772 INFO 304 GET /devices (0.0.0.0) 7.06ms 2024-11-03 17:16:55,791 INFO 304 GET /devices (0.0.0.0) 2.73ms 2024-11-03 17:17:01,793 INFO 304 GET /devices (0.0.0.0) 3.14ms 2024-11-03 17:17:06,776 INFO 304 GET /devices (0.0.0.0) 2.75ms 2024-11-03 17:17:11,788 INFO 304 GET /devices (0.0.0.0) 3.07ms

nachobazz commented 2 days ago

One additonal note that could shed some light on the issue.

The local time has just passed 00:00 but the date of the device still shows the correct day (Sunday) even though the device is past 12:00 am.

This means the panel "knows" it's not really Monday yet, despite the time displayed.

Any ideas?

IMG_9020

ad-borges commented 2 days ago

Same here. Brazil. Also GMT -3 Started yesterday. Now im updating to last version but already seen that yours is at last version and have the bug. very very strange.

edwardtfn commented 2 days ago
dburger2023 commented 2 days ago

I have the same issue. Try many time Zone with no success

edwardtfn commented 2 days ago

Have you tried this?

rleongcs commented 1 day ago

Same is happening to me. I am not sure when it started but it definitely is very recent. Maybe due to the ESPHome automatic version update? I have also tried to change different time zones to no effect. One thing I am seeing from the blueprint is the offset looks weird as highlighted in yellow in screenshot attached. image

edwardtfn commented 1 day ago

One thing I am seeing from the blueprint is the offset looks weird as highlighted in yellow in screenshot attached.

This is standard POSIX format for time zone, which is used by ESP to calculate the time. But looks like ESP is using the value between <>, which is supposed to be just a description for this. The script shared here should deal with this.

rleongcs commented 1 day ago

@edwardtfn From your explanation, looks like ESPHome implemented wrongly and should the fix not be from them?

edwardtfn commented 1 day ago

Well, I have to pick my battles. This thing with time zones is not new and as most of the ESPHome projects would never display a time to users, it is a bit hard to get a priority to this. And I believe Arduino handle this in a different way, so this may be visible only for users of ESP-IDF framework, which certainly are not a majority on ESPHome world. This issue was reported at around 2 years ago and still not fixed from ESPHome side, but mainly to the fact that there's no ESPHome code to be fixed, as the error is on the Espressif side. However, as my comment here, this was already fixed by them on the ESP-IDF v5.1. The latest ESP-IDF is v5.3, but ESPHome still using ESP-IDF v4.4, which is not even maintained anymore: image image

But I don't blame the ESPHome guys... update this is not trivial. I've worked to prepare this project for ESP v5 and it was quite a lot of work (which I'm happy it is already done). The same have to be done to all the other components available at ESPHome. There is a PR handling this update, but I believe it still have a way to go, as that is also covering the use an alternative for PlatformIO.

So, with all that said, I will take the shortcut to happy users by find a workaround on our side. 😉

edwardtfn commented 1 day ago

v4.3.12 - Hotfix for Incorrect Timezone Calculation Issues

This hotfix addresses critical issues with timezone handling on the NSPanel, specifically with POSIX string handling in ESP-IDF v4.4 and resolving an error in the propagation of timezone selection from the Blueprint to ESPHome. These fixes ensure accurate and consistent time display, fully synchronized with Home Assistant.

Fix for Incorrect Time Display Due to Timezone Handling (#2363, #2304)

edwardtfn commented 1 day ago

It would be nice if you can validate this new version. 😉

nachobazz commented 1 day ago

Hi @edwardtfn. I reckon I'll be back in my house in a few days, so I will be able to test this soon.

Sorry for the noob question, but could you provide a methodology to test this merge before it's released in the production channel? Should I install the esphome beta add-on in HASOS?

edwardtfn commented 1 day ago

It is released already. 😉 But when you have a chance, please update to this new version and let me know if it fixed the issue.

pana800 commented 18 hours ago

Hi all, Sorry but my 2 panels are still facing the same issue after importing new fix version. Could other people confirm the issue is gone? Thanks a lot

edwardtfn commented 17 hours ago

Have you selected the timezone in the blueprint?

pana800 commented 17 hours ago

yes, I did image

edwardtfn commented 15 hours ago

Could you please share the ESPHome logs? Whe your panel restart, after a few seconds, the Blueprint will send the timezone settings and log this. It would be nice to see those logs.

kkondyl commented 12 hours ago

same issue with latest fix... displayed time is 13:54 instead of 19:54

[19:54:14][D][time:051]: Synchronized time: 2024-11-05 13:54:14 [19:54:14][D][time.on_time_sync:211]: System clock synchronized [19:54:14][D][time.on_time_sync:212]: Timezone: <+03>-3 ... [19:54:19][I][script.set_timezone:3151]: Setting timezone: <+03>-3 [19:54:19][C][homeassistant.time:010]: Home Assistant Time:

edwardtfn commented 11 hours ago

Ok. Could you please go to the blueprint, change the timezone to any other timezone, save, wait for your panel report the new timezone in it's logs, then change it back to your desired timezone, wait for your panel to report it in the log again, then share all this log?

kkondyl commented 9 hours ago

changing the timezone twice resolved the issue

senolsun commented 8 hours ago

Europe/Istanbul still has issues. Had to switch to Moscow to fix the issue. Europe/Istanbul shows GMT-3 instead of +3

edwardtfn commented 7 hours ago

Could you please share ESPHome logs from when you change the timezones on the Blueprint?