Comm Enabled unchecked after trying to turn on devices

I've had this happen a few times lately and cannot figure out why. After trying to turn on a group of lights with my iPhone, some devices stop working. When I log in to Indigo, the Comm Enabled checkbox for many devices are now unchecked. Below is what's in the log. Any recommendations on how to fix this? I'm running Indigo 7.1.1. Thanks ahead for your assistance.

Code: Select all

Feb 15, 2018, 5:42:32 PM
   WebServer                       Indigo Touch client connected from 10.0.1.102
   Virtual Devices                 sent "Backyard Lights" on
   Z-Wave                          sent "Trampoline Lights" on
   Z-Wave                          sent "Lower Patio Lights" on
   Z-Wave                          sent "Upper Patio Lights" on
   Z-Wave                          sent "Back Low Voltage" on

Feb 15, 2018, 5:43:40 PM
   Z-Wave Error                    no ack/nak/busy reply (017) for setRelayValue (re-sending)

Feb 15, 2018, 5:44:46 PM
   Z-Wave Error                    no ack/nak/busy reply (017) for setRelayValue (re-sending)

Feb 15, 2018, 5:45:52 PM
   Z-Wave Error                    no ack/nak/busy reply (017) for setRelayValue (re-sending)
   Z-Wave Error                    send "Back Fence Lights" on failed
   Z-Wave                          sent "Back Fence Lights" on

Feb 15, 2018, 5:46:45 PM
   Z-Wave Error                    send setRelayValue failed after 9 attempts
   Z-Wave Error                    restarting serial connection in 5.0 seconds
   Interface Failure               lost connection with interface
   Schedule                        Outdoor Lights On
   Z-Wave                          connected to Z-Stick Plus (ZW090) interface on /dev/cu.usbmodem1411 (firmware 1.00)
   Z-Wave Error                    module 003 included in controller no longer matches device "Front Door Light" type (controller module type: zwDimmerType/zwDimmerType (4, 17, 4), indigo device type: zwDimmerType (4, 17, 1))
   Z-Wave                          found module included in controller with no matching device (missing or disabled): 004 - Dimmable Power Switch
   Z-Wave Error                    module 005 included in controller no longer matches device "Z-Wave Repeater Slate Room" type (controller module type: zwRelayType/zwRelayType (4, 16, 1), indigo device type: zwCustomType (4, 15, 1))
   Z-Wave Error                    module 007 included in controller no longer matches device "Upper Patio Lights" type (controller module type: zwCustomType/zwCustomType (4, 15, 1), indigo device type: zwRelayType (4, 16, 3))
   Z-Wave Error                    module 009 included in controller no longer matches device "Back Low Voltage" type (controller module type: zwRelayType/zwRelayType (4, 16, 3), indigo device type: zwRelayType (4, 16, 1))
   Z-Wave Error                    module 010 included in controller no longer matches device "Lower Patio Lights" type (controller module type: zwRelayType/zwRelayType (4, 16, 1), indigo device type: zwRelayType (4, 16, 3))
   Z-Wave Error                    module 012 included in controller no longer matches device "Z-Wave Repeater Garage" type (controller module type: zwRelayType/zwRelayType (4, 16, 3), indigo device type: zwCustomType (4, 15, 1))
   Z-Wave Error                    module 013 included in controller no longer matches device "Front Low Voltage" type (controller module type: zwRelayType/zwRelayType (4, 16, 3), indigo device type: zwRelayType (4, 16, 1))
   Z-Wave                          found module included in controller with no matching device (missing or disabled): 014 - Basic Repeater Slave
   Z-Wave Error                    module 015 included in controller no longer matches device "Z-Wave Repeater Garage South" type (controller module type: zwRelayType/zwRelayType (4, 16, 1), indigo device type: zwCustomType (4, 15, 1))
   Z-Wave Error                    module 017 included in controller no longer matches device "Back Fence Lights" type (controller module type: zwCustomType/zwCustomType (4, 15, 1), indigo device type: zwRelayType (4, 16, 1))
   Z-Wave Error                    module 020 included in controller no longer matches device "Shed Path Light" type (controller module type: zwRelayType/zwRelayType (4, 16, 1), indigo device type: zwRelayType (3, 16, 0))
   Z-Wave Error                    module 021 included in controller no longer matches device "Side Patio Light" type (controller module type: zwRelayType/zwRelayType (4, 16, 1), indigo device type: zwRelayType (3, 16, 0))
   Z-Wave Error                    module 022 included in controller no longer matches device "Front Door Outdoor Light" type (controller module type: zwRelayType/zwRelayType (3, 16, 0), indigo device type: zwRelayType (4, 16, 3))
   Z-Wave Error                    module 023 included in controller no longer matches device "Front Door Outside Outlet" type (controller module type: zwRelayType/zwRelayType (3, 16, 0), indigo device type: zwRelayType (4, 16, 3))
   Z-Wave Error                    module 024 included in controller no longer matches device "Creek" type (controller module type: zwRelayType/zwRelayType (4, 16, 3), indigo device type: zwRelayType (4, 16, 1))
   Z-Wave Error                    to re-enable the devices with new z-wave modules, press the "Define and Sync..." button in the device dialog
   Z-Wave Error                    could not find module/node for action
   Z-Wave Error                    could not find module/node for action
   Z-Wave                          sent "Garage Outdoor Lights" on
   Z-Wave Error                    could not find module/node for action
   Z-Wave Error                    could not find module/node for action


