Discussions related to HomeSeer Beta 3.0.0.332->356

[DSteiNeuro]

Rich,

This seems to have fixed it for me. Both screen changes and press of an element.

Thanks

Working here.
Thanks!

This version has been very stable for me

[SteveMSJ]

I do want to release this as soon as possible. Looking back through the posts, the issues I see are:

* Screens not switching from events, random issue. Can you check the log and make sure the event triggered ok. And enable HSTouch logging and see if the command was sent to the client. I cannot recreate this and looking at the code, I don't see anything obvious.

* Video on clients locking up the screen. Video is probably faster so maybe its tying up the clients. I may need to make a change in the client. I have yet to see this as I have a bunch of cameras at home and they don't slow down my client. Can you tell me which brand of camera is causing this?

Also for me PluginFunction ClientAction 82 to start an application on iOS device stopped working with the move of HSTouch into the core program. I thought I had reported it but looking back through the thread it seems I didn't

The attached event triggers and runs script with no errors in log. No errors also with HSTouch detailed logging on. This worked faultlessly with HSTouch as separate plug-in launching Google Maps at the defined location.

Does anybody else have this issue?

Updated to 3.0.0.343 today, no change. Everything else running well, definitely improved HSTouch performance.

Steve

[rjh]

I did not know anyone was calling directly into this plugin. Since its not a plugin, this would fail. So I added a check for this in the hs.pluginfunction call (and the other plugin calls) so it calls the correct object. Looks ok now, please try this build and let me know:

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

Also for me PluginFunction ClientAction 82 to start an application on iOS device stopped working with the move of HSTouch into the core program. I thought I had reported it but looking back through the thread it seems I didn't

The attached event triggers and runs script with no errors in log. No errors also with HSTouch detailed logging on. This worked faultlessly with HSTouch as separate plug-in launching Google Maps at the defined location.

Does anybody else have this issue?

Updated to 3.0.0.343 today, no change. Everything else running well, definitely improved HSTouch performance.

Steve

[stefxx]

I did not know anyone was calling directly into this plugin. Since its not a plugin, this would fail. So I added a check for this in the hs.pluginfunction call (and the other plugin calls) so it calls the correct object. Looks ok now, please try this build and let me know:

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

Great! Can't wait for the Linux version

[SteveMSJ]

I did not know anyone was calling directly into this plugin. Since its not a plugin, this would fail. So I added a check for this in the hs.pluginfunction call (and the other plugin calls) so it calls the correct object. Looks ok now, please try this build and let me know:

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

3.0.0.344 sorts this, my pluginfuction call now starts GoogleMaps on iPhone again. Thanks for the speedy resolution

I don't suppose you have a chance to take a quick look at the other longstanding issue with the pluginfunction call to HSTouch to set the text of an element? ClientAction 45.
There have been a number of threads and bugzilla's over the years but I don't think it has been resolved, e.g.
https://forums.homeseer.com/showthread.php?t=189795

This obviously predates the change bringing HSTouch into the core program so I apologise that it isn't directly related to this thread.

Many thanks,
Steve

[stefxx]

Just noticed another small issue that popped up since build 332 (or shortly after). I have a few events that check if a timer is less than 3 seconds (if device x turns off and timer y < 3 seconds) and that check always seems to return true. If I turn device x off, no matter the value of the timer but the event executes.

A similar event that checks if a timer is greater than 2 seconds works just fine.

[fvhemert]

Allthough most likely not specific to this release, something that would be nice if it could be resolved in an upcoming release because it is killing Blue Iris connectivity:

HSTouch eating up my Blue Iris connections
https://forums.homeseer.com/showthread.php?t=190144

Rich, can you put this on the list of HSTouch issues to address??

[rjh]

I will have a look.

Allthough most likely not specific to this release, something that would be nice if it could be resolved in an upcoming release because it is killing Blue Iris connectivity:

HSTouch eating up my Blue Iris connections
https://forums.homeseer.com/showthread.php?t=190144

Rich, can you put this on the list of HSTouch issues to address??

[The Profit]

I will have a look.

Hi Rich, is it possible to get a date when you think this might be an official release?


Sent from my iPad using Tapatalk

[rjh]

I posted build 348 for testing. I went ahead and added a "Voice Command" property to devices. It's on the device properties page. When set, this command will be given to Aexa and Google home, instead of the device name and location. Note that the standard Alexa skill does not use this property yet, only the Smart Home skill is supported. Other methods of handling voice will be modified to use this shortly.

Posted here:

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

[waynehead99]

I posted build 348 for testing. I went ahead and added a "Voice Command" property to devices. It's on the device properties page. When set, this command will be given to Aexa and Google home, instead of the device name and location. Note that the standard Alexa skill does not use this property yet, only the Smart Home skill is supported. Other methods of handling voice will be modified to use this shortly.



Posted here:



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

OMG!!! THANK YOU RICH!!

[rjh]

I hope to release it next week, going through testing this week.

Hi Rich, is it possible to get a date when you think this might be an official release?


Sent from my iPad using Tapatalk

[randy]

Very good Rich! We're getting dangerously close to something my wife will use

[DSteiNeuro]

I posted build 348 for testing. I went ahead and added a "Voice Command" property to devices. It's on the device properties page. When set, this command will be given to Aexa and Google home, instead of the device name and location. Note that the standard Alexa skill does not use this property yet, only the Smart Home skill is supported. Other methods of handling voice will be modified to use this shortly.

Posted here:

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

Very nice! Up and running. Don't forget to run the Echo discovery, if you use the Voice Command feature.

Any chance of adding alternative Voice Commands e.g. Kitchen Light || Kitchen Lamps?

[sidepipe]

I'm using several ClientAction calls. My layouts depend on 45 ( set element text property ) which doesn't work, so I can't really say if anything else does. Is there a new way to call the "PluginFunction" stuff for this build? As I say, I use a lot of them ( open a screen, set text etc )

This is using Linux and 3.0.0.348 manual tar install... had to revert to the current "stable" version after half hour of trying to work out what was going on