Discussions related to HS3 build 3.0.0.368

[rjh]

Thread for discussing HS3 release 3.0.0.368

[ewkearns]

Not that it is a problem, but still not saying "Welcome to Homeseer....... Port 8#." It shows up in the speaker log, but doesn't talk to any other computer.... Otherwise, speech works fine....

[randy]

Not that it is a problem, but still not saying "Welcome to Homeseer....... Port 8#." It shows up in the speaker log, but doesn't talk to any other computer.... Otherwise, speech works fine....

It appears that the speaker remote clients are connecting a little more slowly since 3.0.0.332. The client on the HS server loads quickly and plays the TTS rom the startup script. The startup script may complete before the remote clients connect.

[happnatious1]

I'm going to have to try this version, I could never get mine to stop saying welcome to homeseer

[concordseer]

.368 downloaded and running. Nothing out of the ordinary to report. Running on Linux Raspbian on Raspberry Pi 3.

Here's to a final final.

[Pete]

Updated Homeseer Lite (Zee) to version .368.

Sep-25 3:44:08 PM Startup ************************************************************ ********************
Sep-25 3:44:08 PM Startup HomeSeer version 3.0.0.368 Edition: HS3 ZEE S2 Starting Now
Sep-25 3:44:08 PM Startup ************************************************************ ********************

Here noticed that start up script chit chat is not heard. Using Homeseer speaker on Wintel.

Sep-25 3:44:08 PM Startup HomeSeer version is: 3.0.0.368
Sep-25 3:44:08 PM Startup Creating Speaker Client Interface Object...
Sep-25 3:44:08 PM Startup This version of HomeSeer is registered as a HS3ZEES2 version.

Sep-25 3:44:18 PM Startup Initializing Speaker Client Interface
Sep-25 3:44:18 PM Speech Listening for remote speaker connections on port 10401
Sep-25 3:44:18 PM Startup Updater services starting...
Sep-25 3:44:18 PM Startup Starting Find service...
Sep-25 3:44:18 PM Startup Running the startup script Startup.vb

Sep-25 3:44:27 PM Speaker Speaker host added, Name: HS3W2003VB Instance: Default IP address: 10.0.2.15
Sep-25 3:44:35 PM Speaker Speaker host disconnected, Name: HS3W2003VB IP address: 10.0.2.15
Sep-25 3:44:35 PM ASR Speaker Client speech recognition stopped

Note this HS box doesn't have any HSTouch clients connected and only one Homeseer speaker connected. HSTouch is disabled on this box.

Tested manual speak event and it is working fine.

Looking at set up and it shows one speaker client connected.

Connected Speaker Clients
Speaker HS3W2003VB DEFAULT

[MarkHargrove]

I do not see a V.368 update yet for Homeseer Pro for Linux at this time.

hs3_linux_3_0_0_368.tar.gz is on the server.

Is there a separate tarball for the Pro version?

[Pete]

Thank you Mark. Same tarball for Standard and Pro.

Typo earlier as for whatever reason was trying to download V.168 instead of V.368

Sep-25 5:13:04 PM Startup ************************************************************ ********************
Sep-25 5:13:04 PM Startup HomeSeer version 3.0.0.368 Edition: HS3 Pro Starting Now
Sep-25 5:13:04 PM Startup ************************************************************ ********************

Start up script here did speak stuff fine.

Here is a snapshot of HTop a bit after starting HS3 Pro

[ATTACH]63537[/ATTACH]

[MarkHargrove]

CPU Loading on Linux Version of Recent Releases

Something has definitely changed on recent releases of HS3 for Linux. On 326 and earlier my RPI model 3 ran with steady-state load averages of < 1.0 and with CPU temps in the low-to-mid 50s. Average CPU% of the parent HSConsole.exe process was around 10-12% (it spiked from time to time, as you would expect, but that was the observable average).

Since 357 (including the most recent 368), load averages steadily creep up over a few hours to values in the 4 to 5 range, and the CPU temp climbs to thermal alarm levels over the same time (roughly 80 *C). After all startup processing is finished, CPU% of the parent HSConsole process shows on htop over 50% and slowly climbs to higher values. Within a few hours the CPU utilization will be at 90% and stays at roughly that value (which certainly explains the thermal issue).

