Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423

[bdickhaus]

And to keep this on topic, both systems have the slow memory rise. Which is not surprising, since one was cloned from the other a couple of years ago.

[Pete]

Guessing then a year ago you didn't have the issues you have today with versions prior to the Homeseer touch integration?

Here broke my attic ZWave RPi updating the RPi2 to Jessie lite running the mono zwave thing. It would run fine for a month or two then just quit running.

Note this was using the Pine64 or the Xi5a computer for Homeseer 3 running.

It became so slow that I couldn't SSH to the device and would have to power it off and on to get it going and over time it would trash the SD card.

I blamed it on Jessie lite running on the RPi2. Note it only did this running mono remote ZWave and I had no issues with running mono remote X10 or UPB remotely.

I have noticed here with V.387 on HS3 lite and pro that the HS3 memory increases have just about stopped. It seems to go up a bit and then down a bit these days.

[rjh]

Is build 391 still crashing with the clr.dll error? I have not see a post for a while.

[concordseer]

Is build 391 still crashing with the clr.dll error? I have not see a post for a while.

Rich still running .387 for 18 days now on Raspberry Pi. You mentioned a couple of weeks ago you wanted to release that version. What beta version is latest on Linux

[Daweeze]

Is build 391 still crashing with the clr.dll error? I have not see a post for a while.

Hey Rich,

I am at 4 days, 18 hours so far on this build.

-Travis

[enigmatheatre]

Is build 391 still crashing with the clr.dll error? I have not see a post for a while.

Rich,
I am on 390 and have an uptime of over 6 days without the clr.dll error which is good for me. I will keep running this to test.

Greig.

[randy]

Is build 391 still crashing with the clr.dll error? I have not see a post for a while.

I've not had any problems with .391, though I was not having crashes with earlier betas. I did have some creeping high CPU utilization with some after .379, but that has not happened with .391.

[MNB]

@Rich, I too have been running v.391 without any crash/hangs with "clr.dll error", according to My System Uptime: I'm at 4 Days 17 Hours 47 Minutes 36 Seconds. I have yet to re-enable my "Morning Announcement" scripts and was thinking about re-enabling them tomorrow morning (allows me to clock-in plus 5 days uptime) to see if I notice any stability issues. Mike

[rjh]

I updated the Beta post with links to the very latest builds for all systems. The latest version 3.0.0.393, so if you are testing, please test with this build. I do want to release this soon.

https://forums.homeseer.com/showthread.php?t=181241

[Pete]

Thank-you Rich.

Updated

HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.393 (Linux)
HomeSeer Version: HS3 Pro Edition 3.0.0.393 (Linux)

[Daweeze]

I updated the Beta post with links to the very latest builds for all systems. The latest version 3.0.0.393, so if you are testing, please test with this build. I do want to release this soon.

https://forums.homeseer.com/showthread.php?t=181241

Hey Rich,

Upgraded to version 3.0.0.393 per your request.

-Travis

[MNB]

Thanxs Rich, have updated to v.393 with no problems loading Will advise if we encounter any issues, Mike

[Pete]

@Rich,

Just noticed that in the update to Homeseer 3 Pro all of my plugins are not initializing using following hardware and os.

Hardware: Intel Haswell iSeries / 16Gb
OS: Ubuntu 16.04 64 bit
Mono: 5.4X

Downgraded to Homeseer 3 Pro V.387 and all of the plugins are working. Tested upgrade a second time to V.393 and confirmed that plugins do not initialize.

Here is one error...for the Omni Plugin. Same for others.

Dec-09 8:28:30 PM Info Plugin OMNI has connected. IP:127.0.0.1:40196
Dec-09 8:28:30 PM Info Plugin OMNI with instance: has disconnected
Dec-09 8:28:30 PM Error Initializing plug-in(2): OMNI Instance::Object reference not set to an instance of an objectSTACK: at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_remoting_wrapper (intptr,intptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI:InitIO (string) at Scheduler.clsHSPI.CheckInterfaces () [0x00098] in :0

[bdickhaus]

Guessing then a year ago you didn't have the issues you have today with versions prior to the Homeseer touch integration?

I was having memory issues well before the hstouch integration. It got worse with those early releases with the integration, now it is much better. But it is still happening. I haven't had time to go back and turn everything off and add things one at a time.

[Pete]

Guessing running Ubuntu 64 bit with 4gb of Ram should help running 8 plugins.