No Response to az00

[mminehan]

I'm also getting this error a few times a day:

Apr-15 00:45:03 1 Error System.FormatException
Apr-15 00:45:03 1 Error System.FormatException: Additional non-parsable characters are at the end of the string. at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos) at System.Convert.ToInt32(String value, Int32 fromBase) at HSPI_ULTRAM1G3.hspi_plugin.ProcessReceived(String strDataRec)
Apr-15 00:40:02 1 Error System.FormatException: Additional non-parsable characters are at the end of the string. at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos) at System.Convert.ToInt32(String value, Int32 fromBase) at HSPI_ULTRAM1G3.hspi_plugin.ProcessReceived(String strDataRec)
Apr-15 00:40:02 1 Error System.FormatException
Apr-15 00:08:36 1 Error System.FormatException: Additional non-parsable characters are at the end of the string. at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos) at System.Convert.ToInt32(String value, Int32 fromBase) at HSPI_ULTRAM1G3.hspi_plugin.ProcessReceived(String strDataRec)
Apr-15 00:08:36 1 Error System.FormatException
Apr-14 23:25:29 1 Error System.FormatException: Additional non-parsable characters are at the end of the string. at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos) at System.Convert.ToInt32(String value, Int32 fromBase) at HSPI_ULTRAM1G3.hspi_plugin.ProcessReceived(String strDataRec)
Apr-14 23:25:29 1 Error System.FormatException

[mminehan]

Has there been any progress on this issue?

I'm still getting the AZ errors, despite 100% success on 1000 pings and checking the data cable.

May-27 08:05:20 Warning No response/improper response from Elk M1 to command 'az00'
May-27 08:05:18 Warning Raw data was: 0AZC021200D
May-27 08:05:18 Warning Invalid checksum 16 for command ZC as data 021

[Ultrajones]

Are you running UltraM1G3 HSPI version 3.0.6326.22951?

[mminehan]

Yes.
HS3 Pro Edition 3.0.0.318 (Windows)
UltraM1G3 3.0.6326.22951

Cheers, M

[Ultrajones]

Yes.
HS3 Pro Edition 3.0.0.318 (Windows)
UltraM1G3 3.0.6326.22951

Cheers, M

Thank you for confirming. Did you replace the cable between the Elk M1 and the Elk M1XEP?

[philipi]

I can confirm that both serial cables have been replaced with shielded cables and the issue continues.

[mminehan]

Thank you for confirming. Did you replace the cable between the Elk M1 and the Elk M1XEP?

Yep....I have tried a ribbon cable and a shielded DB9. Still get to az00 error.

[Ultrajones]

Yep....I have tried a ribbon cable and a shielded DB9. Still get to az00 error.

Thanks for confirming. After replacing the cable, how often does the error/warning occur in your logs?

[Ultrajones]

I can confirm that both serial cables have been replaced with shielded cables and the issue continues.

Thanks for confirming. After replacing the cable, how often does the error/warning occur in your logs?

[rxatwell]

Solution

Sorry to bring up an old thread but I had the same issue and wanted to post a resolution, at least in my case and possibly anyone else that comes across this thread looking for a solution.

I migrated my HomeSeer server recently (Windows7 -> Windows 10) and had this error and others like it consistently anytime the plugin would communicate with Elk panel. (az00, cp00, zs00, etc.)

I have determined that it was a firewall/antivirus issue. In fact, I was never able to make Windows Firewall/Antivirus behave with this plugin. As soon as I installed my Norton Security and made the proper .exe file exception the problem resolved immediately.

I hope this information may help anyone else looking for a solution. Your mileage may vary. Cheers!

[mminehan]

I'm not sure it's a firewall issue for me (or Philip) as it happens randomly, not every time the plugin communicates.

I get it about 10 to 12 times a day. Errors like this:

