Should I move to the xap.net plugin?

[Steve Q]

My mcsxapdevices.ini file still contains the definitions for the devices. They also appear in mcsxap.mdb file. The mcsxapdevices.ini appears to be in use because it is dated 10/11/07 (The last time I restarted Homeseer). Maybe this is why the "defined more than once" message is being generated.

As long as xap.net is continuing work, I am going to leave things alone.

Let me know if I can help you test any future versions.

Steve Q

[Steve Q]

As an update, and to close out this thread, since I upgraded to the most recent version of xapmcs1wire.exe, I have not had any problems with the mcsxAP.net version. Things have been running smoothly for 3 weeks.

Steve Q

[Steve Q]

Michael,

I guess I jinxed myself because now some of my devices are working, some are not?

On my 1 wire network I have 7 devices; 4 relays (the Hobby board 4 channel relay board) and 3 DS2405 switches connected as magnetic door contact closures. The 4 relays are working and responding to Homeseer commands; the 3 switches are invisible to Homeseer. All of the devices are showing up in xAP viewer and On/Off events are occuring. So for some reason Homeseer has become deaf to the switches. I will restart and run for a few more days to see if this might have been related to router problems I was having about the time things stopped.

Steve Q

[Steve Q]

Just for the record, mcsXAP.net is working great. I have had 2 consecutive periods where I ran for 5-6 days with not problems. I rebooted 5 days ago after installation of some new media software.

Steve Q

[Michael McSharry]

Through all of this investigation of why it stops I was able to only find one thing as the cause of messages to be stopped in the outbound direction. A variety of preventative guesses for everything else. To my knowledge Bill Dickhaus is the only one where a message lockup occurs and in his case it cannot be overcome programatically other than a restart. It looked as if his issue may have been related to spyware removal tools.