Patrik wrote:Its series 2!
Have a gen 5 laying around...But if its the same its not worth to migrate?!
colin_d wrote:That pretty much rules out a hardware issue.
[SNIP]
The question is, how is the data being corrupted in the first place?
colin_d wrote:... It seemed to be provoked on almost any device changes, even doing a single optimise network would kick it off. I copied the script from viewtopic.php?f=58&t=19916&start=30#p163225 into a trigger which helped with re-enabling devices and notifying me, which is great, but if you can’t rely on the devices working then it’s a non-starter.
matt (support) wrote:? Indigo only auto-disables device communication when the interface is restarted (or physically removed/reinserted, or Indigo Server restarts) so I would hope that after running the script the devices work okay; at least until the next server or interface restart. If that isn't the case, then how are things failing specifically?
matt (support) wrote:I've been looking at what Indigo can do to workaround the problem, including not having it disable devices even though the Z-Stick is handing us bad information on most of the nodes. So after running the script to re-enable the devices does everything work okay for a while? Indigo only auto-disables device communication when the interface is restarted (or physically removed/reinserted, or Indigo Server restarts) so I would hope that after running the script the devices work okay; at least until the next server or interface restart. If that isn't the case, then how are things failing specifically?
17 Nov 2018, 16:33:38
Z-Wave Error send getVersion failed after 9 attempts
Z-Wave Error restarting serial connection in 5.0 seconds
Interface Failure lost connection with interface
17 Nov 2018, 16:34:20
Z-Wave connected to Z-Wave 3.95 static controller interface on /dev/cu.usbmodem1411 (firmware 1.00)
Z-Wave Error module 007 included in controller no longer matches device "007 - ROUTER POWER" type (controller module type: zwDimmerType/zwDimmerType (4, 17, 1), indigo device type: zwRelayType (4, 16, 1))
17 Nov 2018, 17:39:40
Z-Wave Error serial port communication error: read failed: [Errno 6] Device not configured
Z-Wave Error Z-Wave 3.95 static controller might be disconnected
Z-Wave Error silently retrying serial connection every 5.0 seconds
Interface Failure lost connection with interface
Z-Wave connected to Z-Wave 4.54 static controller interface on /dev/cu.usbmodem1411 (firmware 1.01)
Z-Wave found module included in controller with no matching device (missing or disabled): 007 - Relay Power Switch
lanbrown wrote:I have two sticks and after I add a few devices I go and pull the working stick, and make a backup copy of it. I keep multiple iterations of the backup. This way if something happens I can always restore on the other and if the backup is corrupted I can go to a previous backup and then just include the devices added since that backup. It only takes a few minutes to perform a backup. This seems like a much better way than hoping than performing a backup and restore will work after it gets into a weird state.
siclark wrote:matt (support) wrote:? Indigo only auto-disables device communication when the interface is restarted (or physically removed/reinserted, or Indigo Server restarts) so I would hope that after running the script the devices work okay; at least until the next server or interface restart. If that isn't the case, then how are things failing specifically?
Is there a difference between auto disables, and disables? If not Indigo definitely disables my devices without any restart of anything. Unless it restarts the interface by itself?
colin_d wrote:matt (support) wrote:I've been looking at what Indigo can do to workaround the problem, including not having it disable devices even though the Z-Stick is handing us bad information on most of the nodes. So after running the script to re-enable the devices does everything work okay for a while? Indigo only auto-disables device communication when the interface is restarted (or physically removed/reinserted, or Indigo Server restarts) so I would hope that after running the script the devices work okay; at least until the next server or interface restart. If that isn't the case, then how are things failing specifically?
Thanks guys for your quick response. Yes after being re-enabled the devices would work okay, at least until the interface decided to get scrambled again.
For your info it all started with errors like this:
- Code: Select all
17 Nov 2018, 16:33:38
Z-Wave Error send getVersion failed after 9 attempts
Z-Wave Error restarting serial connection in 5.0 seconds
matt (support) wrote:siclark wrote:matt (support) wrote:? Indigo only auto-disables device communication when the interface is restarted (or physically removed/reinserted, or Indigo Server restarts) so I would hope that after running the script the devices work okay; at least until the next server or interface restart. If that isn't the case, then how are things failing specifically?
Is there a difference between auto disables, and disables? If not Indigo definitely disables my devices without any restart of anything. Unless it restarts the interface by itself?
Communication can be manually disabled in the UI, but the auto disables should only occur (I think) when the Z-Wave Controller communication initialization is occurring. So that would be on server restart, Z-Wave interface reload (menu or other), or if there is a Z-Wave USB communication failure bad enough that Indigo forces a reload of the interface.
The next time you notice devices are disabled take a look at the Event Log and see if you can trace back to exactly when the problem occurred (it'll be higher up than the lines logging Indigo disabling devices but include those too) and copy/paste those lines into a reply for me.
Users browsing this forum: No registered users and 11 guests