Discussions related to HomeSeer Beta 3.0.0.332->356

[Pete]

It took me a while here to update to V.342 which I think was the second version of HS to integrate Homeseer Touch.

I have been sitting on the fence relating to updating beyond V.342 lately.

That said per your post here disabled Homeseer Touch in the Tools> Setup > network page and the switch here does appear to be working.

A partial clip of the Homeseer logs showing a disconnect of all of the LAN connected clients.

Sep-07 11:48:44 AM HSTouch Server HSTouch was shutdown
Sep-07 11:48:44 AM HSTouch Server Client ICS-Jog-XPE-10:ICS-Jog-XPE-10 (192.168.244.225/4617) has raised LineDisconnected.
Sep-07 11:48:44 AM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171
Sep-07 11:48:44 AM ASR Speaker Client speech recognition stopped
Sep-07 11:48:44 AM HSTouch Server Client ICS-Jog-XPE-10 named ICS-Jog-XPE-10 has DISCONNECTED.
Sep-07 11:48:44 AM HSTouch Server Client ICS-Jog-XPE-05:ICS-Jog-XPE-05 (192.168.244.205/3372) has raised LineDisconnected.
Sep-07 11:48:44 AM HSTouch Server Client ICS-Jog-XPE-02:ICS-Jog-XPE-02 (192.168.244.202/1775) has raised LineDisconnected.

On and on here until all of the clients got disconnected.

Re-enabled HSTouch and all of them connected fine looking at the Homeseer logs.

In a quickie recap here using:

- HomeSeer Pro / Lite HS3 Edition 3.0.0.342 (Linux)
- HSTouch Windows Clients V.36

I understand that V.356 is or may be going to a standard release.

Updated Homeseer Pro machine running 3.0.0.342 (Linux) to HS3 Pro Edition 3.0.0.356 (Linux).

Noticed I have an archive of HS3 Pro Edition 3.0.0.348 (Linux) from August 9, 2017. Not sure why I went back to .342.

Starting logs show no errors and all clients connected fine.

Shut off Homeseer Touch via switch. Logs showing disconnect are less chatty kathy. Saw Homeseer Speaker client shut off 4 times.

Sep-07 1:57:32 PM HSTouch Server HSTouch was shutdown
Sep-07 1:57:32 PM HSTouch Server Client ICS-Jog-XPE-05:ICS-Jog-XPE-05 (192.168.244.205/3594) has raised LineDisconnected.

rest of HSTouch clients

Sep-07 1:57:32 PM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171
Sep-07 1:57:32 PM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171
Sep-07 1:57:32 PM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171
Sep-07 1:57:32 PM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171

I do not understand 4 speakers being disconnected here as there is only one running for HSPro machine.
Sep-07 1:57:32 PM ASR Speaker Client speech recognition stopped

Enabled Homeseer touch and everything connected fine.

Will let this run a bit and upgrade Homeseer 3 lite (zee) to same version.

[concordseer]

It took me a while here to update to V.342 which I think was the second version of HS to integrate Homeseer Touch.

I have been sitting on the fence relating to updating beyond V.342 lately.

That said per your post here disabled Homeseer Touch in the Tools> Setup > network page and the switch here does appear to be working.

A partial clip of the Homeseer logs showing a disconnect of all of the LAN connected clients.

Sep-07 11:48:44 AM HSTouch Server HSTouch was shutdown
Sep-07 11:48:44 AM HSTouch Server Client ICS-Jog-XPE-10:ICS-Jog-XPE-10 (192.168.244.225/4617) has raised LineDisconnected.
Sep-07 11:48:44 AM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171
Sep-07 11:48:44 AM ASR Speaker Client speech recognition stopped
Sep-07 11:48:44 AM HSTouch Server Client ICS-Jog-XPE-10 named ICS-Jog-XPE-10 has DISCONNECTED.
Sep-07 11:48:44 AM HSTouch Server Client ICS-Jog-XPE-05:ICS-Jog-XPE-05 (192.168.244.205/3372) has raised LineDisconnected.
Sep-07 11:48:44 AM HSTouch Server Client ICS-Jog-XPE-02:ICS-Jog-XPE-02 (192.168.244.202/1775) has raised LineDisconnected.

On and on here until all of the clients got disconnected.

Re-enabled HSTouch and all of them connected fine looking at the Homeseer logs.

In a quickie recap here using:

- HomeSeer Pro / Lite HS3 Edition 3.0.0.342 (Linux)
- HSTouch Windows Clients V.36

I understand that V.356 is or may be going to a standard release.

Updated Homeseer Pro machine running 3.0.0.342 (Linux) to HS3 Pro Edition 3.0.0.356 (Linux).

Noticed I have an archive of HS3 Pro Edition 3.0.0.348 (Linux) from August 9, 2017. Not sure why I went back to .342.

