Discussions related to HS3 build 435

[stefxx]

After a week or two of running stable on 435, HS3 just "disappeared" this morning. No error message on the screen, but HS3 was not running anymore. This is what I found in the windows event logs:

Exception: System.Runtime.InteropServices.SEHException

Message: External component has thrown an exception.

StackTrace:    at System.Threading.Monitor.ObjWait(Boolean exitContext, Int32 millisecondsTimeout, Object obj)
   at System.Threading.Monitor.Wait(Object obj, Int32 millisecondsTimeout, Boolean exitContext)
   at HSCF.Threading.QueueProcessorThread`1.DoProcess()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

The request is not supported

and

Application: HS3.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
   at System.Threading.Monitor.ObjWait(Boolean, Int32, System.Object)
   at System.Threading.Monitor.Wait(System.Object, Int32, Boolean)
   at HSCF.Threading.QueueProcessorThread`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].DoProcess()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

and

Faulting application name: HS3.exe, version: 3.0.0.435, time stamp: 0x5ada0565
Faulting module name: ntdll.dll, version: 10.0.17134.112, time stamp: 0xcfe5bd82
Exception code: 0xc0150014
Fault offset: 0x0008dcb6
Faulting process id: 0x294c
Faulting application start time: 0x01d4074891e7798b
Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HS3.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: a99c7834-b466-4612-844b-3288cf65d0c8
Faulting package full name: 
Faulting package-relative application ID:

I am running Windows Defender and have the HomeSeer HS3 directory excluded from scanning. Running Windows 10 1803.

[rjh]

I have never seen that error before. After some googling it looks like it could be the result of a conflict with some other app, like the bitdefender issue we saw before. Are you running any other services that monitor or tie into the networking system like a port monitor, antispam, etc.? Errors in ntdll point to a networking related error.

After a week or two of running stable on 435, HS3 just "disappeared" this morning. No error message on the screen, but HS3 was not running anymore. This is what I found in the windows event logs:

Exception: System.Runtime.InteropServices.SEHException

Message: External component has thrown an exception.

StackTrace:    at System.Threading.Monitor.ObjWait(Boolean exitContext, Int32 millisecondsTimeout, Object obj)
   at System.Threading.Monitor.Wait(Object obj, Int32 millisecondsTimeout, Boolean exitContext)
   at HSCF.Threading.QueueProcessorThread`1.DoProcess()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

The request is not supported

and

Application: HS3.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
   at System.Threading.Monitor.ObjWait(Boolean, Int32, System.Object)
   at System.Threading.Monitor.Wait(System.Object, Int32, Boolean)
   at HSCF.Threading.QueueProcessorThread`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].DoProcess()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

and

Faulting application name: HS3.exe, version: 3.0.0.435, time stamp: 0x5ada0565
Faulting module name: ntdll.dll, version: 10.0.17134.112, time stamp: 0xcfe5bd82
Exception code: 0xc0150014
Fault offset: 0x0008dcb6
Faulting process id: 0x294c
Faulting application start time: 0x01d4074891e7798b
Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HS3.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: a99c7834-b466-4612-844b-3288cf65d0c8
Faulting package full name: 
Faulting package-relative application ID:

I am running Windows Defender and have the HomeSeer HS3 directory excluded from scanning. Running Windows 10 1803.

[stefxx]

I have never seen that error before. After some googling it looks like it could be the result of a conflict with some other app, like the bitdefender issue we saw before. Are you running any other services that monitor or tie into the networking system like a port monitor, antispam, etc.? Errors in ntdll point to a networking related error.

It is my dedicated HS3 machine, reinstalled a few weeks ago (very clean Windows install). The only "other" software installed is Bonjour (for Chromecast plugin), IRTrans LAN (for IRTrans plugin) and RFXMngr (RFXCOM).

[concordseer]

Had there been any changes to your .Net Framework recently

[stefxx]

Had there been any changes to your .Net Framework recently

Not by me and I can't find anything .Net related in the update history...

[concordseer]

What version of Windows are you using. Your .Net Framework version looks a little dated. I'm not a Windows user but I tend to keep Mono as current as possible running in Linux. I noticed the latest .Net Framework version is 4.7

[Moskus]

What version of Windows are you using. Your .Net Framework version looks a little dated. I'm not a Windows user but I tend to keep Mono as current as possible running in Linux. I noticed the latest .Net Framework version is 4.7

HomeSeer uses .NET framework 4.0, not 4.7.
https://docs.microsoft.com/en-us/dot...d-dependencies

You don't need to install 4.7 until you have software that depends on it. HomeSeer does not.

[rjh]

HS is built against ver 4.0 but I believe that only means we are limited to the 4.0 API. If you look in your .net folder under system/Microsoft.net you will see only one 4.0... folder with all the DLL files. They are used for 4.0 and 4.7 so I bet if you update to 4.7 you must get some fixes for 4.0 (or some new bugs). But I could be wrong!

The development systems and test systems here all have 4.7 on them.

So I would suggest updating to 4.7, at least it will match with what we test with.

HomeSeer uses .NET framework 4.0, not 4.7.
https://docs.microsoft.com/en-us/dot...d-dependencies

You don't need to install 4.7 until you have software that depends on it. HomeSeer does not.

[concordseer]

