I am seeing client errors occurring after updating PowerLink links? Everything seems to work properly.

Code: Select all

Sep 21, 2009 4:55:58 PM
  PowerLinc          Linking - entered discovery linking mode (240 seconds)
  PowerLinc          Linking - syncing PowerLinc links (address 11.F1.F6)
  PowerLinc          Linking - comparing local and powerlinc links
  PowerLinc          Linking - .  missing: remote link not found for new link 10.DD.6C group 01 (adding remote link)
  PowerLinc          Linking - compare complete
  PowerLinc          Linking - . . adding: INSTEON plc link to controller 10.DD.6C, flags 03, group 01, data 00 00 FF
  PowerLinc          Linking - sync complete
  PowerLinc          Linking - PowerLinc links updated
  PowerLinc          Linking - sending id request for device information
  PowerLinc          Linking - sending id request for device information
  PowerLinc          Linking - received id request response from 10.DD.6C
  PowerLinc          Linking - initializing remote device "MBR Bed Lamp E (slave)" (address 10.DD.6C, firmware version 3.7)
  PowerLinc          Linking - . . . read: default on brightness 100, ramp rate 0.5 seconds
  PowerLinc          Linking - initialize complete
  PowerLinc          Linking - syncing remote device "MBR Bed Lamp E (slave)" (address 10.DD.6C, firmware version 3.7)
  PowerLinc          Linking - syncing all links
  PowerLinc          Linking - . . adding: PowerLinc responder for group 1 (inserting new link at 0FF8)
  PowerLinc          Linking - comparing local and remote links
  PowerLinc          Linking - compare complete
  PowerLinc          Linking - sync complete
  PowerLinc          Linking - device 10.DD.6C links updated
  PowerLinc          Linking - exited linking mode
  Sent INSTEON       "MBR Bed Lamp E (slave)" status request (received: 0)
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.

I'm not able to reproduce the problem. Does it happen every time? And what version of OS X is your Indigo client running under?

Not all the time, just occasionally, and then only on a neighbors installation, never on mine. He has a new Mac Mini running 10.6, I don't think he has installed 10.6.1.

The error should be pretty benign and is on the client side only. The server has already updated the links at the point when the error above was logged. Keep an eye on it and let me know if it goes away after he upgrades to 10.6.1. Thanks!

Will do. BTW, the problem of reporting client error is complicated by the fact that the client error log is not persistent (at least not as far as I know). Is there any way to cause client errors (which are inevitably exceptions) to be automatically saved to file like on the server, or does this happen already and I just missed it?

Actually, the client side errors like this are never logged to the server log file. They only show up in the Event Log window.

Right. Sorry if I wasn't clear. This should be filed under possible future product enhancements: I was wondering if there should be a client side error log file. Perhaps with an option to use it or not.

berkinet wrote:I am seeing client errors occurring after updating PowerLink links? Everything seems to work properly.

Code: Select all

Sep 21, 2009 4:55:58 PM
  PowerLinc          Linking - entered discovery linking mode (240 seconds)
  PowerLinc          Linking - syncing PowerLinc links (address 11.F1.F6)
  PowerLinc          Linking - comparing local and powerlinc links
  PowerLinc          Linking - .  missing: remote link not found for new link 10.DD.6C group 01 (adding remote link)
  PowerLinc          Linking - compare complete
  PowerLinc          Linking - . . adding: INSTEON plc link to controller 10.DD.6C, flags 03, group 01, data 00 00 FF
  PowerLinc          Linking - sync complete
  PowerLinc          Linking - PowerLinc links updated
  PowerLinc          Linking - sending id request for device information
  PowerLinc          Linking - sending id request for device information
  PowerLinc          Linking - received id request response from 10.DD.6C
  PowerLinc          Linking - initializing remote device "MBR Bed Lamp E (slave)" (address 10.DD.6C, firmware version 3.7)
  PowerLinc          Linking - . . . read: default on brightness 100, ramp rate 0.5 seconds
  PowerLinc          Linking - initialize complete
  PowerLinc          Linking - syncing remote device "MBR Bed Lamp E (slave)" (address 10.DD.6C, firmware version 3.7)
  PowerLinc          Linking - syncing all links
  PowerLinc          Linking - . . adding: PowerLinc responder for group 1 (inserting new link at 0FF8)
  PowerLinc          Linking - comparing local and remote links
  PowerLinc          Linking - compare complete
  PowerLinc          Linking - sync complete
  PowerLinc          Linking - device 10.DD.6C links updated
  PowerLinc          Linking - exited linking mode
  Sent INSTEON       "MBR Bed Lamp E (slave)" status request (received: 0)
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.
  Error (client)     _broadcastSelectionChanged() caught exception: NSRangeException -- Cannot remove an observer <NSKeyValueObservance> for the key path "AddressValUI" from <NSCFDictionary> because it is not registered as an observer.

Look for something with a name that contains the string "AddressValUI" in his database - I suspect he's got some character (probably an @) in there that's causing Cocoa Bindings to freak out. And what version is he running? I fixed a bug in 4.1 that fixed a problem with some characters.

berkinet wrote:Right. Sorry if I wasn't clear. This should be filed under possible future product enhancements: I was wondering if there should be a client side error log file. Perhaps with an option to use it or not.

Um, probably not. Generally, when someone sees a client error like that it's a bug, so as soon as they report it we track it down and fix it.

jay wrote: And what version is he running? I fixed a bug in 4.1 that fixed a problem with some characters.

4.1.b4. I'll check his database next time I see him. Thanks.

This problem should be fixed in Indigo 4.1.1 (not yet available).

Indigo 4.1.1 is now available and should fix this problem.