How to reduce the excessive debug logging in the new Alexa plugin( was Re: more info on the Alexa plugin)

[James Sentman]

Yes, sorry, it starts up in debug mode, so it’s just out of sync with XTension. I was so excited at having gotten it to work that I sent it out to you all before I even commented out the hard coding of setting debug mode to true :) 

You can make that turn off by turning on and then off again debug mode in XTension itself. You’ll still see some lines when the alexa device is actually polling for a light status and it does that periodically which I”m pretty sure it never did before either. That is just one line though and not the entirety of every UPNP packet that is received. So give that a try until I can get a new build of it out with everything.

Or… if you’re feeling very adventurous you can open the plugin code in your favorite text editor (no promises that text edit in the OS won’t just mess up everything so download the free version of BBEdit or use nano in the terminal or something. Same Finder dance you used to install the beta plugin in the first place. Control click on XTension in the finder, select Show Package Contents, open the Contents folder and then the Resources folder and then the Plugins folder and finally the “alexasudo.isf” folder. Inside there you want to edit the “alexasudo.py” file. Make a copy of it in the finder first just in case this makes everything stop working :)

Search for the line that begins “XTension.debugMode” it’s line 2015 if your text editor supports that. Change it from 

XTension.debugMode = True

to

XTension.debugMode = False

or just put a # in front of it to comment it out like:

#XTension.debugMode = True

Which is probably the best way as the silly language is case sensitive and if you write false instead of False or if you change the indenting then it won’t run the next time ;) Then re-enable the interface. That will do the same thing and it will stick between restarts unlike manually turning off and back on the debug logging. If the log spits errors rather than a successful startup message you can just throw away the file you edited and change the name of the copy you made in the finder back to alexasudo.py and try again. 

Or just wait a day or so until I can do another beta with that all taken care of. I’m going to be out of touch shortly here for most of the day and then for much of Sunday as well but will be around in the evenings and checking email.



> On Feb 21, 2020, at 6:08 PM, Steve Blethen <ssblethen59 at gmail.com> wrote:
> 
> I’m getting pretty much the same thing.  I figured James has this Beta version stuck in debug mode so he can see under the hood if things break.  I’ll admit its hard to ignore all the activity in the log.  I’ve found that pushing the power button on the monitor helps ;>
> 
> -steve
> 
> 
>> On Feb 21, 2020, at 4:35 PM, BobsXTension at comcast.net <mailto:BobsXTension at comcast.net> wrote:
>> 
>> 
>> On 2/21/20 4:49 PM, James Sentman wrote:
>>> Honestly I wouldn’t be at all surprised if there are a few new gotchas in the new Alexa software. I had to make several changes to the original code to get it to work even after I had the port 80 stuff working. Keep any notes of odd things you observe and I’ve added this one to the list of stuff I should test. It’s much pickier about certain values that were previously ignored for instance. Lots has changed in it.

Thanks,
 James


James Sentman                       http://www.PlanetaryGear.org		http://MacHomeAutomation.com




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20200222/6fece57c/attachment.html>