Recently my voice command becomes very unreliable. This morning, I asked Alexa to turn on/off the Master Bed Side Light, and it does not listen  Here is the log.

I downloaded the error log too. But it does not have any entry at around the same time stamp. IN fact, my error log stops at around 8:47 AM on the same day, and the time I tried to juse Alexa is 9:31AM as you can see in the log. I posted my error log here anyway.

Of course, I want to understand why there is "Error" in the normal ISY log but no error in the error log. I researched and found that -170001 in the error log is informational so does not seem to matter.

Anyone knows how to fix this? This happens sporadically for me, and recently happens much more than before. Iw ould say more than half of the time my voice command does not work.

 

 

 

Master Bed Side	On		Mon 2019/12/09 09:29:20 AM	Web	Log
Master Bed Side	Error	1	Mon 2019/12/09 09:29:24 AM	System	Log
Master Bed Side			Mon 2019/12/09 09:29:24 AM	System	-2
Master Bed Side	On		Mon 2019/12/09 09:29:36 AM	Web	Log
Master Bed Side	Error	0	Mon 2019/12/09 09:29:44 AM	System	Log
Master Bed Side	Status	100%	Mon 2019/12/09 09:29:44 AM	System	Log
Master Bed Side	Off		Mon 2019/12/09 09:31:34 AM	Web	Log
Master Bed Side	Error	1	Mon 2019/12/09 09:31:38 AM	System	Log

 

Error Log:

Sat 2019/12/07 07:25:18 PM    System    -10108    Check log    
Mon 2019/12/09 08:47:28 AM    System    -170001    [Auth:-10104] 104.237.128.197:43656->443, Num=
 

 

 

 

 

 

 

@zhangyeus 

Please remove all port forwarding rules to ISY. It seems that you might be getting hacked. 

Also, it seems that you have insteon communication issues. Please try moving the PLM to a different outlet.

 

With kind regards,

Michel

Thanks for your reply. I am curious how do you think I might be getting hacked? The log I posted shows my several attempts of using Alexa->did not work-> use siwtch physically ->worked -> use Alexa app to turn it off -> did not work. Is my error log looking bad? Could you please let me know?

Yes, I have more than 100 insteon switches/outlets and quite some z-wave devices etc. I totally buy that my PLM may not be communicating well. I have been plugging it in a cord extension to get it to a position where ISY has better z-wave coverage... I will try to move it around.  

Appreciate such a fast reply.

@zhangyeus,

Mon 2019/12/09 08:47:28 AM    System    -170001    [Auth:-10104] 104.237.128.197:43656->443, Num=

So, unless you know who is min-extra-grab-209-ustx-prod.binaryedge.ninja (104.237.128.197), then you are being hacked.

With kind regards,
Michel

36 minutes ago, Michel Kohanim said:

@zhangyeus,

Mon 2019/12/09 08:47:28 AM    System    -170001    [Auth:-10104] 104.237.128.197:43656->443, Num=

So, unless you know who is 104.237.128.197), then you are being hacked.

With kind regards,
Michel

This is interesting as I just happened to see something similar recently in my log.  It appears there were 12(?) hacking attempts from 192.46.140.90 that were logged on 12-8.  That is not an IP in my LAN and a Google search comes up with a 198-46-140-90-host.colocrossing.com which is listed as a SPAM hosting hacking site. Fortunately except for these 12 entries, I did not find any others.

At any rate, I closed down my port forwarding to the ISY which hopefully secures my site. I set this forwarding up a long, long time ago for remote access to the ISY.  Apparently port forwarding is not required when using the ISY portal. 

In fact I could never get port forwarding to work at a site where I had 2 routers in series to my ISY.  But the ISY Portal never has had an issue seeing through all that to access the ISY.  Amazing MOJO by U-D!

 

Thanks a lot! I erroneously think that is from the ISY portal. Clearly I am wrong. Let me disable all the ports and see what happens.