I have been getting the same. Happened 3 times in last few months.


Sent from my iPhone using Tapatalk

[matt (support)]

I'm not sure why it is occurring but either the Z-Stick is locking up and becoming unresponsive, or there are USB level errors occurring (which might be related to macOS changes). Trying different USB ports or a USB hub might help. We are looking at making Indigo more robust when it occurs, but there isn't anything we can do about the root communication errors that are occurring – we can just make Indigo less aggressive about disabling communication with devices when it starts receiving garbage from the Z-Stick.

Thanks. Don't suppose there is a way to capture that it's happened, ie at least one device has had comms disabled so I know to go and turn them all back on. Sometimes I don't realise it's happened straight away and then lose some more critical house functionality, worse if its the wife that finds out first as some lights won't turn out.


Sent from my iPhone using Tapatalk

Thanks Matt.

Do you have any recommendations on how to debug what's really happening? Any logging that can be turned on in Indigo? I'm on my second Z-Stick and it's still under warranty. If it's malfunctioning, I would like to know so I can get it replaced.

There are not many options for ports on the Mac Mini since the computer will only boot if the stick is in the port closest to the power connector. This seems to be a common issue reported in the forum. The only change I made yesterday was connecting the stick to the end of a 1m USB extension cable. Maybe that will help. Indigo will not recognize the stick when connected to a powered USB hub. I had this issue with the previous stick too.

[matt (support)]

Don't suppose there is a way to capture that it's happened, ie at least one device has had comms disabled so I know to go and turn them all back on.

You could try running a periodic script that loops through all the devices to test if they are enabled or not. Untested, but something like:

Code: Select all

for dev in indigo.devices.iter("indigo.zwave"):
  if dev.configured and not dev.enabled:
    indigo.actionGroup.execute(someActionGroupID_or_name)
    break  # prevent from executing Action Group multiple times.

[matt (support)]

Do you have any recommendations on how to debug what's really happening? Any logging that can be turned on in Indigo? I'm on my second Z-Stick and it's still under warranty. If it's malfunctioning, I would like to know so I can get it replaced.

Unfortunately, not really. There is low level Z-Wave debug logging, but that won't help much in this case as the problem isn't related to debugging . Although it could be a defective Z-Stick, I lean more towards it being a firmware bug (that isn't fixed in any Z-Stick version) that causes it to get into a bad state and misreport information to Indigo.

There are not many options for ports on the Mac Mini since the computer will only boot if the stick is in the port closest to the power connector. This seems to be a common issue reported in the forum.

I don't think that is a common issue at all. Maybe one or two other reports of it if I remember correctly. Given the number of Z-Sticks being used on Mac Minis (including mine here), it definitely isn't something I would expect to happen. Just to be clear, the Mac doesn't boot at all (or the Z-Stick just doesn't show up once booted)? If the Mac isn't booting at all, then I would actually lean towards it being a defective Z-Stick.

The only change I made yesterday was connecting the stick to the end of a 1m USB extension cable. Maybe that will help. Indigo will not recognize the stick when connected to a powered USB hub. I had this issue with the previous stick too.

I'm surprised a powered hub doesn't work. Again, that might be another sign of a bad Z-Stick. Not all hubs work, but I believe most of them will. I actually had problems here with a Z-Stick and a USB extension cable (which was a passive cable and not an "active" hub cable). It introduced lots of subtle USB level garbage that wasn't reported to Indigo as errors, but the byte values would definitely occasionally be incorrect.

USB2 hub fixed the issue for me - both passive and active works. The key - USB2, but not USB3

Passive works only if connected via 10cm built-in cable.

Cheap powered dlink works perfectly well.

https://www.amazon.co.uk/dp/B00006B7DA/ ... TE_3p_dp_1