<?xml version="1.0"?>
<rss version="2.0"><channel><title>EnvisaLink-HW Latest Topics</title><link>https://forum.universal-devices.com/forum/390-envisalink-hw/</link><description>EnvisaLink-HW Latest Topics</description><language>en</language><item><title>Unhandled Command?</title><link>https://forum.universal-devices.com/topic/43717-unhandled-command/</link><description><![CDATA[<p>
	 
</p>

<p>
	This keeps showing up.  Pages in the logs.  ALl the same over and over.
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	2024-06-14 16:52:56,389 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 16:55:34,722 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 16:57:50,010 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 16:58:05,789 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:03:21,905 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:08:10,561 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:10:58,818 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:13:33,836 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:17:08,658 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:22:52,618 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:24:50,131 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:25:06,856 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:27:06,954 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:27:21,644 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:27:29,399 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:37:02,256 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:38:02,070 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:39:49,619 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:39:57,063 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:41:29,992 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 17:51:24,274 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:54:43,116 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 17:56:10,895 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 18:03:55,148 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:07:40,015 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:08:07,554 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:09:12,379 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:11:01,217 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:11:08,217 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 18:14:12,274 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:14:13,404 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 18:15:54,213 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:15:59,093 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 18:17:38,721 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 18:18:48,235 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 18:21:43,713 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:23:08,586 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 18:31:52,539 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9<br />
	2024-06-14 18:35:58,470 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:36:07,595 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:38:41,943 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:40:19,017 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5<br />
	2024-06-14 18:44:58,403 Thread-6277 (_command_listener) udi_interface      WARNING  nodes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9
</p>
]]></description><guid isPermaLink="false">43717</guid><pubDate>Fri, 14 Jun 2024 23:47:18 +0000</pubDate></item><item><title>Only seeing zones 1-8</title><link>https://forum.universal-devices.com/topic/43525-only-seeing-zones-1-8/</link><description><![CDATA[<p>
	Let me start by saying that this was working perfectly. I'm not sure exactly when this stopped, but I noticed today that the plug-in is only seeing Zones 1-8 and not 9-16. When I look at the Nodes on the PG3 page 9-16 are not listed or included. It used to show 1-16. Obviously they are not showing up in the IoX Admin Console either. I deleted the plug in and installed into a different slot and got the same results.
</p>

<p>
	On the PG3 page, it is showing 10 nodes:
</p>

<p>
	Node1 = Alarm Panel
</p>

<p>
	Node2 = partition 1
</p>

<p>
	Node3 - Node10 = Zone 1 to Zone 8
</p>

<p>
	But yet when I log directly into the EvisaLink I see 16 zones and it tells me if open or how long closed.
</p>

<p>
	I have not changed any of the settings since I got it working several months ago. Could a recent PG3 or IoX update be the culprit? 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">43525</guid><pubDate>Wed, 01 May 2024 19:25:40 +0000</pubDate></item><item><title>Node Server Requires Frequent Restart (eisy v5.8.0)</title><link>https://forum.universal-devices.com/topic/43097-node-server-requires-frequent-restart-eisy-v580/</link><description><![CDATA[<p>
	First, I love this node server when it is working.  I am using a HW Vista Panel with 24 zones and 1 partition. When first started the panel and all 24 zones report correct status and update status in a timely manner.  My system has 5 motion detectors. After some random number of hours (less than a day), the motion detectors stop updating their status and remain showing an "open" condition. Occasionally, an exit door status will freeze reporting an "open" state despite being closed.  The node server partition status reports "not ready" when any of the zones report an "open" condition.  The panel console, Eon App, and Total Connect all show the panel status to be "ready"  Restarting the node server clears this condition and we start fresh.
</p>

<p>
	My suspicion is that the frequency of Motion triggers and potential overlap with processing zone updates is causing the issue. I believe that Total Connect and Eon do not use motion zones to determine whether the panel can respond to commands. The Eon App shows motion detectors to be open for a long time following a trigger.
</p>

<p>
	Any help with this issue will be greatly appreciated.  Thanks in advance....
