The unknown shutter status warning is a "feature" of the controller which I didn't expose before, it reports the shutter status as open/closed/unknown. Upon reboot it doesn't seem to know the status until an open or close command has been issued and completed. I'm not sure what I should do about it, but at least I can make it less spammy by not setting the state to the base class if it already is the same so it would trigger the print only once. But there also seems to be some bug in there as the status should be valid after you have opened and closed the shutter but the warning is still printed. From the log it seems the status numbers are incorrect in the documentation.
After opening:
DEBUG 127.478333 sec : GINF packet: V4,690,25,3,29,0, --> 0 <--,1,0,20,31,0,128,255,255,255,255,255,255,255,999,3,0
After closing:
DEBUG 1151.965279 sec : GINF packet: V4,690,25,3,25,0,--> 1 <--,1,0,20,31,0,128,255,255,255,255,255,255,255,999,3,0
but documentation says:
/* GINF packet structure:
Field Content Note (each datum is separated by comma)
1 V# Denotes Version Data. E.g., V1
2 Dticks DTICKS is dome circumference in ticks 0-32767. Value is sent as a string of characters, e.g., 457. Leading zeros not transmitted.
3 Home1 Azimuth location of the HOME position in ticks 0-32767
4 Coast Coast value in ticks (0-255)
5 ADAZ Current dome azimuth in Ticks 0-32767
6 Slave Slave Status 0=slave off 1=slave on
7 Shutter Shutter status 0=indeterminate, 1=closed, 2=open <---
8 DSR status DSR Status 0=indet, 1=closed, 2=open
9 Home Home sensor 0=home, 1=not home
10 HTICK_CCLK Azimuth ticks of counterclockwise edge of Home position
11 HTICK_CLK Azimuth ticks of clockwise edge of Home position
12 UPINS Status of all user digital output pins
13 WEAAGE Age of weather info in minutes 0 to 255 (255 means expired)
14 WINDDIR 0-255 wind direction (use (n/255)*359 to compute actual direction), subtract dome azimuth if weather module is mounted on dome top.
15 WINDSPD Windspeed 0-255 miles per hour
16 TEMP Temperature 0-255, representing -100 to 155 degrees F
17 HUMID Humidity 0-100% relative
18 WETNESS Wetness 0 (dry) to 100 (soaking wet)
19 SNOW Snow 0 (none) to 100 (sensor covered)
20 WIND PEAK Windspeed Peak level over session 0-255 miles per hour
21 SCOPEAZ Scope azimuth from LX-200 (999 if not available)
22 INTDZ Internal “deadzone”- angular displacement around the dome opening centerline within which desired dome azimuth can change without causing dome movement.
23 INTOFF Internal offset- angular distance DDW will add to the desired azimuth, causing the dome to preceed the telescope’s position when a slaved goto occurs.
24 car ret
25 car ret
*/
So I think I'll change that to match what the hardware actually sends instead.
Beeping I'm don't know anything about, haven't done anything to produce those or not, I just send commands 
As for slaving I'm not sure what the problem is as it seems to always calculate the scope azimuth as 0 in your log and thus not move anywhere:
DEBUG 247.678610 sec : JD: 2.45925e+06 - MSD: 11.4864
DEBUG 247.678695 sec : MC.x: 0 - MC.y: 0.07 MC.z: 0.34
DEBUG 247.678723 sec : HA: 6.00029 Lng: -107.985 RA: 334.307
DEBUG 247.678808 sec : OTA_SIDE: -1
DEBUG 247.678832 sec : OTA_OFFSET: 0.33 Lat: 32.4878
DEBUG 247.678852 sec : OC.x: -2.48124e-05 - OC.y: -0.10725 OC.z: 0.0616431
DEBUG 247.678874 sec : Mount Az: 0 Alt: 32.4878 <
DEBUG 247.678892 sec : OV.x: 0 - OV.y: 0.843506 OV.z: 0.53712
DEBUG 247.678917 sec : Calculated target azimuth is 360.00. MinAz: 336.84, MaxAz: 23.16
DEBUG 247.678938 sec : MoveAbs (359.998827)
INFO 247.678976 sec : Dome is moving to position 360.00 degrees azimuth...
DEBUG 247.679024 sec : Dome is syncing to position 360.00 degrees...
There aren't any snooping messages either so probably something to do with that or with slaving parameters. Also I didn't do any changes that would change these calculations lately (and they are made in the base class anyway).
Read More...