ISY 5.3.4, 700 Zwave board here. I added an Aeotec Siren 6 and 2 700 series devices to improve Zwave network coverage and also replaced what I thought was the problematic Minoston plug with a 700 series Minoston plug. The Minoston 700 is within 5 feet of an Enbrighten wall switch and there are also 3 other Zwave devices in the garage, all of which work reliably and without errors. So at this point I don't think it's a question of range, although the siren is on the inside of the house, about 20 feet away from the Enbrighten and the other switches in the detached garage and there's a wifi router alongside some of the garage Zwave devices. I still get reliable, immediate responses to commands on the 700 series Minoston plug, but the occasional error in UD Mobile and ISY admin (image attached). I also get errors from another Minoston 500 series plug that is within 15 feet of a 700 series device here in the house. The Zwave network in its current form has been in place for about 6 days now. This occasional error only happens with the Minoston plugs.

My question is, what should I be looking for in the log, or how else can I troubleshoot this? The only thing I see in device communication events for the Minoston devices causing trouble is Error 0. What is an error 0? And if you tell me not to worry about it, I won't, except why is it causing the iSY to throw a "Can't communicate with device" error?

 

 

 

 

 

 

i would like an answer to yoir queation too. I have Trane RCS45 T-stats in two homes that behave the same. i can control them but cant get status. UD Mobile shows the same error you posted and in the admin console, the query fails and the level 3 trace shows tx & rx events working for quite a few exchanges then the acks stop and the ISY retries until it fails .. you might want to look at your level 3 event viewer to see if the same is happening. 

17 hours ago, landolfi said:

ISY 5.3.4, 700 Zwave board here. I added an Aeotec Siren 6 and 2 700 series devices to improve Zwave network coverage and also replaced what I thought was the problematic Minoston plug with a 700 series Minoston plug. The Minoston 700 is within 5 feet of an Enbrighten wall switch and there are also 3 other Zwave devices in the garage, all of which work reliably and without errors. So at this point I don't think it's a question of range, although the siren is on the inside of the house, about 20 feet away from the Enbrighten and the other switches in the detached garage and there's a wifi router alongside some of the garage Zwave devices. I still get reliable, immediate responses to commands on the 700 series Minoston plug, but the occasional error in UD Mobile and ISY admin (image attached). I also get errors from another Minoston 500 series plug that is within 15 feet of a 700 series device here in the house. The Zwave network in its current form has been in place for about 6 days now. This occasional error only happens with the Minoston plugs.

My question is, what should I be looking for in the log, or how else can I troubleshoot this? The only thing I see in device communication events for the Minoston devices causing trouble is Error 0. What is an error 0? And if you tell me not to worry about it, I won't, except why is it causing the iSY to throw a "Can't communicate with device" error?

 

 

 

 

 

 

Are you using the isy994 or polisy?

Quote

the query fails and the level 3 trace shows tx & rx events working for quite a few exchanges then the acks stop and the ISY retries until it fails

Thanks!  Are you getting these errors randomly or after sending a command? I noticed it is sometime unrelated to a command but most frequently happens right after the command.

Edited July 19, 20223 yr by landolfi

32 minutes ago, lilyoyo1 said:

Are you using the isy994 or polisy?

ISY with the new 700 zwave board.

2 minutes ago, landolfi said:

ISY with the new 700 zwave board.

There is no 700 board for the Isy. The latest board for the Isy is the 500 board. Michel has stated that they will not have a 700 board for it (only polisy). With that said, all communication will be at 500 series. 

I don't use the app so i can't say what the errors mean. 

If you've already run a network heal on your problem device, I would recommend clearing your Java cache just to ensure there isn't anything causing any conflicts. Next, bring your problem device closer to the Isy and run a heal. Then test to see if the error goes away. If it does then there's a chance it could be environmental. If it doesn't, trying removing the device from the Isy and re-adding. Something could've potentially gotten corrupted in the process. Repeat the tests. 

If it continues (especially if it's with the same device while others work) it could be a defective device. 

Thanks, I stand corrected on the board version and that removes some of the initial confusion for me. I was expecting considerably more range than I was getting from the ISY. So if I went full Polisy, it sounds like I could get 700 series range (with the Aeotec dongle). I have a Polisy that I'm hardly using so far, so that would be a good reason to finally migrate.

I've updated the neighbors on these devices more than once in the past, but since I'm within the first week of the current physical network config, I'm inclined to leave it for a bit. I'll try clearing the java cache in the meantime and then retry the add closer to the ISY as you suggest should the problem persist.

As for these particular devices, they are Minoston and I've seen reports elsewhere here on UD forums of defective Minoston devices. Unfortunately other affordable zwave plugs seem to be hard to find.

I've been having the same problem for several months now on a number of z-wave devices with my ISY-994 on v5.1 and series 500 dongle. They all seem to be older devices that I bought from monoprice. Same exact message on UD Mobile. I've cleared java cache and removed and re-added the Zwave device. No improvement.

The devices function properly, just don't return a successful response. Was some change made that would affect only older series Z-wave devices?

23 minutes ago, photogeek54 said:

ISY-994 on v5.1 and series 500 dongle

You should upgrade the ISY994 to 5.3.4 firmware. Not saying that will fix all your problems, but I would think some changes between 5.1 and 5.3.4 probably finetuned some z-wave settings since that was a big part of the 5.x upgrade. 

Especially since 5.3 was the first one to be an "official build" for full z-wave certification. 5.3.4 is further minor updates within the system. 

But you mention they're old devices and probably a generic z-wave device that might not actually meet some certification aspects that could be causing problems as ISY advanced into z-wave certification.