On Sun, 28 Jul 2013, Sancho wrote: >> Very interesting. Well, that is good to know. Unfortunately, I haven't >> seen the Logitech software issue any sort of changes to the devices, ie, a >> "SetDevices" message, so therefore I don't know how to do it (yet). >> Additionally, we haven't reverse engineered the EZHex format, so we don't >> know how to create one. The way that mhgui works is by sending >> configuration changes to the Logitech server (ie, add device, delete >> device, etc) and then downloads the compiled EZHex file from the server. >> Then we write it to the remote using concordance/libconcord. > > How about using a high-end model of the Logitech Harmony remotes, i.e. one > that allows setting the delays (e.g. inter device delay) by the end-user, in > order to find out the message structure and content needed to configure > those delay changes in the device profile stored on the Logitech server? > > Is my understanding correct, that the high-end models use more or less the > same message interface to Logitech servers like the low-end models do (i.e. > Harmony 300)?
Yes - I would suspect that the high-end models would use the same messages as the low-end models. I will be investigating this as I continue adding support for the Harmony Link, which is the only high-end "remote" that I have access to. Hopefully the Logitech software allows making these changes for the Link, and I will be able to see how to do it. Scott ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