</p>
]]></description><guid isPermaLink="false">43097</guid><pubDate>Tue, 13 Feb 2024 17:32:57 +0000</pubDate></item><item><title>EnvisaLink-HW PG3 Node Server Released</title><link>https://forum.universal-devices.com/topic/38593-envisalink-hw-pg3-node-server-released/</link><description><![CDATA[<p>
	I have released the PG3 version of the EnvisaLink-HW Node server (v3.0.3).
</p>

<p>
	The EnvisaLink-HW node server provides an interface for the ISY to a Honeywell/Ademco Vista series alarm panel through EnvisaLink™ EVL-3/4 and DUO™ adapters from EyezOn. See http://www.eyezon.com/ for more information on these products.
</p>

<p>
	Installation instructions, release notes, and version history can be found here: <a href="https://github.com/Goose66/NSDocs/blob/main/evlvista-pg3.md" rel="external nofollow">https://github.com/Goose66/NSDocs/blob/main/evlvista-pg3.md</a>.
</p>

<p>
	There is a 1-month trial period and then the node server is a one-time purchase at $10.95.
</p>
]]></description><guid isPermaLink="false">38593</guid><pubDate>Thu, 29 Sep 2022 21:55:06 +0000</pubDate></item><item><title>Cannot get my panel to connect</title><link>https://forum.universal-devices.com/topic/40952-cannot-get-my-panel-to-connect/</link><description><![CDATA[<p>
	I have input the IP address of my envisalink and tested with the web logon as well as with fing program.  Pinged the IP with perfect results.  I have used the correct password (tested with web logon as well).  I have also put in the correct user code.  Is there anything I may have missed.  Have tried numerous times and still nothing.  
</p>

<p>
	Thanks in advance for your time!
</p>

<p>
	Dave
</p>
]]></description><guid isPermaLink="false">40952</guid><pubDate>Thu, 06 Apr 2023 16:48:56 +0000</pubDate></item><item><title>cant connect to envisalink at ip address</title><link>https://forum.universal-devices.com/topic/40222-cant-connect-to-envisalink-at-ip-address/</link><description><![CDATA[<p>
	I installed Envisalink HW last Saturday on PG3   everything worked flawlessly.
</p>

<p>
	Yesterday the PG3 Node Server threw a cant connect to envisalink at 192.168.1.155 (the reserved address)
</p>

<p>
	I can ping it, and I can login to it at that address with browser / password is default
</p>

<p>
	Tried removing the Node Server and re-installing, same failure
</p>

<p>
	I can see alarm from the app
</p>

<p>
	It may have been when I upgraded to 5.5.5 on IOX Polisy with Zmatter
</p>

<p>
	Any other ideas ??
</p>

<p>
	log attached
</p>

<p>
	...Barry
</p>

<p>
	 
</p>
<p>
<a class="ipsAttachLink" href="https://forum.universal-devices.com/applications/core/interface/file/attachment.php?id=24573&amp;key=339f4c65d690f4903700858a255d9ba8" data-fileExt='zip' data-fileid='24573' data-filekey='339f4c65d690f4903700858a255d9ba8'>EnvisaLink-HW_2-7-2023_35933-PM.zip</a></p>]]></description><guid isPermaLink="false">40222</guid><pubDate>Tue, 07 Feb 2023 23:02:16 +0000</pubDate></item><item><title>PG 3.1.13 update today killed things</title><link>https://forum.universal-devices.com/topic/38924-pg-3113-update-today-killed-things/</link><description><![CDATA[<p>
	Was running 3.1.12   30 min ago and about an hour ago I had an alarm and it shows up in logs.
</p>

<p>
	I updated PG3 and rebooted it and all node servers working but this one.
</p>

<p>
	It says connected (And I have restarted it) but this is all I get in the log (xxxx for passwords but they are correct and I did not change them)
</p>

<p>
	and then the log stops and nothing else happens.
</p>

<p>
	in ISY it says Unknown/Not in User for my partition
</p>

