On Wed, 19 Jun 2013, Chain von den Keiya wrote:
>>> I am new to Concordance and Cungruity, but not new to the Harmony Remotes.
>>>
>>> I am using a 1100eu, and I tried your software with it. I open the
>>> Connectivity.EzHex with it, just as intended, and then I get a new file:
>>>
>>> LatestFirmware.hfw
>>
>> Concordance doesn't support firmware upgrades for the 1100, but you
>> probably should not need that. It should support configuration updates,
>> though. Did you select "upgrade firmware" when you went to
>> members.harmonyremote.com? Or did the website somehow force you to
>> download the firmware?
>>
>> Also, what does "concordance -iv" show when you run it?
>>
>> Scott
>
> Hi,
>
> Yeah I read that, and I didn't want to. The website just forces it upon me,
> and that's where I get stuck. I just selected "Update Remote" - but maybe that
> was wrong?
>
> chain@richBOOK ~ $ concordance -iv
> Concordance 1.0
> Copyright 2007 Kevin Timmerman and Phil Dibowitz
> This software is distributed under the GPLv3.
>
> Requesting identity: 100% done
> Model: Logitech Harmony 1100
> Skin: 63
> Firmware Version: 7.6
> Firmware Type: 0
> Hardware Version: 0.2.14
> External Flash: 2 MiB - 01:49 AMD Am29LV160BB
> Architecture: 11
> Protocol: 11
> Manufacturer: Logitech
> Product: Harmony 1100
> IRL, ORL, FRL: 0, 0, 0
> USB VID: 046D
> USB PID: C11F
> USB Ver: 0000
> Serial Number: {015C9B94-EEEE-EEEE-EEEE-EEEEEEEEEEEE}
> {0410AE26-A47C-4EBF-85E1-D32D5AFE0F34}
> {29BEA602-B662-4C8F-9C51-D297F698AFA7}
> Config Flash Used: 7897699% (78 of 1 KiB)
>
> Success!
>
> ...Which is, AFAIK, the newest firmware available. So, I am kind of lost why
> it wants me to upgrade the firmware at all.
Nope, "Update Remote" is what you want. That should give you a
configuration file, not a firmware file. I wonder if perhaps we are
reporting the firmware version incorrectly to the website and it is
thinking that we need to upgrade the firmware.
Do you mind recompiling libconcord with debug enabled? This should just
involve adding CPPFLAGS="-D_DEBUG" to your ./configure command and
recompile. Then if you can re-run the part where you process the
Connectivity.EzHex file, it should print out the HTTP message that it is
sending. It might have your HTTP cookie in there - you can delete that if
you want.
------------------------------------------------------------------------------
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
