New Firmware 3.10A old comm/time problems back

[pete_c]

Very nice rsw686! What are you doing with your HAI logger relating to your home automation setup?

Here (sometimes low on the WAF) I have a bit of a sandbox always playing relating to see if I could do this or that. (WAF low this morning at 4 with some nightstand touchscreen activities wake up stuff happening and explaining the why part of it).

Hence lately trying to figure out how to utilize the DECT Voip and Zigbee interface on the latest little box (trying to make it a sort of Fritz box)....(really don't need to add to my hodgepodge of UPB, X10, Z-Wave and Insteon stuff lately)...

BTW I have not seen any time sync corrections in your HAI logger console since my issue went away yesterday.

 

[pete_c]

rsw686,

Never set up the HAILogger as a service and gave it a try today.

I see the following error after putting in a username/password.

An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The account name is invalid or does not exist, or the password is invalid for the account name specified
The installation failed, and the rollback has been performed.
C:\HAILogger>

changed login to ".\" Username and it worked.

InstallUtil /LogToConsole=true HAILoggerService.exe
The Install phase completed successfully, and the Commit phase is beginning.
See the contents of the log file for the C:\HAILogger\HAILoggerService.exe assem
bly's progress.
The file is located at C:\HAILogger\HAILoggerService.InstallLog.
Committing assembly 'C:\HAILogger\HAILoggerService.exe'.
Affected parameters are:
logtoconsole = true
assemblypath = C:\HAILogger\HAILoggerService.exe
logfile = C:\HAILogger\HAILoggerService.InstallLog

The Commit phase completed successfully.

The transacted install has completed.

 

[rsw686]

The username password is what account Windows will run the service as. Verify the username/password combination is valid to log into the computer with as the log shows "System.ComponentModel.Win32Exception: The account name is invalid or does not exist, or the password is invalid for the account name specified".

I have a new version that fixes a few bugs, allows testing without logging to the database, and control of the verbose output.

http://www.excaliburtech.net/downloads/HAILogger_1_0_3.zip

 

[rsw686]

Very nice rsw686! What are you doing with your HAI logger relating to your home automation setup?

Here (sometimes low on the WAF) I have a bit of a sandbox always playing relating to see if I could do this or that. (WAF low this morning at 4 with some nightstand touchscreen activities wake up stuff happening and explaining the why part of it).

Hence lately trying to figure out how to utilize the DECT Voip and Zigbee interface on the latest little box (trying to make it a sort of Fritz box)....(really don't need to add to my hodgepodge of UPB, X10, Z-Wave and Insteon stuff lately)...

BTW I have not seen any time sync corrections in your HAI logger console since my issue went away yesterday.

I originally built the logger so I could receive email notifications when an alarm went off, etc. Right now I'm not doing anything with the data. I need to build a web based graph interface for the thermostat data. Long term it would be neat to play back last weeks lighting events when the controller is armed to vacation mode. Right now I have some rules in the controller, but they don't give same lived in effect.

Glad to hear the time issue has gone away for the time being!

 

[pete_c]

Thank you rsw686. I have not seen the timing issue nor the thermostat communications issue.

Updated logger to current version.

I see this in the output and do not understand what it means.

VERBOSE: SystemEvent: Unhandled Raw: 55 253 40 Num: 64808
VERBOSE: SystemEvent: Unhandled: 253 40: 11111101 00101000

Can I set up a second instance of the application in a different directory or is it better to install it on a different computer talking to another OPII?

How would the time sync work in a different time zone?

 

[rsw686]

You can run multiple instances of the logger on the same computer from different directories. I ignore the time zone of the controller and computer. If the time is 8:00pm on the computer I set the controller to 8:00pm. Are you trying to set time on a controller in a different time zone than the computer?

VERBOSE: SystemEvent: Unhandled Raw: 55 253 40 Num: 64808
VERBOSE: SystemEvent: Unhandled: 253 40: 11111101 00101000

I started to add support for system events. Right now I only have ac power off / recovery, battery low / ok, and dcm trouble / ok. The unhanded event quoted above is UPB link 40 being activated. The OmniLink II Protocol PDF is needed to decode the binary.

 

[rsw686]

To do the timezone support correctly I would need to bump the minimum to .NET 3.5 which has a TimeZoneInfo class. Without that support I would need to assume daylight savings is the same for the computer and controller location. By ignoring daylight savings it is simple math using the time zone stored in the controller.

 

[pete_c]

Are you trying to set time on a controller in a different time zone than the computer?

Just experimenting crossing over a time zone (CST versus EST) via a WAN connection to another OPII using a direct and indirect connection.

Relating to the switching over to battery with a power failure; I could never catch the message generating via an event for the short power glitches I was having here in the midwest this past summer. Many of the power outages were less than a minute. I do notice though if I do a warm boot with the battery off it takes a few minutes to see any numbers relating to the battery after I set the time. Same with the telephone line stuff. (rarely seeing that though unless I remove the telephone line manually)

 

[pete_c]

rsw686,

Is your HAI panel keeping time well?

I've been watching mine and it appears to lose 4 seconds a day. I've been trying to adjust this with PCA going a little bit at a time and not seeing it change.

 

[rsw686]

Every 3-4 days it adjust the time by 10 seconds. So its off around 3 seconds per day. You would think the controller would be more accurate at keeping time.

 

[pete_c]

rsw686, thank-you. Here will continue to tweak to see if it changes anything.

 

[pete_c]

I had an unusal "thing" happen a couple of nights ago.  I went looking to modify some stuff via PCA and could not get to the panel.  I then noticed that nothing was working which was connected to the network interface (all of the Omnitouch 5.7e screens were sitting at the connecting prompt).
 
I disconnected the OPII network connection at the switch and reconnected it and all was fine again.
 
I did also update PCA and the OPII firmware to 3.11A (low WAF at 2 AM).  This was/is the first time I have every seen this.  The clock time was fine, serial to Omnitouch 5.7 screens was fine, thermostat was fine and events were triggering just fine.  It seemed just to be an issue with the network interface and devices on the network.

 

[pete_c]

Noticed the time on the OPII was off by about 1 hour tonight.  Omnitouch serial screens showed no ambient temperatures (as before) and network connectivity was poor both with PCA and Snaplink.
 
I was on Firmware 3.11B and went to firmware 3.11C tonight and upgraded the software.
 
I then disconnected ethernet cable.
 
Next morning checked Omnitouch screens.  Time is correct and thermostat temp is fine.
 
Connected nic back next day to see what happens.
 
Within 30 minutes it was 5 minutes off.  Using snaplink noticed a zero thermostat temperature and many timeouts and retries connecting.  It was very slow to load.
 
Disconnecting the NIC for the time being.  (losing my Omnitouch 5.7e connections).

 

[pete_c]

Plugged the network cable back in this morning and immediately saw comm issues on the serial ports via the thermostat to Omnitouch 5.7 screens. 
 
Noticed too that the network connectivity was not too good with disconnects and time out errors using both PCA and Snaplink. 
 
Disconnected the network cable. 
 
Today will power down the panel and restart and reconnect the network cable to see if the "issue" goes away.

 

[pete_c]

Leaving the NIC unplugged for 2 days appears to have fixed the "issue". 
 
Odd. 
 
Serial comm and network connectivity and time are OK.
 
Problem returned by night time with the time being off some 20 minutes and comm errors (thermostat) and network disconnects.
 
Disconnected the network connection last night again.