Event log question (restore device)

[ergodic]

A question about what I see in the event log when I do a restore device on a motion sensor. The restore seems to proceed and complete OK, but the last line (see below) is always a "*Failed writing" on a device that isn't involved in any of the MS scenes (there's only one).

 

The MS is ID "11.9d.28" - a sensor in a downstairs shower which keeps the lights on. What the ISY seems to be trying to write in that last line is ID "0e.72.25" - an upstairs lighting switch, at least if I understand it correctly. I've verified that the ISY doesn't show any scene connection between these two devices. The event log behavior is consistent if I repeat the restore.

 

This is not the only device that does this on a restore, there are others. All seem to complete OK, it is just the event log that is puzzling to me. I'm trying to clear up some troublesome problems that I was thinking were a wonky PLM or comm issues, and it still might be. But I currently think this is some sort of link or database corruption. So I'm asking so I can understand if this is something normal or indicative of some problem.

 

I've listed the last several lines of the event log for this restore in case they help, but it is just that last line that I'm really wondering about.

 

***

 

Thu 01/28/2010 10:52:40 AM : [standard-Direct Ack][0E.72.25-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Thu 01/28/2010 10:52:40 AM : [iNST-ACK ] 02 62 0E.72.25 0F 28 0F 06 SET-MSB(0F)

 

Thu 01/28/2010 10:52:49 AM : [iNST-ACK ] 02 62 0E.72.25 0F 28 0F 06 SET-MSB(0F)

 

Thu 01/28/2010 10:52:59 AM : [iNST-ACK ] 02 62 0E.72.25 0F 28 0F 06 SET-MSB(0F)

 

Thu 01/28/2010 10:53:00 AM : [iNST-SRX ] 02 50 0E.72.25 0E.DC.6D 23 28 0F SET-MSB(0F)

 

Thu 01/28/2010 10:53:00 AM : [standard-Direct Ack][0E.72.25-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

 

Thu 01/28/2010 10:53:00 AM : [iNST-ACK ] 02 62 0E.72.25 0F 2B F2 06 PEEK (F2)

 

Thu 01/28/2010 10:53:04 AM : [E 72 25 1 ] Link 1 : 0FF0 [A2010F380EFF1B01] *Failed Writing [A2010F380EFF1B01]

[Michel Kohanim]

ergodic,

 

This is a feature .

 

Here's the reason:

In 2.7.9 and above (in PRO), there a feature called Batch mode. Batch mode basically lets you do everything offline and then have ISY push it out for you. ISY maintains the history of all the bits/bytes that could not be written and will retry them ANY TIME you click on the batch button again. So, in short, ISY has a hard time communicating with E 72 25 1 and it keeps retrying every time you are not in batch mode.

 

In non-PRO versions, this is done every time there's a change to any other device. If you really don't want ISY to keep trying, simply disable the device.

 

The bottom line is: your whole network should be in synch with ISY. If not, ISY keeps trying unless you advise it otherwise (by disabling the device).

 

With kind regards,

Michel

[ergodic]

Amazing, as always. You guys have been busy.

 

BTW, I understand the new, little "Writing" green arrow, but what's the one that looks like "1011" or "ION"?

[Michel Kohanim]

Hi ergodic,

 

The 1011 icon means that there are PENDING writes for the device. That icon stays there till ISY writes all the pending info into the device.

 

With kind regards,

Michel

Amazing, as always. You guys have been busy.

 

BTW, I understand the new, little "Writing" green arrow, but what's the one that looks like "1011" or "ION"?