tibbar Posted April 21 Posted April 21 Could some one please shed some light on this traffic: Sat 04/20/2024 09:02:36 PM : [n007_keypad_1 ] GV10 0 Sat 04/20/2024 09:03:05 PM : [n007_keypad_1 ] GV10 0 Sat 04/20/2024 09:03:21 PM : [n008_setup ] DOF 0 Sat 04/20/2024 09:03:33 PM : [n007_keypad_1 ] GV10 0 Sat 04/20/2024 09:03:45 PM : [ Time] 21:04:07 0(0) Sat 04/20/2024 09:04:02 PM : [D2D EVENT ] Event [n007_keypad_1] [GV10] [0] uom=0 prec=-1 Sat 04/20/2024 09:04:02 PM : [n007_keypad_1 ] GV10 0 Sat 04/20/2024 09:04:15 PM : [ Time] 21:04:37 0(0) Sat 04/20/2024 09:04:31 PM : [D2D EVENT ] Event [n007_keypad_1] [GV10] [0] uom=0 prec=-1 Sat 04/20/2024 09:04:31 PM : [n007_keypad_1 ] GV10 0 Sat 04/20/2024 09:04:45 PM : [ Time] 21:05:07 0(0) Sat 04/20/2024 09:04:59 PM : [D2D EVENT ] Event [n007_keypad_1] [GV10] [0] uom=0 prec=-1 Sat 04/20/2024 09:04:59 PM : [n007_keypad_1 ] GV10 0 Sat 04/20/2024 09:05:04 PM : [D2D EVENT ] Event [n007_controller] [DOF] [0] uom=0 prec=-1 Sat 04/20/2024 09:05:04 PM : [n007_controller ] DOF 0 Sat 04/20/2024 09:05:09 PM : [D2D EVENT ] Event [n008_8b4c010007aa53] [CLITEMP] [-158] uom=4 prec=1 Sat 04/20/2024 09:05:09 PM : [n008_8b4c010007aa53] CLITEMP -158 (uom=4 prec=1) Sat 04/20/2024 09:05:09 PM : [D2D EVENT ] Event [n008_8b4c010007aa53] [CLIHUM] [548] uom=51 prec=1 Sat 04/20/2024 09:05:09 PM : [n008_8b4c010007aa53] CLIHUM 548 (uom=51 prec=1) n007 is Elk plugin and n008 is Yolink plugin. And here is a part from PG3 Elk log: val=0 force=False 2024-04-20 21:04:54,059 ELK-35682 udi_interface DEBUG BaseNode:set_driver: keypad_1:Keypad 01: GV3,0 default=None force=False,report=True 2024-04-20 21:04:54,059 ELK-35682 udi_interface DEBUG Keypad:send_driver: keypad_1:Keypad 01: reportCmd(GV10,1.2) 2024-04-20 21:04:54,065 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'command': [{'address': 'keypad_1', 'cmd': 'GV10', 'value': '1', 'uom': 2}]} 2024-04-20 21:04:54,092 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-04-20 21:04:54,092 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-04-20 21:04:54,092 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'keypad_1', 'success': True} from Polyglot 2024-04-20 21:04:58,216 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-04-20 21:04:58,216 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-04-20 21:04:58,216 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-04-20 21:04:58,217 Thread-448 udi_interface DEBUG Controller:handler_poll: start 2024-04-20 21:04:58,217 Thread-448 udi_interface DEBUG Controller:shortPoll: start 2024-04-20 21:04:58,217 Thread-448 udi_interface DEBUG Area:shortPoll: area_2:Area Bypass: ready=True poll_voltages=False 2024-04-20 21:04:58,217 Thread-448 udi_interface DEBUG Area:shortPoll: area_1:Area 1 Driv: ready=True poll_voltages=False 2024-04-20 21:04:58,217 Thread-448 udi_interface DEBUG Controller:shortPoll: done
Geddy Posted April 21 Posted April 21 13 hours ago, tibbar said: Could some one please shed some light on this traffic Maybe the wiki information would help: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Using_the_Event_Viewer Otherwise, what specific question do you have? Event viewer is usually only used in troubleshooting steps. Are you having other issues that you could describe and get help with? Or are you just generally inquiring about the event viewer information? 1
paulbates Posted April 21 Posted April 21 The pg3x plugins rely on short and long polling via message queues to communicate with devices/external services. The pg3x elk log looks like normal "respiration" of that activity to me. 1
Recommended Posts