What are you running Homeseer 3 on?
I have a program written by a Cocoontech forum user / plugin which originally was written to test the Omni Pro network communications and fix the time when it went off.
The program has evolved now to integrate with the Samsung hub. That said you do not need enable the Samsung hub piece.
This program will run in a command line terminal session in Windows or similarly using Mono in Linux.
You can run it on your HS3 box to see if there are network issues.
I would suggest to give it a try.
The fix for the panel communications error only worked by disconnecting the network port or connecting one port to the LAN side of a router and then using the WAN port on the router to the rest of your network. It did not work for me trying an old 10Mb hub or using VLANs.
It doesn't sound like you have a lot of devices on your network any how. Here only saw problem after some 50 network devices. Never saw the problem with the second OmniPro 2 panel that I had configured with a much smaller network (< 10 devices).
Read here about the HAI Logger program. ===> HAI Logger
Personally here running it on the Zee-2 box along with HS3 and Rob's HAI plugin.
Here what it looks like running. You can leave the terminal window open to watch it.
mono HAILogger.exe -i
INFO: CoreServer: Starting up server 1.0.8.0
INFO: CoreServer: CONNECTION STATUS: Connecting
INFO: CoreServer: CONTROLLER IS: OmniPro II (4.0B)
INFO: CoreServer: Retrieving named units
INFO: CoreServer: Unsolicited notifications enabled
VERBOSE: ThermostatTimer: Added to watch list Thermostat 1
I have a program written by a Cocoontech forum user / plugin which originally was written to test the Omni Pro network communications and fix the time when it went off.
The program has evolved now to integrate with the Samsung hub. That said you do not need enable the Samsung hub piece.
This program will run in a command line terminal session in Windows or similarly using Mono in Linux.
You can run it on your HS3 box to see if there are network issues.
I would suggest to give it a try.
The fix for the panel communications error only worked by disconnecting the network port or connecting one port to the LAN side of a router and then using the WAN port on the router to the rest of your network. It did not work for me trying an old 10Mb hub or using VLANs.
It doesn't sound like you have a lot of devices on your network any how. Here only saw problem after some 50 network devices. Never saw the problem with the second OmniPro 2 panel that I had configured with a much smaller network (< 10 devices).
Read here about the HAI Logger program. ===> HAI Logger
Personally here running it on the Zee-2 box along with HS3 and Rob's HAI plugin.
Here what it looks like running. You can leave the terminal window open to watch it.
mono HAILogger.exe -i
INFO: CoreServer: Starting up server 1.0.8.0
INFO: CoreServer: CONNECTION STATUS: Connecting
INFO: CoreServer: CONTROLLER IS: OmniPro II (4.0B)
INFO: CoreServer: Retrieving named units
INFO: CoreServer: Unsolicited notifications enabled
VERBOSE: ThermostatTimer: Added to watch list Thermostat 1
Comment