1-wire success, sort of (and info on XTension crash)

Rob Lewis rob at whidbey.com
Thu Nov 20 12:14:13 EST 2014


Well, there’s the dang log, frankly where I thought it was supposed to be. Its icon was just positioned way outside the visible window area. It’s odd that Spotlight didn’t find it, though. (Can you refresh my memory on how to freeze the log window so it doesn’t keep scrolling?) 

Haven’t examined the startup debug log in great detail, but I did find one curious thing: I seem to have at least one unit with “phantom” ON and OFF scripts. That is, the flags in the Master List indicate that the scripts are present, but when I try to edit them the window is empty. I tried inserting a single comment line and then using “select all” and deleting it, but the flags stay on. 

And the debug log says this about the unit: 
"The was an error getting the compiled script data, attempting to use the backup”
and right after that: 
“error in OSAScript.save at index”

Whut?


On Nov 20, 2014, at 8:40 AM, James Sentman <james at sentman.com> wrote:

> 
>> On Nov 20, 2014, at 10:16 AM, Rob Lewis <rob at whidbey.com> wrote:
>> 
>> 1. I do have 3 XTension units that were created by your “create units for Barix” script but don’t have any physical sensors. I guess I should just delete those units? 
> 
> that probably explains that, but they can cause no trouble except spamming your log file.
> 
>> 
>> 2. Around 1AM this morning, the Barionet apparently stopped responding. First time I’ve ever seen that happen. Disabling and re-enabling the interface in XTension didn’t fix it, but rebooting the B-50 (from its web interface) did. 
> 
> Maybe want to check it's power supply or other connections something is causing it pain.
> 
>> 
>> 3. I wanted to check the log regarding problem #2, but I can’t find XTension’s current log file! The previous ones (cut once a week) are in the “Logs” folder, but I’ve searched and can’t find the active one. XTension’s Log window only shows the last hour or so. 
> 
> Current log is not in the Logs folder, but should be just alongside the application inside it's folder. In the same folder as the Logs folder.
> 
> Thanks,
> 	James
> 
> 
> James Sentman                       http://sentman.com		http://MacHomeAutomation.com
> 
> 
> 
> _______________________________________________
> XTensionList mailing list
> XTensionList at shed.com
> http://shed.com/mailman/listinfo/xtensionlist



More information about the XTensionList mailing list