From a plugins perspective, this is basically all "apples-to-apples" -- I'm running exactly the same set of plugins (and versions of those plugins) on 326 as on 368. The only reason I say 'basically the same' is that the HSTouch plugin is gone in 357 (and above) since it's in the core HS3 code now.

I realize that not everybody running HS3 is seeing this, but it's very consistent on my HS installation: 326 or lower, no issue; 357 or higher, big issue.

Any suggestions on troubleshooting to figure out what might be going on?

Thanks!

-M.

[rjh]

The "welcome to homeseer" text is generated in the startup.vb script. If you change the script, you may not hear it. Also, the script waits a short time for speaker clients to connect. If they take longer than this timeout to connect, the script exits. I suspect this is what you are seeing. You can edit the script and extend the timeout if you want to get it to speak on startup.

Not that it is a problem, but still not saying "Welcome to Homeseer....... Port 8#." It shows up in the speaker log, but doesn't talk to any other computer.... Otherwise, speech works fine....

[rjh]

Just edit the startup script if you don't want to hear it, or cjhange it something more interesting!

I'm going to have to try this version, I could never get mine to stop saying welcome to homeseer

[rjh]

HS3 configures itself to standard or pro based on your license, so no seperate tar file needed.

hs3_linux_3_0_0_368.tar.gz is on the server.

Is there a separate tarball for the Pro version?

[MarkHargrove]

Thank you Mark. Same tarball for Standard and Pro.

Typo earlier as for whatever reason was trying to download V.168 instead of V.368

Sep-25 5:13:04 PM Startup ************************************************************ ********************
Sep-25 5:13:04 PM Startup HomeSeer version 3.0.0.368 Edition: HS3 Pro Starting Now
Sep-25 5:13:04 PM Startup ************************************************************ ********************

Start up script here did speak stuff fine.

Here is a snapshot of HTop a bit after starting HS3 Pro

[ATTACH]63537[/ATTACH]

You're not running an ARM CPU are you? (or if you are, I'd like to know what it is since you have that much free memory!)

[rjh]

Odd, and correct, I don't see any high cpu on any of our test systems, windows or Linux. Any activity in the log? If you disable all your plugins, does it still happen?

There was a problem for sure with the betas where a thread was using CPU, but that has been removed in the latest.

The only change with the latest is the move of HSTouch into the main app. This moves some threads into HS, but they should be idle if no HSTouch clients are connected. Disconnect all your clients and see if the cpu changes.

My home system is Linux and I always have at least 2 clients connected. Just checked now and cpu was under 6%. This is on Raspberry PI 2. Z-Wave and Nest plugins enabled.

Something has definitely changed on recent releases of HS3 for Linux. On 326 and earlier my RPI model 3 ran with steady-state load averages of < 1.0 and with CPU temps in the low-to-mid 50s. Average CPU% of the parent HSConsole.exe process was around 10-12% (it spiked from time to time, as you would expect, but that was the observable average).

Since 357 (including the most recent 368), load averages steadily creep up over a few hours to values in the 4 to 5 range, and the CPU temp climbs to thermal alarm levels over the same time (roughly 80 *C). After all startup processing is finished, CPU% of the parent HSConsole process shows on htop over 50% and slowly climbs to higher values. Within a few hours the CPU utilization will be at 90% and stays at roughly that value (which certainly explains the thermal issue).

From a plugins perspective, this is basically all "apples-to-apples" -- I'm running exactly the same set of plugins (and versions of those plugins) on 326 as on 368. The only reason I say 'basically the same' is that the HSTouch plugin is gone in 357 (and above) since it's in the core HS3 code now.

I realize that not everybody running HS3 is seeing this, but it's very consistent on my HS installation: 326 or lower, no issue; 357 or higher, big issue.

Any suggestions on troubleshooting to figure out what might be going on?

Thanks!

-M.

[Rvtravlr]

Getting this error...

Unable to log into Gmail server: Authenticate as SSL client failed. You might be connecting to non SSL port.:Inner Exception: System.IO.IOException: Authentication failed because the remote party has closed the transport stream. at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceiv e(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsync Result lazyResult) at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost, X509CertificateCollection clientCertificates, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation) at Limilabs.Client.ClientBase.(Stream )