Dec-05 09:52:05 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:52:04 Warning Raw data was: D6AZ00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000008B
Dec-05 09:52:04 Warning Invalid checksum 160 for command AZ as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000
Dec-05 09:52:01 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:52:00 Warning Invalid RegExp for data 0BPCM0901084
Dec-05 09:48:40 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:30:35 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:30:33 Warning Invalid checksum 80 for command AZ as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000
Dec-05 09:30:33 Warning Raw data was: D6AZ00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000B
Dec-05 09:14:04 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:14:03 Warning Raw data was: D6AZ00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000008B
Dec-05 09:14:03 Warning Invalid checksum 160 for command AZ as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000
Dec-05 07:28:48 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 06:56:07 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 06:56:05 Warning Invalid checksum 129 for command PC as data 162
Dec-05 06:56:05 Warning Raw data was: 0BPC1623080
Dec-05 06:42:26 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 06:42:25 Warning Invalid checksum 207 for command PC as data O120
Dec-05 06:42:25 Warning Raw data was: 0BPCO1200088
Dec-05 05:30:13 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 05:30:12 Warning Invalid checksum 207 for command PC as data N040
Dec-05 05:30:12 Warning Raw data was: 0BPCN0400088


And the plugin already has an exception in my firewall (Webroot).

Marty.

Sorry to bring up an old thread but I had the same issue and wanted to post a resolution, at least in my case and possibly anyone else that comes across this thread looking for a solution.

I migrated my HomeSeer server recently (Windows7 -> Windows 10) and had this error and others like it consistently anytime the plugin would communicate with Elk panel. (az00, cp00, zs00, etc.)

I have determined that it was a firewall/antivirus issue. In fact, I was never able to make Windows Firewall/Antivirus behave with this plugin. As soon as I installed my Norton Security and made the proper .exe file exception the problem resolved immediately.

I hope this information may help anyone else looking for a solution. Your mileage may vary. Cheers!

[snhroc]

I get it every 5 seconds!

I'm not sure it's a firewall issue for me (or Philip) as it happens randomly, not every time the plugin communicates.

I get it about 10 to 12 times a day. Errors like this:

Dec-05 09:52:05 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:52:04 Warning Raw data was: D6AZ00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000008B
Dec-05 09:52:04 Warning Invalid checksum 160 for command AZ as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000
Dec-05 09:52:01 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:52:00 Warning Invalid RegExp for data 0BPCM0901084
Dec-05 09:48:40 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:30:35 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:30:33 Warning Invalid checksum 80 for command AZ as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000
Dec-05 09:30:33 Warning Raw data was: D6AZ00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000B
Dec-05 09:14:04 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 09:14:03 Warning Raw data was: D6AZ00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000008B
Dec-05 09:14:03 Warning Invalid checksum 160 for command AZ as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000
Dec-05 07:28:48 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 06:56:07 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 06:56:05 Warning Invalid checksum 129 for command PC as data 162
Dec-05 06:56:05 Warning Raw data was: 0BPC1623080
Dec-05 06:42:26 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 06:42:25 Warning Invalid checksum 207 for command PC as data O120
Dec-05 06:42:25 Warning Raw data was: 0BPCO1200088
Dec-05 05:30:13 Warning No response/improper response from Elk M1 to command 'az00'
Dec-05 05:30:12 Warning Invalid checksum 207 for command PC as data N040
Dec-05 05:30:12 Warning Raw data was: 0BPCN0400088


And the plugin already has an exception in my firewall (Webroot).

Marty.

[fwolferd]

I resolved this issue by disabling all security options in Windows defender and turning off the Windows firewall.

[mminehan]

I resolved this issue by disabling all security options in Windows defender and turning off the Windows firewall.

So you now have no security on you HS machine? I don't like the implications of no secuirty.

It seems odd that Windows defender and firewall would cause this intermittent problem. You'd expect it to either block all or none of the traffic in question.

Can someone else verify that turning off all Windows security settings fixes this?

Marty

[geodementia]

Per the discussion about the latest plugin crashing, a number of us have confirmed that Windows Defender / Security Essentials are indeed the cause of the various comms failure and invalid message messages being logged by the UltraM1G plugin.

Disable them (via GPO) or uninstall them and everything starts working very nicely again, no errors!