Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423

[enigmatheatre]

I am seeing that error to but also have a strange user show up in the user list. support@riverside.k12.az.us

Greig.

Sent from my SM-G950F using Tapatalk

[MNB]

I am seeing that error to but also have a strange user show up in the user list. support@riverside.k12.az.us

Greig.

Sent from my SM-G950F using Tapatalk

@Greig out of curiosity where are you seeing user list from? Mike

[randy]

@Greig out of curiosity where are you seeing user list from? Mike

All of the users are displayed at the top of the page under the Network tab of setup with the heading "Web/HSTouch User Settings".

[Guest]

I have posted build 3.0.0.398 for testing.

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

Thanks Rich. Testing and events feel snappy. Have not had a chance to test SSL just yet. Which ini file are the SSL settings held in?

[MNB]

All of the users are displayed at the top of the page under the Network tab of setup with the heading "Web/HSTouch User Settings".

Thanxs for the steer, Mike

[rjh]

This is fixed in build 398 which is posted. If you are testing, please update to 398.

@Rich I am on .397 and I am getting the following error in the log:

Dec-16 14:17:02 Error In SettingManager getVar setting var gUseNormalLogFolder: Object reference not set to an instance of an object.

On the Setup / Labs tab, I saw the first item is Log is Persistent (saved to Data folder) but I do not have this checked.

Thanks,

Michael

[rjh]

SSL settings are in the settings.ini file, but can configure it from the Labs tab in setup.

Thanks Rich. Testing and events feel snappy. Have not had a chance to test SSL just yet. Which ini file are the SSL settings held in?

[Stuart]

Still seeing the error in 398

Stuart

[rjh]

Looks I did fix it, but it did not get into that build. Its a harmless error though, you can ignore.

Still seeing the error in 398

Stuart

[MNB]

@Rich, looks like your last two releases (IMHO) seems to have cured the crash/hang problem and the memory leak of v.368 seems to be managing its self for the Windows platform side of business.
I for one am happy with the latest v.398, obviously there is always something that could be fixed/tweaked to make the product better. I hope your "hair-pulling" development is coming to a crescendo and that you are able to get a final production release prior to the holidays. Many thanks for the putting up with me and having the patience as we test our product. Mike

[efrey]

I have posted build 3.0.0.398 for testing.

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

Thanks for another beta release. I've installed and after a day it is running fine on my HT-ZeeS2.

I'd like to try the SSL feature that is new to this beta release.

Changes in 3.0.0.398:
* Added SSL support to web server, configure on Labs tab in setup. For Linux, MONO 5 is probably required

I would appreciate recommended steps to update mono from 4.5.1 to 5.4.1 on a HT-ZeeS2.

(FWIW ... When I attempted to upgrade to mono 5.4.1 my Zee a few weeks ago ... I went through a process of backing up my sdcard, purging the current mono install, getting the 5.4.1 release and installing the various mono-pkgs, ... and at the end of it all the mono --version command still reported 4.5.1.)

[rjh]

We originally had to build MONO from source for the Zee since the Raspian repositories did not contain the latest MONO. I have not tried the latest Raspian yet so maybe someone who has the latest can tell us what version of MONO is in there. If its not ver 5, then you may have to build it from source.

Note that I did get 4.5 to work with Firefox and Edge browsers. For some reason Chrome does not like it.

The SSL support does seem to work fine on all browsers on our SSL unit, which does have MONO 5 on it.

I am looking to updating our ZEE S2 image.

Thanks for another beta release. I've installed and after a day it is running fine on my HT-ZeeS2.

I'd like to try the SSL feature that is new to this beta release.

Changes in 3.0.0.398:
* Added SSL support to web server, configure on Labs tab in setup. For Linux, MONO 5 is probably required

I would appreciate recommended steps to update mono from 4.5.1 to 5.4.1 on a HT-ZeeS2.

(FWIW ... When I attempted to upgrade to mono 5.4.1 my Zee a few weeks ago ... I went through a process of backing up my sdcard, purging the current mono install, getting the 5.4.1 release and installing the various mono-pkgs, ... and at the end of it all the mono --version command still reported 4.5.1.)

[concordseer]

Rich no need to build Mono from scratch. Just follow this link to add the latest version to your relevant Raspbian distribution repo. You will also need to download Dirmngr to complete the installation. You will be prompted to do this.

http://www.mono-project.com/download...d-lin-raspbian

[jlrichar]

Mobile UI?

I have posted build 3.0.0.398 for testing.

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

Hi Rich,

The beta I am on right now (.391) is the fasted version of HS3 I have ever used, and seems to be somewhat stable. Handles do continue to climb slowly, but it seems like even this is better in .398--which I will switch to soon. Since these betas seem to be solving most of the reported issues for folks I imagine you are close to a major release?

After that release will you release a beta with the new mobile UI you have hinted at? Releasing a beta with the new UI would be a great way to keep this testing momentum going. Lots of folks will probably have some time over the coming holidays to test.

At any rate--really nice job on the latest HS3 betas!!!

[efrey]

Thanks for sharing the link. That is what I had used in my attempts.

I followed the instructions on the mono-project.com website (although did not download Dirmngr and issued the sudo commands manually. I'll try again later tonight.)

The puzzling thing is that I can see it download and install all the 5.4.1 files, but at the end of the day the "mono --version" still displays 4.5.1.

What am I missing? Do I need to remove something manually? (I recall it was located something like /etc/sbin/mono. Not sure about /etc path but I do recall the whereis command showed it to be in sbin.)