Jump to content

Zwave no longer working...possibly after upgrade


ctviggen1
Go to solution Solved by DennisC,

Recommended Posts

I upgraded to 5.6.4, and now nothing on Zwave works.  I'm not sure it was the upgrade, as the front lock MIGHT not have been working before then.  I have limited Zwave, only one light, ceiling fans, two locks.  I cannot control or query these from the admin panel.  I was getting various errors when I queried these.  Current error for queries is "Request failed". 

How can I test whether the Zwave module/card works?  Or whether it's the software? 

Link to comment
  • Solution
1 hour ago, ctviggen1 said:

I upgraded to 5.6.4, and now nothing on Zwave works.  I'm not sure it was the upgrade, as the front lock MIGHT not have been working before then.  I have limited Zwave, only one light, ceiling fans, two locks.  I cannot control or query these from the admin panel.  I was getting various errors when I queried these.  Current error for queries is "Request failed". 

How can I test whether the Zwave module/card works?  Or whether it's the software? 

I would suggest you start by powering down, waiting a bit and power up again. After about 30 minutes, check your Zwave device. If there is no status, try a query.

Also, make sure Zwave is enabled on the Configuration tab of admin console.

  • Like 1
Link to comment
1 hour ago, ctviggen1 said:

Thanks, I'll try that when I get home (I'm at work).

For the power down, is this just a removal of the power plug?  Or does the admin console have a shutdown?  (My EISY is in a place that's a bit tough to get to.)

I would suggest you shutdown gracefully and then pull the plug for a couple of minutes before plugging power back in.

Link to comment

I had the same issue occur when updating my Polisy to 5.6.4.  The upgrade executed successfully and upon logging back into the AC, Z-wave was not functioning at all.  I ended up doing a power cycle on the Polisy and when everything came back up again, Z-wave was back and functioning properly.  I queried all Z-wave devices and all updated/reported successfully.

Link to comment

Unplugging the EISY then plugging it back in did work.  I found all the devices and was able to lock the front door using the admin console.  

I couldn't see a way to do a clean shutdown.  There's only a "reboot" on the admin console, no "shutdown".  And I figured there's not much difference between a reboot and unplug and and unplug without rebooting.

Link to comment
3 hours ago, ctviggen1 said:

I couldn't see a way to do a clean shutdown.  There's only a "reboot" on the admin console, no "shutdown".  And I figured there's not much difference between a reboot and unplug and and unplug without rebooting.

For some reasons sometimes the "Reboot" in the admin console doesn't force a full reboot/power cycle of the device. 

Since you mentioned your eisy is in a difficult spot to get to if unplugging isn't easy if you can get to the power button (aka "Multi function button") you can use that to reboot (5 button presses) or shut down (6 button presses). 

Another option might be to put it on an on/off outlet (maybe not z-wave or zigbee) that can be controlled by a 3rd party app should the eisy become unresponsive. Some have commented about using a Kasa outlet to be able to use the Kasa app to cycle the device. Not the "cleanest" of ways, but an option.

Finally, I think Michel's comment about a ticket might have been to help troubleshoot what happened so they (UDI) can learn from the issues from the update. 

Glad the power cycle worked!

Link to comment

Thanks.  I attached the EISY to a joist in my basement, which was near a preexisting outlet in the ceiling and also between the two Zwave door locks I have.  The original location of the ISY 994i (which the EISY replaced) was too far from the front door, causing intermittent issues.  This location (and probably different Zwave hardware) has resulted in many fewer issues. 

I was able to unplug the transformer using a ladder.  Turns out this is also on the breaker for the fire alarms, which I found out when I changed out an alarm.  I could do that too. 

Sorry -- I didn't realize that the ticket would be for them to troubleshoot.  I just thought a shut down and reboot seemed reasonable. 

  • Like 1
Link to comment
Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      36.6k
    • Total Posts
      368.1k
×
×
  • Create New...