PG3 ELK Node server 3.6.5

[Jimbo.Automates]

The Polyglot Version 3 Node server for ELK Security Version 3.6.5 is released.  See the Release Notes 

This release added support for ELK Lights see Light Node. Since releasing and testing in my production environment I realize there is an issue since ElkRP has a 12 character limit for device names. If your device name is longer you are forced to use the node address which works perfectly but visually is not ideal in the ELk interface. Please provide feedback on this if you use this feature. This may necessitate adding the ability to export/import which is a fair amount of work.

See the README for more information, including information on moving from PG2.

If you have issues or requests please check PG3 ELK Github issues to see it has already been listed.  And if you want to thumbs up an issue I will try to prioritize fixing the ones with most votes.

Edited April 7, 2023 by Jimbo.Automates
Change to 3.6.5

[DennisC]

@Jimbo.Automates,

The link for Light Node above is not working. It results in a not found message.

[Jimbo.Automates]

2 hours ago, DennisC said:

@Jimbo.Automates,

The link for Light Node above is not working. It results in a not found message.

Fixed

[DennisC]

FYI,

The update went fine, but the light nodes were not automatically removed. I had to delete them manually.

[DennisC]

Follow up question -

I just noticed that I have two nodes remaining with light bulb symbols in admin console. One is for a Elk Task, it shows as nxxx_task_1 - Elk Light and the other one as nzzz_counter_2 - Elk Counter.

They both are doing things in the Elk M1, should they remain or can they be deleted from the node server?

[Jimbo.Automates]

20 minutes ago, DennisC said:

The update went fine, but the light nodes were not automatically removed. I had to delete them manually.

Yes, I've noticed that as well, might be a PG3 bug, I need to look into it further.

14 minutes ago, DennisC said:

I just noticed that I have two nodes remaining with light bulb symbols in admin console. One is for a Elk Task, it shows as nxxx_task_1 - Elk Light and the other one as nzzz_counter_2 - Elk Counter.

They both are doing things in the Elk M1, should they remain or can they be deleted from the node server?

Yes, I should change the Icons, but all tasks and counters defined in ElkRP are pulled across.  I could add configuration options like I have for Area's and Outputs that allows you to define which tasks and counters were tracked in the NS.

 

[DennisC]

5 minutes ago, Jimbo.Automates said:

Yes, I should change the Icons, but all tasks and counters defined in ElkRP are pulled across.  I could add configuration options like I have for Area's and Outputs that allows you to define which tasks and counters were tracked in the NS.

If you get to it great, if not, no worries. I thought it was different than a light node and wanted verification. Thanks.

[garybixler]

Hi, just update PGx to version 3.1.24 and it seems that the poll zone voltages aren't working. Did a restart on the NS but still no polling. Also the eisy was rebooted. The log used to show polling but I no longer see that. After doing a query on the zone the correct voltage was filled in.  I included a partial log. Also made sure 'set poll voltages' were set to true. ELK may have updated when PGx was rebooted.

IOx  5.5.9

PGx  3.1.24

ELK  3.6.0

Thanks

New Text Document (3).txt

[Jimbo.Automates]

Hi, just update PGx to version 3.1.24 and it seems that the poll zone voltages aren't working. Did a restart on the NS but still no polling. Also the eisy was rebooted. The log used to show polling but I no longer see that. After doing a query on the zone the correct voltage was filled in.  I included a partial log. Also made sure 'set poll voltages' were set to true. ELK may have updated when PGx was rebooted.
IOx  5.5.9
PGx  3.1.24
ELK  3.6.0
Thanks
New Text Document (3).txt

Ok, will take a look but nothing related to zones changed in this release.

Sent from my Pixel 6 Pro using Tapatalk

[garybixler]

I updated to version 3.6.4 but am still not seeing polling of the zone voltages. Area1 and zone 'Poll Voltage' are set to true. Doing a query on the zone will load the latest voltage level. Short Poll is set to 30 seconds. Power reset the eisy but no difference.

New Text Document (3).txt

[Jimbo.Automates]

I updated to version 3.6.4 but am still not seeing polling of the zone voltages. Area1 and zone 'Poll Voltage' are set to true. Doing a query on the zone will load the latest voltage level. Short Poll is set to 30 seconds. Power reset the eisy but no difference.
New Text Document (3).txt

Sorry, that's on my list for today. Had to fix a crash first and didn't have time to investigate that last night.

Sent from my Pixel 6 Pro using Tapatalk

[Jimbo.Automates]

3 hours ago, garybixler said:

