Through the help of this board, I was able to successful setup a Superbus 2000 Automation module to work with HomeSeer. I used a StarTech RS232 serial to UP converter.
It generally works, but maybe once a week or so, I'll get an AM Bus Failure on the Concord Keypad. When I go to HomeSeer, the Concord PI will say "Connected to Concord4" but when I go to the Control pad and try to use the Virtual Keypad, I will get an error that it's not connected. Usually some combination of plugging and unplugging the StarTech and reconnecting in the PI will fix it. And yes, I have "Start with HS" enabled.
We usually just arm and disarm the keypad manually. My thought is that the AM module may go days without communication from HS and then just drops the connection.
Any ideas? Should I create some kind of recurring event that forces comms between HS and the Concord panel? Is there something else I could try. Any help is appreciated.
It generally works, but maybe once a week or so, I'll get an AM Bus Failure on the Concord Keypad. When I go to HomeSeer, the Concord PI will say "Connected to Concord4" but when I go to the Control pad and try to use the Virtual Keypad, I will get an error that it's not connected. Usually some combination of plugging and unplugging the StarTech and reconnecting in the PI will fix it. And yes, I have "Start with HS" enabled.
We usually just arm and disarm the keypad manually. My thought is that the AM module may go days without communication from HS and then just drops the connection.
Any ideas? Should I create some kind of recurring event that forces comms between HS and the Concord panel? Is there something else I could try. Any help is appreciated.
Comment