Starting logs show no errors and all clients connected fine.

Shut off Homeseer Touch via switch. Logs showing disconnect are less chatty kathy. Saw Homeseer Speaker client shut off 4 times.

Sep-07 1:57:32 PM HSTouch Server HSTouch was shutdown
Sep-07 1:57:32 PM HSTouch Server Client ICS-Jog-XPE-05:ICS-Jog-XPE-05 (192.168.244.205/3594) has raised LineDisconnected.

rest of HSTouch clients

Sep-07 1:57:32 PM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171
Sep-07 1:57:32 PM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171
Sep-07 1:57:32 PM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171
Sep-07 1:57:32 PM Speaker Speaker host disconnected, Name: ICS-HS3PRO IP address: 192.168.244.171

I do not understand 4 speakers being disconnected here as there is only one running for HSPro machine.
Sep-07 1:57:32 PM ASR Speaker Client speech recognition stopped

Enabled Homeseer touch and everything connected fine.

Will let this run a bit and upgrade Homeseer 3 lite (zee) to same version.

Pete by any chance did the update reset your login credentials on your speaker and possibly HSTouch.

On a separate matter a number of people are now updating from .318 to .356 now that it is slated for release. Maybe worth their while reading the posts at the beginning of this thread before they start. A bit of work to be done relating to the HSTouch plugin and it needs to be followed carefully.

[Pete]

did the update reset your login credentials on your speaker and possibly HSTouch?

No for local LAN connected speaker / Homeseer Touch clients (main-lining the connection).

I do not utilize MyHomeseer here on the clients or the main mothership or Homeseer Touch Designer.

On a separate matter a number of people are now updating

Yes. It would be a good idea to read this thread from the OP. We are on post #422 and the OP started in June, 2017.

The Homeseer Touch server moving from a plugin to being integrated in to Homeseer is a good thing. I have not noticed a difference here between the Homeseer Touch plugin versus being integrated in to Homeseer.

It would probably be good to close this thread now as Rich just started a new beta V.357 thread.

[concordseer]

did the update reset your login credentials on your speaker and possibly HSTouch?

No for local LAN connected speaker / Homeseer Touch clients (main-lining the connection).

I do not utilize MyHomeseer here on the clients or the main mothership or Homeseer Touch Designer.

On a separate matter a number of people are now updating

Yes. It would be a good idea to read this thread from the OP. We are on post #422 and the OP started in June, 2017.

The Homeseer Touch server moving from a plugin to being integrated in to Homeseer is a good thing. I have not noticed a difference here between the Homeseer Touch plugin versus being integrated in to Homeseer.

It would probably be good to close this thread now as Rich just started a new beta V.357 thread.

Yes Pete. Just noticed that on my way to the bed for the evening. The thread was starting to wander a bit I'll keep an eye out for the .357 Linux version. Fingers crossed its a Final.

[rjh]

357 is available for Linux, I updated the link in the release notes if you are using the tar file.

Yes Pete. Just noticed that on my way to the bed for the evening. The thread was starting to wander a bit I'll keep an eye out for the .357 Linux version. Fingers crossed its a Final.

[Pete]

Thank you Rich.

[concordseer]

357 is available for Linux, I updated the link in the release notes if you are using the tar file.

Thanks Rich.

[Jobee]

Issue with Log Filter

I have noticed with one of the versions after .350 the filter section of the log is not working. I used it with .350 so I know it was working. Today I needed to use it to troubleshoot a different issue and the Date Range dates are not working for me. They both only have the start date. I rebooted my server and restarted HS3 on 9/7. Now today I needed to filter the log just for a couple hours on the 8th, but it is not there.

Anyone else seeing this?

Michael

.

[The Profit]

I noticed that the beta has been moved to an official release, is it safe to just download it and allow it to upgrade? Or will we need to disable plugins and everything else that people have done before upgrade??


Sent from my iPad using Tapatalk

[Kerat]

357 is available for Linux, I updated the link in the release notes if you are using the tar file.

Sweet, I will patch when I get back in town on Sunday.


Sent from my iPhone using Tapatalk

[integlikewhoa]

Issue with Log Filter

I have noticed with one of the versions after .350 the filter section of the log is not working. I used it with .350 so I know it was working. Today I needed to use it to troubleshoot a different issue and the Date Range dates are not working for me. They both only have the start date. I rebooted my server and restarted HS3 on 9/7. Now today I needed to filter the log just for a couple hours on the 8th, but it is not there.

Anyone else seeing this?

Michael

.

Nope mine works fine on 354 I have todays and back a few weeks. You might want to check you log file. usually if it don't show in the drop down it's because it don't exist in the file. Maybe corrupt or reboot wiped it?

[rjh]

Note, we have released build 3.0.0.362:

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