HomeSeer uses .NET framework 4.0, not 4.7.
https://docs.microsoft.com/en-us/dot...d-dependencies

You don't need to install 4.7 until you have software that depends on it. HomeSeer does not.

As posted earlier I'm not a Windows user but it looked strange to have such a dated version of .Net Framework running on your system. The subsequent post from Rich might just confirm this. I only made that suggestion in the absence of any other logical explanation for your error message.

[stefxx]

Windows 10 version 1803. Detected .Net version is 4.7.2.

[Moskus]

They are used for 4.0 and 4.7 so I bet if you update to 4.7 you must get some fixes for 4.0 (or some new bugs). But I could be wrong!

I'm not 100% sure. I still think 4.0 is maintained with bug fixes through Windows Update even if you don't install the latest .NET Frameworks.

I can install .NET Framework 4.7 while HomeSeer is still running and without a restart afterwards, but I can't update version 4.0 while it's running (it has to restart afterwards). I know this because I just testet it with my new HS3 server that is running Windows 7 (as Win10 1803 is making problems for HS3).

At the office we have (among others) a virtual Windows 7 machine with the .NET framework 4.0 installed, but not newer ones. I see the updates contains fixes from time to time, so I would say 4.0 is still maintained (as expected).

[skavan]

I'm not sure if this is a bug or intended behavior...BUT:

http://xxx.xxx.xxx.xxx/JSON?request=voicecommand&phrase=increase porch lights [B]by[/B] 20 percent

doesn't do that, it SETS brightness to 20%. I have tried playing with increase|brighten|bright|raise - all to no avail.

http://xxx.xxx.xxx.xxx/JSON?request=voicecommand&phrase=increase porch lights

results in a

{ "Response":"That command was not found on the device." }

For future consideration, it would also be great if the json response object could include a status object of the device being controlled. Even if the status fields were limited to ref# and name/location/voicecommand fields.

Finally, while I have the mic, the ?request=getstatus response, doesn't include the setting of the voice_command_enabled Boolean. This flag is included with the ?request=getevents.

Could it be added to the getstatus response please.

s.

[rjh]

The support for "by" is not in there at this time but its noted to get it added in a future update. Note that I believe "by" does work if you use the Amazon or Google smart home skills.

I'm not sure if this is a bug or intended behavior...BUT:

http://xxx.xxx.xxx.xxx/JSON?request=voicecommand&phrase=increase porch lights [B]by[/B] 20 percent

doesn't do that, it SETS brightness to 20%. I have tried playing with increase|brighten|bright|raise - all to no avail.

http://xxx.xxx.xxx.xxx/JSON?request=voicecommand&phrase=increase porch lights

results in a

For future consideration, it would also be great if the json response object could include a status object of the device being controlled. Even if the status fields were limited to ref# and name/location/voicecommand fields.

Finally, while I have the mic, the ?request=getstatus response, doesn't include the setting of the voice_command_enabled Boolean. This flag is included with the ?request=getevents.

Could it be added to the getstatus response please.

s.

[skavan]

The support for "by" is not in there at this time but its noted to get it added in a future update. Note that I believe "by" does work if you use the Amazon or Google smart home skills.

Thanks.

So, I have built my own Alexa skill, in order to capture and use device location. So

Tell Jarvis to Turn on the Lights

will turn on the living room lights, if that echo is regsitered to the living room

Tell Jarvis to Register this Echo to the Living Room

.
Right now, I send my finished voice_command:

turn on the living room lights

to Homeseer via a

/JSON?request=voicecommand&phrase=turn on the living room lights

.

It's working well and handles switch on/off/turn on/off/change/dim and so forth.

Now, I don't actually know whether you do your Alexa/Google processing in the cloud or it happens locally with HS3.

• If the former, it would be great (using account linking) to send my processed speech to your cloud service. My vendorId credentials would be in the json body.
• If the latter, then how can I modify my request=voicecommand so that homeseer believes its coming from Alexa and does all the processing goodness?
• Of course, we could move all this stuff directly to homeseer, if you passed down the echo deviceId that you receive with your custom skill.

Hope that all makes sense.

[rjh]

We have 2 skills for Alexa. The "tell homeseer to..." skill simply sends the entire voice command to HS and HS processes it. The ability to do this has been removed, so I am told, but they are allowing us to continue to use it.

The second skill is the SmartHome Alexa skill. With this one, Amazon does all the processing and sends json commands to HS to control devices. We never see the actual voice command that is heard.

Thanks.

So, I have built my own Alexa skill, in order to capture and use device location. So will turn on the living room lights, if that echo is regsitered to the living room .
Right now, I send my finished voice_command: to Homeseer via a

/JSON?request=voicecommand&phrase=turn on the living room lights

.

It's working well and handles switch on/off/turn on/off/change/dim and so forth.

Now, I don't actually know whether you do your Alexa/Google processing in the cloud or it happens locally with HS3.

• If the former, it would be great (using account linking) to send my processed speech to your cloud service. My vendorId credentials would be in the json body.
• If the latter, then how can I modify my request=voicecommand so that homeseer believes its coming from Alexa and does all the processing goodness?
• Of course, we could move all this stuff directly to homeseer, if you passed down the echo deviceId that you receive with your custom skill.

Hope that all makes sense.