I updated to version 3.6.4 but am still not seeing polling of the zone voltages. Area1 and zone 'Poll Voltage' are set to true. Doing a query on the zone will load the latest voltage level. Short Poll is set to 30 seconds. Power reset the eisy but no difference.

New Text Document (3).txt 10.22 kB · 1 download

There is an error, but it must have happened previous day because it's not in the log.   I can tell because NS keeps printing this:

2023-04-01 08:03:46,526 Thread-232 udi_interface      WARNING  Controller:handler_poll: waiting for sync and node initialization to complete

So the initial sync didn't complete.  This can also happen if ElkRP is connected.  I need to look into a way to allow this to be detected on the ISY side...

Please restart NS and when it completes PM me the log package.

 

[Jimbo.Automates]

Nevermind @garybixler I think I found the error, I'll have a new release soon.

[Jimbo.Automates]

The Polyglot Version 3 Node server for ELK Security Version 3.6.5 is released.  See the Release Notes 

If you are running 3.6.0 or greater then you need to update or may experience crashes.

 

[garybixler]

Sorry was away for awhile. I updated to version 3.6.5 and all looks good now. Thanks.

Edited April 1, 2023 by garybixler

[bigDvette]

this shows up as an elk notice under the node server.

 

ERROR: 04/02/2023 18:09:26 See log for: ISY None is not initialized, see log

I can't see any log entries under the ELK node server when I click on LOG.  

Log file when I download has this for that start.

 

2023-04-02 18:06:51,418 Thread-140 udi_interface      WARNING  Controller:elk_stop: Stopping ELK thread...
2023-04-02 18:08:14,034 MainThread udi_interface      INFO     polylogger:set_basic_config: set_basic_config: enable=True level=30
2023-04-02 18:08:14,410 MainThread udi_interface      INFO     __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.56 Starting...
2023-04-02 18:08:14,493 MainThread udi_interface.interface INFO     interface:__init__: Initialization received from Polyglot V3 3.1.24  [ISY: 5.5.9, Slot: 11]
2023-04-02 18:08:14,494 MainThread udi_interface.interface INFO     interface:__init__: Connect: Network Interface: DELETED}
2023-04-02 18:08:14,494 Interface  udi_interface.interface INFO     interface:_startMqtt: Connecting to MQTT... localhost:8883
2023-04-02 18:08:14,495 MainThread udi_interface.interface WARNING  interface:start: No node server version specified. Using deprecated server.json version
2023-04-02 18:08:14,495 MainThread udi_interface.interface WARNING  interface:db_getNodeDrivers: controller not found in database.
2023-04-02 18:08:14,495 MainThread udi_interface.custom INFO     custom:_save: Sending data notices to Polyglot.
2023-04-02 18:08:14,495 MainThread udi_interface.interface WARNING  interface:send: MQTT Send waiting on connection :: {'set': [{'key': 'notices', 'value': {}}]}
2023-04-02 18:08:14,496 Interface  udi_interface.interface INFO     interface:_startMqtt: Using SSL certs: xxxxxxx.key
2023-04-02 18:08:14,503 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with result code 0 (Success)
2023-04-02 18:08:14,504 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/IDIDIDIDIDIDI -  MID: 2 Result: 0
2023-04-02 18:08:14,546 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,)
2023-04-02 18:08:17,578 MainThread udi_interface.interface INFO     interface:addNode: Adding node ELK Controller(controller) [None]
2023-04-02 18:08:17,578 MainThread udi_interface.interface INFO     interface:setController: Using node "controller", driver "ST" for connection status.
2023-04-02 18:08:17,596 MQTT       udi_interface.interface INFO     interface:_message: Successfully set key = notices
2023-04-02 18:08:36,129 ELK-4065   udi_interface      WARNING  Controller:add_node: Existing node name 'Output 001' for output_1 does not match requested name 'Output-001', NOT changing to match, set change_node_names=true to enable
2023-04-02 18:08:44,004 Thread-27  udi_interface      WARNING  Controller:handler_poll: waiting for sync and node initialization to complete
2023-04-02 18:09:13,005 Thread-52  udi_interface      WARNING  Controller:handler_poll: waiting for sync and node initialization to complete
2023-04-02 18:09:26,497 ELK-4065   udi_interface      WARNING  Controller:sync_complete: ELK Controller: All nodes added, ready to go...
2023-04-02 18:09:26,498 ELK-4065   udi_interface      ERROR    Controller:update_config_docs: ISY None is not initialized, see log

[Jimbo.Automates]

Thanks, yes I saw that error, it happens when you have no lights configured in the Elk. You can safely ignore until I can get a new rele out.

Sent from my Pixel 6 Pro using Tapatalk