ralbright Posted February 21, 2018 Posted February 21, 2018 Just want to make sure that I am not blasting data TOO quickly to my ISY from the NodeLink and GEM. Currently the GEM is set to send data packets every 5 seconds, The NodeLink server shows timeouts at 10 seconds. I just do not want to cause the ISY to get TOO busy from the NodeLink GEM connection to be able to process sensor inputs from other REST API components (such as Elk, CAO Wireless Tags, etc.)
io_guy Posted February 21, 2018 Posted February 21, 2018 I use 15s, can't really tell you what too much is, it's a question for UDI.
larryllix Posted February 21, 2018 Posted February 21, 2018 Just want to make sure that I am not blasting data TOO quickly to my ISY from the NodeLink and GEM. Currently the GEM is set to send data packets every 5 seconds, The NodeLink server shows timeouts at 10 seconds. I just do not want to cause the ISY to get TOO busy from the NodeLink GEM connection to be able to process sensor inputs from other REST API components (such as Elk, CAO Wireless Tags, etc.) My guess is that the ISY cpu can handle it no problem. The same problem comes in to a lesser degree than Insteon though. If you are going to bombard the Ethernet port with a few more devices with that speed you may start to get some drag when you operate devices via the same port for HA purposes.I have heard the RPi Ethernet port is a downstream hardware connection on the shared USB bus and probably easy to bog down. Sent from my SM-G930W8 using Tapatalk
Recommended Posts
Archived
This topic is now archived and is closed to further replies.