OK, so here's what I know so far.

The Logitech software doesn't do much with the Link over USB other than 
configuring its WiFi.  It doesn't send a configuration file like is done 
for the traditional remotes.  It looks like there may be a way to upgrade 
its firmware, though.

As best as I can tell, the "configuration" file doesn't actually even get 
sent to the Link itself (unless it is getting it via WiFi, but I don't 
think it is).  It appears that all of the configuration is sent to the 
mobile device, which kind of makes sense, I suppose - just make the Link a 
dumb WiFi to IR convertor.

So, it looks like the bulk of supporting this device is going to be more 
SOAP / GUI stuff.  :(

Scott

On Sun, 16 Jun 2013, David Callahan wrote:

> Yes. Putting the buttons on your phone or tablet instead of a remote. You
> probably had the phone in your hand Anyway! Right? I'll dig around in the
> code and see what I can see.
> 
> Scott Talbert <s...@techie.net> wrote:
> 
> Unfortunately, there isn't a whole lot of documentation, especially since 
> all of this is reverse engineered.  A skin ultimately represents an 
> individual model of remote (e.g., Harmony 650), whereas there may be 
> multiple remotes that use the same Architecture (Arch).  You can see the 
> Skins and Arches defined in remote_info.h.
> Isn't what a novel idea for a remote?  The Link?
> On Sun, 16 Jun 2013, David Callahan wrote:
> Even without specifics, I think I understand arch 17, but what does skin 82
> mean? Can you point me to the documentation for this project, where that
> sort of thing is hopefully explained? If not, can you send me whatever raw
> data there is so I can start documenting it myself?
> <
>  br
> />And isn't that a novel idea for a remote?
> Scott Talbert <s...@techie.net> wrote:
> OK, so got the Link.  As I suspected, it speaks the 'MH' protocol, which 
> is good news as we won't have to completely reverse engineer a new 
> protocol.  It is Skin 82 and Arch 17 (a new Arch).
> Now, just to figure out how this thing works...and how it interacts with 
> the web service.
> On Wed, 12 Jun 2013, David Callahan wrote:
> Packing it up. Where shall I send it?
> Scott Talbert <s...@techie.net> wrote:
> Okay, I read the user manual and now I understand a lot better what this 
> thing is.  :)
> Unfortunately, it's probably going to take a significant effort to get it 
> working, and I don't see how I can do it without physically having access 
> to the device.  If you are willing t
> o loan
> me one, I am willing to work on 
> it, though.  I'm not sure how long it will take - it could be a month or 
> mo
>  re, but
> you can have the device back whenever you want.
> Scott
> On Wed, 12 Jun 2013, David Callahan wrote:
> I'm not using it right now. Just came in yesterday. I took it to work to try
> to program it, but the security system kicked it out. So then I started
> googling ways to do it directly from my OS.
> <
> br
> />And I admit I actually mentioned the model numbers to try and make sure yo
> u
> realized what this thing was without asking a horribly insulting sounding
> question.
> I spent $65 on this and it's just a paperweight until we make it work. I'm
> willing to do whatever we need. But I'd really like to have it back again in
> the end.
> Scott Talbert <s...@techie.net> wrote:
> Oh, wait.  I was thinking that this was actually a remote control itself, 
> but now I am seeing that it is not
> .  This
> may be a bit more challenging to 
> support than I thought, depending on what actually gets programmed in
>  to 
> it.
> On Wed, 12 Jun 2013, David Callahan wrote:
> MH remote?
> And for the record, I think there are two versions of this floating around
> now. Either that, or the other product number is just to differentiate the
> one that comes with a remote control. This is the 915-000144. The newer one
> is 915-000194. Ju
> st
> thought I'd mention it for documentation purposes.
> Scott Talbert <s...@techie.net> wrote:
> OK, it sounds like it might be an MH remote.  I'll send a patch l
> ater
> for 
> you to try.
> On Wed, 12 Jun 2013, David Callahan wrote:
> I don't have windows, but it wants silverlight AND a special harmony plugin 
> from myharmony.com.
> From the kernel ring buffer:
> [593011.490607] usb 2-1.2: new high-speed USB device number 12 using ehci-pc
> i
> [593011.593257] usb 2-1.2: New USB device found, idVendor=046d, 
> idProduct=c126
> [593011.593264] usb 2-1.2:
>  New USB
> device strings: Mfr=1, Product=2, 
> SerialNumber=0
> [593011.593268] usb 2-1.2: Product: Harmony Remote
> [593011.593272] usb 2-1.2: Manufacturer: Logitech
> From lsusb:
> Bus 002 Device 012:<
> br
> />ID
> 046d:c126 Logitech, Inc.
> On 06/12/2013 11:18 AM, Scott Talbert wrote:
> OK, cool.  If it uses a brand new protocol, it would probably be a lot
> faster to have physical access to the device, but if it is just another
> variant of an existing, it probably won't be too hard to add support.For
> starters:
> 1) When you use it with Windows or Mac OS, do you use
> members.harmonyremote.com, or do you use www.myharmony.com (the
> Silverlight app)?
> 2) What does 'lsusb' show for it?
> Scott
> On Wed, 12 J
> un
> 2013, David Callahan wrote:
> Yes! And I'd be happy to mail it off to some
> one if
> I can have it back
>  , or
> gather whatever debugging info you can tell me how to get, or give you 
> shell
> access to a computer that it is plugged in to. Whatever works. (hint: 
> mailing
> stuff costs money, don't pick that one unless it's R
> EALLY
> better than the
> other options)
> On 06/12/2013 10:44 AM, Scott Talbert wrote:
> On Wed, 12 Jun 2013, David Callahan wrote:
> Is the Harmony Link ever going to be supported by this project? I don't
> even
> know if it actually has anything in common with the rest of the series
> besides its n
> ame.
> It will if someone either donates one to the developers, or someone who
> owns own is willing to provide USB debug traces, so we can enabl
> e
> the
> functionality.
> Do you own one?
> Scott
> ____________________________________________________________________________
> This SF.net email is sponsored by
> Windows:
> Build for Windows Store.
> http://p.sf.net/sfu/windows-dev2dev
> ____________________________________________________________________________
> concordance-devel mailing list
> concordance-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/concordance-devel
> ____________________________________________________________________________
> This SF.net email is sponsored by Windows:
> Build for Windows Store.
> http://p.sf.net/sfu/windows-dev2dev
> ____________________________________________________________________________
> concordance-devel mailing list
> concordance-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/concordance-devel
> ____________________________________________________________________________
> This SF.net email is sponsored by Windows:
> Build for Windows Store.
> http://p.sf.net/sfu/windows-dev2dev
> ____________________________________________________________________________
> concordance-devel mailing list
> concordance-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/concordance-devel
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
> ____________________________________________________________________________
> This SF.net email is sponsored by Windows:
> Build for Windows Store.
> http://p.sf.net/sfu/windows-dev2dev
> ____________________________________________________________________________
> concordance-devel mailing list
> concordance-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/concordance-devel
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
> ____________________________________________________________________________
> This SF.net ema
> il is
> sponsored by Windows:
> Build for Windows Store.
> http://p.sf.net/sfu/windows-dev2dev
> ____________________________________________________________________________
> concordance-devel mailing list
> concordance-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/concordance-devel&lt;
> a>
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
> ____________________________________________________________________________
> This SF.net email is sponsored by Windows:
> Build for Windows Store.
> http://p.sf.net/sfu/windows-dev2dev
> ____________________________________________________________________________
> concordance-devel mailing list
> concordance-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/concordance-devel
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
> ____________________________________________________________________________
> This SF.net email is sponsored by Windows:
> Build for Windows Store.
> http://p.sf.net/sfu/windows-dev2dev
> ____________________________________________________________________________
> concordance-devel mailing list
> concordance-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/concordance-devel
> 
> 
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel

Reply via email to