On Fri, 26 Jul 2013, Sancho wrote: > I have now tested your latest correction. It works, but now I get an exception > on a different unknown info element of the GetUserFeatureResult message > (namely "ActionId", sub-element of "AbstractIRAction" ?). > Here is the full Python traceback: > > suds.TypeNotFound: Type not found: 'b:ActionId' > > <b:AbstractIRAction i:type="b:IRDelayAction"> > <b:ActionId>3</b:ActionId> > <b:Order>1</b:Order> > <b:Delay>1000</b:Delay> > </b:AbstractIRAction>
It looks like this was the issue. I hadn't seen this 'IRDelayAction' before so it wasn't in the XSD. This must be something else that Logitech just added to your account, because I don't think it was in the previous capture you sent. I pushed another commit - let me know if this fixes the latest traceback. > The problem of adding a delay between the PowerToggle commands of the > "TechniSat" and the "Sony-Fernseher (2)" could be solved in the meantime. I > was right that the proper delay setting for such an use case is the socalled > InterDeviceDelay (IDD). The IDD is applied during activities / macros BEFORE > the programmed commands are sent to the corresponding device. That means I > had to ask them to set the IDD of the "Sony-Fernseher (2)" device to 5000 > milliseconds to get a 5 seconds pause between the PowerToggle command sent > to the "Technisat" device and the one sent to the "Sony-Fernseher (2)" > programmed on the AUX key. > > So these delay values are not fixed, at least Logitech has the means to > change them. I'm not too familiar with the whole concept of the Harmony > programming procedure using Logitech servers, but if it is possible to > create or manipulate the content of the "GetDevicesResult" message and then > compile this modified settings to EZhex-format, they it should be also > possible to configure this without the help of Logitech. 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. 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
