v8.0.1 "setting end time" errors

[antamy]

I recently installed a new instance of njspc on a new Debian system. My system is an Intellitouch5+3 and I used git clone to install (this installed v8.0.1). It all appears to be working fine, including my custom rule for heat boosting (see #741).

What I see on startup is the following and the "Error setting end time" errors just continue ad infinitum. Is this to be expected?

Init state for Pool Controller
[1/9/2024, 11:38:14 AM] info: The current git branch output is master
[1/9/2024, 11:38:14 AM] info: The current git commit output is aa0ec318992c6710dd2f68352c261d0670501e77
[1/9/2024, 11:38:14 AM] info: Starting up SSDP server
[1/9/2024, 11:38:14 AM] info: Server is now listening on 0.0.0.0:4200 - 10.10.20.41:4200
[1/9/2024, 11:38:14 AM] info: Serial port: /dev/ttyUSB0 request to open successful 9600b 8-none-1
[1/9/2024, 11:38:14 AM] info: Checking njsPC versions...
[1/9/2024, 11:38:14 AM] info: Starting Pool System undefined
[1/9/2024, 11:38:14 AM] info: Listening for any installed OCPs
[1/9/2024, 11:38:14 AM] info: Auto-backup initialized Last Backup: 1969-12-31T19:00:00.000-0500
[1/9/2024, 11:38:14 AM] info: New socket client connected GQ9YEjW932zy9Xp1AAAA -- 10.10.20.40
[1/9/2024, 11:38:15 AM] info: Found IntelliTouch Controller
RESETTING DATA -- Controller type changed from undefined to intellitouch
Pentair IntelliTouch System Detected!
[1/9/2024, 11:38:15 AM] info: Initializing IntelliTouch Valve A
[1/9/2024, 11:38:15 AM] info: Initializing IntelliTouch Valve B
[1/9/2024, 11:38:15 AM] info: Initializing IntelliTouch Intake/Return Valves
[1/9/2024, 11:38:15 AM] info: Requesting intellitouch configuration
RS485 Stats:{ "bytesReceived": 1649 "success": 57, "failed": 1, "bytesSent": 696, "collisions": 0, "failureRate": 1.72% }
[1/9/2024, 11:38:29 AM] info: New socket client connected 2PM_RfkQhpTtayg3AAAC -- 10.10.20.50
[1/9/2024, 11:38:29 AM] info: [11:38:29 AM] 10.10.20.50 GET /state/all?null {}
[1/9/2024, 11:38:31 AM] error: Error setting end time for 6: TypeError: Cannot read properties of null (reading 'getTime')
[1/9/2024, 11:38:31 AM] error: Error setting end time for 41: TypeError: Cannot read properties of null (reading 'getTime')
[1/9/2024, 11:38:31 AM] error: Error synchronizing virtual circuits
[1/9/2024, 11:38:31 AM] error: Error triggering nixie schedules: Cannot read properties of null (reading 'getTime')
[1/9/2024, 11:38:31 AM] error: Error setting end time for 6: TypeError: Cannot read properties of null (reading 'getTime')
[1/9/2024, 11:38:37 AM] info: EasyTouch system config complete.
[1/9/2024, 11:38:37 AM] info: Initializing Nixie Controller
[1/9/2024, 11:38:37 AM] info: Nixie Controller Initialized
[1/9/2024, 11:38:37 AM] error: Error triggering nixie schedules: Cannot read properties of null (reading 'getTime')
[1/9/2024, 11:38:39 AM] error: Error triggering nixie schedules: Cannot read properties of null (reading 'getTime')
[1/9/2024, 11:38:41 AM] error: Error triggering nixie schedules: Cannot read properties of null (reading 'getTime')
[1/9/2024, 11:38:43 AM] error: Error triggering nixie schedules: Cannot read properties of null (reading 'getTime')
[1/9/2024, 11:38:45 AM] error: Error triggering nixie schedules: Cannot read properties of null (reading 'getTime')

Ids 6 and 41 are as follows in poolConfig.json. Id 41 is the generic HEATBOOST feature that just appears in the UI. Id 41 is the BOOSTRELAY circuit that is attached to Valve B.

    {
      "id": 6,
      "freeze": true,
      "type": 2,
      "isActive": true,
      "eggTimer": 720,
      "showInFeatures": true,
      "name": "Pool",
      "master": 0,
      "nameId": 61,
      "dontStop": false
    }
  ],
  "features": [
    {
      "id": 41,
      "freeze": false,
      "type": 0,
      "isActive": true,
      "eggTimer": 720,
      "showInFeatures": true,
      "master": 0,
      "name": "HEATBOOST",
      "nameId": 201,
      "macro": true
    },
    {
      "id": 42,
      "freeze": false,
      "type": 0,
      "isActive": true,
      "eggTimer": 720,
      "showInFeatures": true,
      "master": 0,
      "name": "BOOSTRELAY",
      "nameId": 202,
      "macro": true
    }

[rstrouse]

Please put your latitude and longitude into the setup so the system can calculate the sunrise/sunset times.

[antamy]

I have done that, however it makes no difference.

[davthomaspilot]

Same issue here.

[tagyoureit]

Can you upload a replay capture and I'll look. Do not check the reload configuration or it will reset your system.

[ChrisOgden]

I am seeing this as well, despite having the latitude and longitude into the system and it actively working with scheduled for sunset. (I am on 8.0.4)