On Sat, 20 Jul 2013, Sancho wrote: > I just noticed that I forgot to call mhgui with the "--use-local-wsdl" > option in my last test. Therefor I retried and got a different exception > this time: > >> mhgui --use-local-wsdl > No handlers could be found for logger "suds.umx.typed" > Traceback (most recent call last): > File "/usr/local/bin/mhgui", line 614, in OnSetupWatchTV > self.resources.page_setup_watch_tv.SetRemote(self.remote) > File "/usr/local/bin/mhgui", line 1516, in SetRemote > inputNames = mhMgr.GetDeviceInputNames(device.Id) > File "/usr/local/share/congruity/mhmanager.py", line 611, in > GetDeviceInputNames > features = self.GetUserFeatures(deviceId) > File "/usr/local/share/congruity/mhmanager.py", line 628, in GetUserFeatures > deviceIds) > suds.TypeNotFound: Type not found: 'b:AbstractIRAction'
It is complaining that it can't find AbstractIRAction in the XSD, which is defined in user_feature.xsd. Can you confirm that you have a user_feature.xsd in the directory where you installed congruity (probably /usr/local/share/congruity based on what I see above). If it is there, then perhaps there is something different about how the messages are formed. Maybe if you tell me what devices (TV, etc) and I can add them to my account - maybe that will allow me to reproduce 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