> Yup - the thing I did first was what I expected was most important - config > update. Can you test that?
Just started playing with concordance yesterday, so this may be a bit basic question. Looking at the man page, looks like --write-config filename is what you are asking me to test. Can you point me in the direction of how to create that file? ( with --dump-config not working, I don't have an example ) > I don't have a 900, but I"d be curious to see what happens when you get your > new one. Me too. I'll report back. > Since you mentioned it doesn't show up in lsusb, the device is fault > enough for the OS to not recognize it, which means there's no way concordance > can find it. Sorry about the formatting of the last email, it was very hard to read. Not sure what happened to it as I wrote it in plain text mode. Anyway, lsusb does in fact recognize the remote. ---------------------------------------- > Date: Sun, 20 Nov 2011 01:06:00 -0800 > From: p...@ipom.com > To: concordance-devel@lists.sourceforge.net; grad...@hotmail.com > Subject: Re: [concordance-devel] 890/900 testing > > On 11/19/2011 08:26 AM, Brendan Grady wrote: > > > > Hi all, Figured I'd share some of my experiences with building/testing the > > zwave_work_branch. Apologize for the long email - most of it is just debug > > output for the devs. > > Thanks for your testing. Replies inline. > > > First tried building the concordance/libconcord zwave branch on Windows > > using VC++. It would not compile and I think it is mainly to do with the > > libzzip dependency. Couldn't find a good tutorial on building libzzip in > > windows and not being a C++/Visual Studio developer ( mainly Java/Eclipse > > ), didn't want to go down the rabbit hole. > > Yeah, I don't own a windows box, I have no idea how much of this does or does > not work. > > > -vi works > > Awesome. > > > -c is not supported -f is not supported > > Yup - the thing I did first was what I expected was most important - config > update. Can you test that? > > > -r did not actually reset the remote ( but the output listed success ) > > Yeah, these things don't reboot on a reset command. As far as I can tell, it's > some sort of "internal reset" not an actual hardware reset. > > > Running zwave_work_branch with a 900 > > I don't have a 900, but I"d be curious to see what happens when you get your > new one. Since you mentioned it doesn't show up in lsusb, the device is fault > enough for the OS to not recognize it, which means there's no way concordance > can find it. > > > -- > Phil Dibowitz p...@ipom.com > Open Source software and tech docs Insanity Palace of Metallica > http://www.phildev.net/ http://www.ipom.com/ > > "Be who you are and say what you feel, because those who mind don't matter > and those who matter don't mind." > - Dr. Seuss > > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
