Discussions related to HS3 build 3.0.0.362

[jfla]

hi,

this morning, my system is upgraded to V.362

McsXap 3.0.0.64 don't work

The interface failed to initialyze .

I reboot my Pc and this is the same.

i revert to V .357, and now , it's Ok.

Jean-Francois.

[rjh]

Ok, I am pretty sure I have resolved the issues with these builds since 362. Some last minute changes broke the plugin API.

It would be ideal if some of you could load build 365 and report any issues you see. I have uploaded builds for all platforms. On the Zee, Zee S2, and SEL, you can run the updatehs script. Here is the Windows installer:

http://homeseer.com/updates3/SetupHS3_3_0_0_365.msi

And the Linux tar file:

http://homeseer.com/updates3/hs3_linux_3_0_0_365.tar.gz

[concordseer]

Plugin server spinning around again. One of my plugins throwing errors as a result. I'll wait till the server settles down and report back.

Ok I'm back on track. Plugin server responding at this end and all plugins operating normally on .363 in Linux Raspbian on Raspberry Pi 3.

[rjh]

363 could still have an issue with HSTouch, make sure you go to 365.

Ok I'm back on track. Plugin server responding at this end and all plugins operating normally on .363 in Linux Raspbian on Raspberry Pi 3.

[sooty]

Maybe it's fixed in .365 but I just tried the Windows version of .364 and there appears to be something in the HS3.exe causing it to consume all one core's cpu on my system. Gone back to .357 for now.

Paul..

[rjh]

Actually, a threading issue is what I fixed in 365 and I verified the CPU usage is low in 365.

Maybe it's fixed in .365 but I just tried the Windows version of .364 and there appears to be something in the HS3.exe causing it to consume all one core's cpu on my system. Gone back to .357 for now.

Paul..

[sooty]

Actually, a threading issue is what I fixed in 365 and I verified the CPU usage is low in 365.

CPU usage is back under control with 365

Paul..

[Pete]

Many plugins written and working will continue to work fine without updates unless there are base core changes in Homeseer 3.

This same topic was brought up with Homeseer 2 and Homeseer 1.

There are many plugin authors here that have been here since Homeseer 1.

We are kind of like family here.

[stefxx]

That error has something to do with HSTouch, can you load build 364 and post any error:

https://homeseer.com/updates3/SetupHS3_3_0_0_364.msi

I skipped 364 and installed 365. No more errors!

[andyf]

365 seems to be running well. No errors in the log.

[concordseer]

.365 running fine on Linux Raspbian Stretch. So far so good.

[happnatious1]

Moved from .357 to .365 on Ubuntu ESXI v6. CPU usage is better. everything seems to be working. I'm going to find some wood to knock on.

Current Date/Time: 9/20/2017 7:24:20 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.365
Linux version: Linux HS3 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 0 Days 0 Hours 45 Minutes 16 Seconds
Number of Devices: 342
Number of Events: 89
Available Threads: 800

Enabled Plug-Ins
3.0.2.0: AquaConnect
2.0.35.0: BLLAN
3.0.0.56: DSC Security
3.0.1.8: Kodi
1.2.0.0: Monoprice Amp
3.0.6405.17148: Ultra1Wire3
3.0.0.73: weatherXML
3.0.0.36: X10
0.0.0.6: YAMAHA-RECEIVER
3.0.1.130: Z-Wave

[Pete]

Updated the Homeseer Lite from V.357 to V.365. All looking good here. (well except for the static network stuff).

Will update Homeseer Pro puter tomorrow.

Current Date/Time: 9/20/2017 7:04:03 PM
HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.365
Linux version: Running command uname -a Linux ICS-HS3ZeeLite 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 0 Days 0 Hours 7 Minutes 16 Seconds

[jpape]

Upgraded to 3.0.0.365 and started getting these entries in the log.

Sep-20 21:14:42 Error DeSerializing object (byte): Unable to load type A.c71d5cdb2ed4347ec1505c1d2979a3dba+action required for deserialization. Source=mscorlib
Sep-20 21:14:42 Error DeSerializing object (byte): Unable to load type A.c71d5cdb2ed4347ec1505c1d2979a3dba+action required for deserialization. Source=mscorlib
Sep-20 21:14:41 Error DeSerializing object (byte): Unable to load type A.c71d5cdb2ed4347ec1505c1d2979a3dba+action required for deserialization. Source=mscorlib
Sep-20 21:14:41 Error DeSerializing object (byte): Unable to load type A.c71d5cdb2ed4347ec1505c1d2979a3dba+action required for deserialization. Source=mscorlib

I can't make out what the error is about.

Papester

[rjh]

Where you running one of the betas before? The error could be related to HSTouch actions in events, do you have any of those? If so, can you rebuild them and see if the error goes away? It looks like it saved some info from the beta builds in the events, but that data has changed.

Upgraded to 3.0.0.365 and started getting these entries in the log.

Sep-20 21:14:42 Error DeSerializing object (byte): Unable to load type A.c71d5cdb2ed4347ec1505c1d2979a3dba+action required for deserialization. Source=mscorlib
Sep-20 21:14:42 Error DeSerializing object (byte): Unable to load type A.c71d5cdb2ed4347ec1505c1d2979a3dba+action required for deserialization. Source=mscorlib
Sep-20 21:14:41 Error DeSerializing object (byte): Unable to load type A.c71d5cdb2ed4347ec1505c1d2979a3dba+action required for deserialization. Source=mscorlib
Sep-20 21:14:41 Error DeSerializing object (byte): Unable to load type A.c71d5cdb2ed4347ec1505c1d2979a3dba+action required for deserialization. Source=mscorlib

I can't make out what the error is about.

Papester