<pre style="height:96%;">2022-11-03 13:58:59,302 MainThread udi_interface      INFO     polylogger:set_basic_config: set_basic_config: enable=True level=30
2022-11-03 13:59:01,932 MainThread udi_interface      INFO     __init__:&lt;module&gt;: UDI Python Interface for Polyglot version 3 3.0.49 Starting...
2022-11-03 13:59:01,941 MainThread udi_interface.interface INFO     interface:__init__: Initialization received from Polyglot V3 3.1.13  [ISY: 5.4.4, Slot: 2]
2022-11-03 13:59:01,943 MainThread udi_interface.interface INFO     interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'}
2022-11-03 13:59:01,944 Interface  udi_interface.interface INFO     interface:_startMqtt: Connecting to MQTT... localhost:1888
2022-11-03 13:59:01,947 MainThread udi_interface.interface WARNING  interface:_get_server_data: get_server_data: failed to read file server.json: [Errno 2] No such file or directory: 'server.json'
Traceback (most recent call last):
  File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 537, in _get_server_data
    with open(Interface.SERVER_JSON_FILE_NAME) as data:
FileNotFoundError: [Errno 2] No such file or directory: 'server.json'
2022-11-03 13:59:01,952 MainThread udi_interface      INFO     evlvistans:&lt;module&gt;: Starting EnvisaLink-HW node server...
2022-11-03 13:59:01,954 MainThread udi_interface.interface WARNING  interface:send: MQTT Send waiting on connection :: {'config': {'version': '3.0.3'}}
2022-11-03 13:59:02,001 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with result code 0 (Success)
2022-11-03 13:59:02,002 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_2 -  MID: 1 Result: 0
2022-11-03 13:59:02,013 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,)
2022-11-03 13:59:05,146 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message getAll
2022-11-03 13:59:05,148 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING getAll
2022-11-03 13:59:05,150 Thread-2   udi_interface.custom DEBUG    custom:load: CUSTOM: load {'hostname': '172.16.1.211', 'password': 'xxxxx', 'usercode': 'xxxx', 'numzones': '43', 'smartzonetracking': '1'}
2022-11-03 13:59:05,151 Command    udi_interface.custom DEBUG    custom:load: CUSTOM: load {}
2022-11-03 13:59:05,152 Thread-2   udi_interface.custom DEBUG    custom:load: CUSTOM:  -- checking hostname / 172.16.1.211
2022-11-03 13:59:05,154 Command    udi_interface.interface DEBUG    interface:_handleInput: Key nsdata should be passed to node server.
2022-11-03 13:59:05,155 Thread-2   udi_interface.custom DEBUG    custom:load: CUSTOM:  -- checking password / user
2022-11-03 13:59:05,158 Command    udi_interface.interface DEBUG    interface:_handleInput: Key oauth should be passed to node server.
2022-11-03 13:59:05,159 Thread-2   udi_interface.custom DEBUG    custom:load: CUSTOM:  -- checking usercode / 1226
2022-11-03 13:59:05,165 Thread-2   udi_interface.custom DEBUG    custom:load: CUSTOM:  -- checking numzones / 43
2022-11-03 13:59:05,165 Thread-2   udi_interface.custom DEBUG    custom:load: CUSTOM:  -- checking smartzonetracking / 1
2022-11-03 13:59:05,185 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message getNsInfo
2022-11-03 13:59:05,187 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING getNsInfo
2022-11-03 13:59:05,206 MainThread udi_interface.interface DEBUG    interface:setCustomParamsDoc: Sending customparamsdoc to Polyglot.
2022-11-03 13:59:05,207 MainThread udi_interface.interface DEBUG    interface:send: PUBLISHING {'set': [{'key': 'customparamsdoc', 'value': '&lt;h2&gt;EnvisaLink Vista Node server Configuration&lt;/h2&gt;\n\n&lt;h3&gt;Advanced Configuration:&lt;/h3&gt;\n\n&lt;ul&gt;\n&lt;li&gt;key: shortPoll, value: polling interval for connection status of Envisalink and zone timers (defaults to 30 seconds)&lt;/li&gt;\n&lt;li&gt;key: longPoll, value: interval for watchdog timer resets if watchdog timer is disabled (see below, defaults to 600 seconds)&lt;/li&gt;\n&lt;/ul&gt;\n\n&lt;p&gt;NOTE: The alarm panel reports zone and partition status changes immediately and other state changes are reported in keypad updates every 4 or 5 seconds, so frequent polling for state in shortpoll is not required. longpoll needs to be less than 20 minutes to prevent EnvisaLink from rebooting.&lt;/p&gt;\n\n&lt;h3&gt;Custom Configuration Parameters:&lt;/h3&gt;\n\n&lt;h4&gt;Required:&lt;/h4&gt;\n\n&lt;ul&gt;\n&lt;li&gt;key: hostname, value: locally accessible hostname or IP address of EnvisaLink or DUO device (e.g., "envisalink.local" or "192.168.1.145")&lt;/li&gt;\n&lt;li&gt;key: password, value: password for EnvisaLink device&lt;/li&gt;\n&lt;li&gt;key: usercode, value: user code for disarming alarm panel (e.g., "5555")&lt;/li&gt;\n&lt;/ul&gt;\n\n&lt;h4&gt;Optional:&lt;/h4&gt;\n\n&lt;ul&gt;\n&lt;li&gt;key: numpartitions, value: number of partition nodes to generate (defaults to 1)&lt;/li&gt;\n&lt;li&gt;key: numzones, value: number of zone nodes to generate (defaults to 8)&lt;/li&gt;\n&lt;li&gt;key: disablewatchdog, value: 0 or 1 for whether EyezOn cloud service watchdog timer should be disabled (defaults to 0 - not disabled)&lt;/li&gt;\n&lt;li&gt;key: zonetimerdumpflag, value: numeric flag indicating whether dumping of the zone timers should be done on shortpoll (1), longpoll (2), or disabled altogether (0) (defaults to 1 - shortpoll)&lt;/li&gt;\n&lt;li&gt;key: smartzonetracking, value: 0 or 1 for whether Node server should use a heuristic to track zone status (open, closed) or just rely on EnvisaLink\'s zone status reporting (defaults to 0 - do not track)&lt;/li&gt;\n&lt;/ul&gt;\n\n&lt;p&gt;NOTE: On Node server start, the child nodes for the Alarm Panel are created based on the numbers configured. The disablewatchdog should be enabled if the EnvisaLink is firewalled to prevent the EnvsiaLink from rebooting after 20 minutes.&lt;/p&gt;\n'}]}
2022-11-03 13:59:05,209 MainThread udi_interface.interface INFO     interface:updateProfile: Sending Install Profile command to Polyglot.
2022-11-03 13:59:05,210 MainThread udi_interface.interface DEBUG    interface:send: PUBLISHING {'installprofile': {'reboot': False}}
2022-11-03 13:59:05,251 MQTT       udi_interface.interface INFO     interface:_message: custom data response {'customparamsdoc': '&lt;h2&gt;EnvisaLink Vista Node server Configuration&lt;/h2&gt;\n\n&lt;h3&gt;Advanced Configuration:&lt;/h3&gt;\n\n&lt;ul&gt;\n&lt;li&gt;key: shortPoll, value: polling interval for connection status of Envisalink and zone timers (defaults to 30 seconds)&lt;/li&gt;\n&lt;li&gt;key: longPoll, value: interval for watchdog timer resets if watchdog timer is disabled (see below, defaults to 600 seconds)&lt;/li&gt;\n&lt;/ul&gt;\n\n&lt;p&gt;NOTE: The alarm panel reports zone and partition status changes immediately and other state changes are reported in keypad updates every 4 or 5 seconds, so frequent polling for state in shortpoll is not required. longpoll needs to be less than 20 minutes to prevent EnvisaLink from rebooting.&lt;/p&gt;\n\n&lt;h3&gt;Custom Configuration Parameters:&lt;/h3&gt;\n\n&lt;h4&gt;Required:&lt;/h4&gt;\n\n&lt;ul&gt;\n&lt;li&gt;key: hostname, value: locally accessible hostname or IP address of EnvisaLink or DUO device (e.g., "envisalink.local" or "192.168.1.145")&lt;/li&gt;\n&lt;li&gt;key: password, value: password for EnvisaLink device&lt;/li&gt;\n&lt;li&gt;key: usercode, value: user code for disarming alarm panel (e.g., "5555")&lt;/li&gt;\n&lt;/ul&gt;\n\n&lt;h4&gt;Optional:&lt;/h4&gt;\n\n&lt;ul&gt;\n&lt;li&gt;key: numpartitions, value: number of partition nodes to generate (defaults to 1)&lt;/li&gt;\n&lt;li&gt;key: numzones, value: number of zone nodes to generate (defaults to 8)&lt;/li&gt;\n&lt;li&gt;key: disablewatchdog, value: 0 or 1 for whether EyezOn cloud service watchdog timer should be disabled (defaults to 0 - not disabled)&lt;/li&gt;\n&lt;li&gt;key: zonetimerdumpflag, value: numeric flag indicating whether dumping of the zone timers should be done on shortpoll (1), longpoll (2), or disabled altogether (0) (defaults to 1 - shortpoll)&lt;/li&gt;\n&lt;li&gt;key: smartzonetracking, value: 0 or 1 for whether Node server should use a heuristic to track zone status (open, closed) or just rely on EnvisaLink\'s zone status reporting (defaults to 0 - do not track)&lt;/li&gt;\n&lt;/ul&gt;\n\n&lt;p&gt;NOTE: On Node server start, the child nodes for the Alarm Panel are created based on the numbers configured. The disablewatchdog should be enabled if the EnvisaLink is firewalled to prevent the EnvsiaLink from rebooting after 20 minutes.&lt;/p&gt;\n'}
2022-11-03 13:59:05,271 Thread-7   udi_interface      DEBUG    classes:start: In start()...
2022-11-03 13:59:05,293 MQTT       udi_interface.interface INFO     interface:_message: Successfully set key = customparamsdoc
2022-11-03 13:59:05,706 MQTT       udi_interface.interface INFO     interface:_message: Profile installation finished</pre>
]]></description><guid isPermaLink="false">38924</guid><pubDate>Thu, 03 Nov 2022 18:07:11 +0000</pubDate></item><item><title>Unhandled Commands?</title><link>https://forum.universal-devices.com/topic/38634-unhandled-commands/</link><description><![CDATA[<p>
	I am seeing unhandled command in the log.....
</p>

<pre style="height:96%;">2022-10-03 21:31:12,112 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 17715 UOM 58
2022-10-03 21:34:30,788 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5
2022-10-03 21:35:55,889 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5
2022-10-03 21:36:11,000 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone02 :: GV1 to 103790 UOM 58
2022-10-03 21:36:11,184 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone03 :: GV1 to 15 UOM 58
2022-10-03 21:36:11,224 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone04 :: GV1 to 16960 UOM 58
2022-10-03 21:36:11,358 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone05 :: GV1 to 4010 UOM 58
2022-10-03 21:36:11,460 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone06 :: GV1 to 8465 UOM 58
2022-10-03 21:36:11,563 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: GV1 to 2525 UOM 58
2022-10-03 21:36:11,663 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone08 :: GV1 to 93805 UOM 58
2022-10-03 21:36:11,760 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone09 :: GV1 to 27255 UOM 58
2022-10-03 21:36:11,855 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone12 :: GV1 to 97690 UOM 58
2022-10-03 21:36:11,957 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone14 :: GV1 to 4095 UOM 58
2022-10-03 21:36:12,062 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone18 :: GV1 to 38620 UOM 58
2022-10-03 21:36:12,162 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone21 :: GV1 to 99860 UOM 58
2022-10-03 21:36:12,260 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 18015 UOM 58
2022-10-03 21:40:20,149 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9
2022-10-03 21:41:10,980 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone02 :: GV1 to 104090 UOM 58
2022-10-03 21:41:11,122 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone03 :: GV1 to 5 UOM 58
2022-10-03 21:41:11,205 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone04 :: GV1 to 17260 UOM 58
2022-10-03 21:41:11,296 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone05 :: GV1 to 4310 UOM 58
2022-10-03 21:41:11,398 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone06 :: GV1 to 8765 UOM 58
2022-10-03 21:41:11,500 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: GV1 to 2825 UOM 58
2022-10-03 21:41:11,594 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone08 :: GV1 to 94105 UOM 58
2022-10-03 21:41:11,699 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone09 :: GV1 to 27555 UOM 58
2022-10-03 21:41:11,801 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone12 :: GV1 to 97990 UOM 58
2022-10-03 21:41:11,898 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone14 :: GV1 to 4395 UOM 58
2022-10-03 21:41:11,998 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone18 :: GV1 to 38920 UOM 58
2022-10-03 21:41:12,100 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone21 :: GV1 to 100160 UOM 58
2022-10-03 21:41:12,196 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 18315 UOM 58
2022-10-03 21:46:11,007 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone02 :: GV1 to 104390 UOM 58
2022-10-03 21:46:11,351 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone03 :: GV1 to 10 UOM 58
2022-10-03 21:46:11,465 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone04 :: GV1 to 17560 UOM 58
2022-10-03 21:46:11,508 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone05 :: GV1 to 4610 UOM 58
2022-10-03 21:46:11,548 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone06 :: GV1 to 9065 UOM 58
2022-10-03 21:46:11,550 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: GV1 to 3125 UOM 58
2022-10-03 21:46:11,638 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone08 :: GV1 to 94405 UOM 58
2022-10-03 21:46:11,739 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone09 :: GV1 to 27855 UOM 58
2022-10-03 21:46:11,839 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone12 :: GV1 to 98290 UOM 58
2022-10-03 21:46:11,942 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone14 :: GV1 to 4695 UOM 58
2022-10-03 21:46:12,037 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone18 :: GV1 to 39220 UOM 58
2022-10-03 21:46:12,138 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone21 :: GV1 to 100460 UOM 58
2022-10-03 21:46:12,240 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 18615 UOM 58
2022-10-03 21:49:26,371 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5
2022-10-03 21:51:10,919 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone02 :: GV1 to 104690 UOM 58
2022-10-03 21:51:11,049 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone03 :: GV1 to 15 UOM 58
2022-10-03 21:51:11,148 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone04 :: GV1 to 17860 UOM 58
2022-10-03 21:51:11,233 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone05 :: GV1 to 4910 UOM 58
2022-10-03 21:51:11,316 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone06 :: GV1 to 9365 UOM 58
2022-10-03 21:51:11,489 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: GV1 to 3425 UOM 58
2022-10-03 21:51:11,531 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone08 :: GV1 to 94705 UOM 58
2022-10-03 21:51:11,632 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone09 :: GV1 to 28155 UOM 58
2022-10-03 21:51:11,734 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone12 :: GV1 to 98590 UOM 58
2022-10-03 21:51:11,834 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone14 :: GV1 to 4995 UOM 58
2022-10-03 21:51:11,937 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone18 :: GV1 to 39520 UOM 58
2022-10-03 21:51:12,036 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone21 :: GV1 to 100760 UOM 58
2022-10-03 21:51:12,134 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 18915 UOM 58
2022-10-03 21:56:10,936 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone02 :: GV1 to 104990 UOM 58
2022-10-03 21:56:11,056 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone03 :: GV1 to 20 UOM 58
2022-10-03 21:56:11,150 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone04 :: GV1 to 18160 UOM 58
2022-10-03 21:56:11,251 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone05 :: GV1 to 5210 UOM 58
2022-10-03 21:56:11,334 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone06 :: GV1 to 9665 UOM 58
2022-10-03 21:56:11,448 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: GV1 to 3725 UOM 58
2022-10-03 21:56:11,550 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone08 :: GV1 to 95005 UOM 58
2022-10-03 21:56:11,647 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone09 :: GV1 to 28455 UOM 58
2022-10-03 21:56:11,748 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone12 :: GV1 to 98890 UOM 58
2022-10-03 21:56:12,010 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone18 :: GV1 to 39820 UOM 58
2022-10-03 21:56:12,053 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone14 :: GV1 to 5295 UOM 58
2022-10-03 21:56:12,055 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone21 :: GV1 to 101060 UOM 58
2022-10-03 21:56:12,150 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 19215 UOM 58
2022-10-03 22:01:10,944 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone02 :: GV1 to 105290 UOM 58
2022-10-03 22:01:11,054 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone03 :: GV1 to 10 UOM 58
2022-10-03 22:01:11,160 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone04 :: GV1 to 18460 UOM 58
2022-10-03 22:01:11,248 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone05 :: GV1 to 5510 UOM 58
2022-10-03 22:01:11,350 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone06 :: GV1 to 9965 UOM 58
2022-10-03 22:01:11,450 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: GV1 to 4025 UOM 58
2022-10-03 22:01:11,550 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone08 :: GV1 to 95305 UOM 58
2022-10-03 22:01:11,655 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone09 :: GV1 to 28755 UOM 58
2022-10-03 22:01:11,747 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone12 :: GV1 to 99190 UOM 58
2022-10-03 22:01:11,847 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone14 :: GV1 to 5595 UOM 58
2022-10-03 22:01:11,947 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone18 :: GV1 to 40120 UOM 58
2022-10-03 22:01:12,052 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone21 :: GV1 to 101360 UOM 58
2022-10-03 22:01:12,151 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 19515 UOM 58
2022-10-03 22:01:44,683 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9
2022-10-03 22:05:52,439 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9
2022-10-03 22:06:10,935 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone02 :: GV1 to 105590 UOM 58
2022-10-03 22:06:11,106 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone04 :: GV1 to 18760 UOM 58
2022-10-03 22:06:11,148 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone05 :: GV1 to 5810 UOM 58
2022-10-03 22:06:11,287 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone06 :: GV1 to 10265 UOM 58
2022-10-03 22:06:11,369 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: GV1 to 4325 UOM 58
2022-10-03 22:06:11,486 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone08 :: GV1 to 95605 UOM 58
2022-10-03 22:06:11,588 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone09 :: GV1 to 29055 UOM 58
2022-10-03 22:06:11,686 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone12 :: GV1 to 99490 UOM 58
2022-10-03 22:06:11,783 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone14 :: GV1 to 5895 UOM 58
2022-10-03 22:06:11,883 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone18 :: GV1 to 40420 UOM 58
2022-10-03 22:06:11,986 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone21 :: GV1 to 101660 UOM 58
2022-10-03 22:06:12,089 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 19815 UOM 58
2022-10-03 22:10:34,574 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9
2022-10-03 22:11:10,938 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone02 :: GV1 to 105890 UOM 58
2022-10-03 22:11:11,118 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone03 :: GV1 to 15 UOM 58
2022-10-03 22:11:11,201 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone04 :: GV1 to 19060 UOM 58
2022-10-03 22:11:11,295 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone05 :: GV1 to 6110 UOM 58
2022-10-03 22:11:11,401 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone06 :: GV1 to 10565 UOM 58
2022-10-03 22:11:11,496 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: GV1 to 4625 UOM 58
2022-10-03 22:11:11,595 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone08 :: GV1 to 95905 UOM 58
2022-10-03 22:11:11,697 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone09 :: GV1 to 29355 UOM 58
2022-10-03 22:11:11,799 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone12 :: GV1 to 99790 UOM 58
2022-10-03 22:11:11,895 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone14 :: GV1 to 6195 UOM 58
2022-10-03 22:11:12,004 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone18 :: GV1 to 40720 UOM 58
2022-10-03 22:11:12,097 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone21 :: GV1 to 101960 UOM 58
2022-10-03 22:11:12,195 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone24 :: GV1 to 20115 UOM 58
2022-10-03 22:12:35,954 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9
2022-10-03 22:12:36,509 Thread-101 udi_interface      INFO     classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5
2022-10-03 22:12:44,225 MQTT       udi_interface.interface INFO     interface:_message: Successfully set zone07 :: ST to 1 UOM 25</pre>
]]></description><guid isPermaLink="false">38634</guid><pubDate>Tue, 04 Oct 2022 02:24:06 +0000</pubDate></item></channel></rss>
