Activity for Scott Talbert
-
Scott Talbert committed [df351f] on Code
GIRR test cases
-
mhgui: Add GIRR Import
-
Fix progress gauge with Python 3.10+
-
Set minimum page height in MHGUI to ensure new buttons are visible
-
New release 21
-
Update README with latest tested versions
-
Support wxPython >= 4.1.0
-
Segfault on s390x with 5.4.1 during docs build
-
On logging in with Google and Facebook, yes I could probably implement that (possibly using a webview) but it may take some work. On the Edit Favorite Channels issue, yes, that's unfortunately known work that needs to be done for certain remotes: https://sourceforge.net/p/congruity/issues/37/ On version numbers, yes, I should probably do a new release with the login changes.
-
Handle invalid credentials and members.harmonyremote.com accounts
-
Okay, I've updated mhgui's login process to match the latest official software. Please pull the latest from git and give it a try. If it still doesn't work, I have some additional ideas/questions. When using the official software, you're using "Login with Email" and not "Login with Google" or "Login with Facebook" right? In other words, you're using a Logitech account, not a Google or Facebook account. If you're still getting that "Not Found" error, let me know.
-
Update login process to match latest official software
-
Wireshark won't help as the communications will be encrypted. Unless there is a way to inject your own root certificate and MITM yourself with Wireshark? But I have a way to do it using Fiddler. I was able to capture the new communications. I just need to find some time to work on it more. Maybe tonight.
-
Okay, I will try to reproduce the problem by using the official software. Also, I noticed that the official software seems to be using a different method for logging in now. I will try to convert mhgui over to use that. Probably won't be able to look into this until Sunday or Monday though.
-
If you're definitely sure that you have a valid myharmony.com username and password (and can log in using the official software), then there may be some case that I'm not handling. Let me know.
-
Okay, so I'm not sure why you're having trouble logging in. I'm able to log in fine. Are you sure you have a myharmony.com account? I was able to reproduce the issue with creating a new account - it turns out that is an issue with Python 3.9+. I fixed it in git. If you want, you can pull the latest code from git or patch your local copy with the change I made. Then you should be able to try creating a new account.
-
Fix account creation on Python 3.9
-
Actually, there may be some remotes for which it is possible to convert from using members.harmony to myharmony.com. The 650 might be one of those. However, I don't think MHGUI would be able to handle transitioning a remote (at least not as currently implemented). You would probably have to use the official software to transition it, after which you could probably use MHGUI.
-
If your remote works with members.harmonyremote.com, then it won't work with MHGUI. It's an either-or thing. It's mainly the newer remotes that work with MHGUI (remotes that use the myharmony.com website).
-
So, it seems clear to me that the problem is in concordance (or lower in the stack). Would you be up for building a debug version of concordance?
-
Actually, yes you are right. The "concordance -r" does ignore the result of the reboot so given that it is waiting for ~60 seconds it does appear that it is just waiting for the maximum number of retries before giving up.
-
Okay, so it sounds like that's roughly Debian Stable, minus udev of course. The "concordance -r" test should actually be useful because it should be waiting for the remote to come back after rebooting. The fact that it seems to be able to talk to the remote fine is interesting. It is a little suspicious that it took ~60 seconds though.
-
My first thought is that this situation should probably work, although I don't know if anyone has ever tested concordance/congruity with mdev before. What model of remote are you using? Also, what Linux distribution are you using? And can you tell me the versions of concordance/libconcord, hidapi, and libusb that you're using? Also, just to simplify the problem, can you plug in your remote and try just a reboot from concordance with "concordance -r" and see if that works or fails?
-
Okay, my bad. I completely failed to apply the patch properly. Sorry about that. Now that I've done so, the zoom box is now visible when using X11, but unfortunately not when using Wayland.
-
I tested with 0d93b4c5c3a365d5278d7d930634b7ecc1c36cc0 on a gtk3 build. Unfortunately, it doesn't seem to resolve the problem.
-
Zoombox doesn't appear with wxterm under GTK3
-
I was talking about in your first reply where you said you ran 'concordance -i'. :P Can you also try running 'concordance -iv' several times repeatedly and see if it works sometimes and sometimes not?
-
Sounds like a permissions issue and that your udev rule is not working.
-
You didn't perhaps run 'concorcordance -i' as root, did you? You could try running the connectivity test with the concordance binary and see what happens. For example 'concordance -v Connectivity.EZHex'
-
Remove Python subpackages
-
Fix gcc6 narrowing conversion by Kentaro Hayashi (Closes: #811758)
-
Remove Python subpackages (Closes: #937321, #948502)
-
Add ButtonClientAction which is needed for Harmony 950
-
mhgui crasher after login(Type not found: 'a:Sub')
-
Thanks for the report. Should be fixed now.
-
Update to match latest website changes
-
To close the loop, it looks like 475fb4e8b2f4444d1d7b406ff3a7d21bc89a1e6f broke it. Going to stop the discussion here as this clearly isn't a rEFInd problem.
-
Looks like it broke between 4.7 and 4.8rc1. Started the git bisection.
-
I didn't mean that the hardware broke...I meant that that kernel's support for said hardware broke. :-)
-
Yeah, I can try to narrow down when this hardware broke. The 18.04 upgrade comes with 4.15.x (ie, I can't boot 4.15.x) so it broke somewhere between 4.4 and 4.15.
-
This seems like it may be a kernel problem on this system. I was able to sort of work around the problem by doing the following: 1) Install Ubuntu 16.04.1 from USB (which does boot) 2) Install refind from Rod's PPA 3) Upgrade to Ubuntu 18.04 However, the system can't seem to boot from the 18.04 kernel. I had to go back to the 16.04 one. So it seems this system may unfortunately be broken in later kernels.
-
Hi, I'm using rEFInd 0.11.4, which I've installed on a Mac Pro (mid 2012) using MacOS. I then installed Ubuntu 18.04.3. When rEFInd loads, I can see the Ubuntu installation and select it, but it hangs on the screen which says: rEFInd - Booting OS Starting vmlinuz-5.0.0-34-generic Using load options 'ro root=UUID=<uuid> initrd=boot\initrd.img-5.0.0-23-generic'</uuid> Any ideas on what I can do to fix this? I can see the ext4 driver has been installed. Thanks, Scott
-
My Harmony 350, I don't save my activity.
-
Yes, 18-4 is quite old.
-
Does the Harmony 350 even have Activities? From looking at a picture of it, it doesn't appear to have Activities, only a Watch TV button. So, MHGUI shouldn't be allowing you to add activities, but it does?
-
OK, I'll have a look later.
-
Do you get a traceback when this happens? You may need to run mhgui from terminal, if you are not doing this already.
-
Any updates on plans for supporting Python 3? Fedora is planning to retire Python 2 soon.
-
Fix #68 -- add `PrioritizedDeviceCapabilityList` to XSD
-
suds.TypeNotFound: Type not found: 'b:PrioritizedDeviceCapabilityList'
-
Thanks for your MR. I didn't see it until I had already fixed it in a slightly different way.
-
Update to match latest website changes
-
So, you are trying to log into mhgui with a Google account, is that correct?
-
Just to make sure I understand what you're requesting... You are talking about buttons like "TV" and "DVD" correct? And you want to have more than one TV assigned to a remote, and you want to be able to choose which TV the remote will send commands to when you press TV?
-
mhgui:Login failed:sslv3 alert handshake failure
-
mhgui error
-
Closing due to no further response from reporter.
-
trying to make congruity work
-
Closing due to lack of response from reporter.
-
Update schema
-
Thanks for the report. Done.
-
Fixes to match latest website changes
-
Yes, 1.4.4 works fine without the patch. Thanks.
-
Python 3 / wxPython 4 (Phoenix) Support
-
Update schemas as of 18 September 2018 (#1)
-
Python 3 Support
-
Python 3 support has been added. Closing.
-
Update schemas as of 24 August 2018
-
Yes, if you want to run mhgui with Python 3, then you will need all dependencies to support Python 3 . Yes, you will need to install concordance 1.3 to get the Python 3 version of the libconcord bindings.
-
It looks like you are using all Python 2 dependencies, but you installed congruity/mhgui with Python 3. Reinstalling congruity with Python 2 should resolve the problem, or switch your dependencies to Python 3. The error you are seeing is because you don't have a Python 3 version of wxPython installed.
-
New release 20
-
Fix install fails with Python 2.7
-
Update release date in Changelog
-
Modernize Python installation (replace Makefile with setup.py)
-
Release bump and preparation for release
-
Add support for Python 3
-
Add support for wxPython 4 (Phoenix)
-
Switch to use https when talking to SourceForge / downloading configs
-
trying to make congruity work
-
Have you ever configured this remote with the website before, or is this the first time? Are you sure this remote works with the older website (members.harmonyremote.com)? At least some (and possibly all?) Harmony 650's must be used with the newer website, and thus you must use mhgui instead. Can you try running mhgui?
-
Add missing XSD for UpdateMultipleResult (for IR learning)
-
MHGui fails to communicate with server (reopen)
-
Glad to hear it is working for you.
-
You have to go to: http://members.harmonyremote.com/EasyZapper/
-
Does "concordance -iv" recognize the remote? It sounds to me like this is one of the older remotes, so you will probably need to use members.harmonyremote.com. I would give that a try.
-
Okay, now that you mentioned creating accounts I can see the problem. The version in Debian/Ubuntu has a problem with creating accounts. Existing accounts work fine, which is why I didn't see any problems there. This has been since fixed in git. I would suggest just using the version from git. Do this: git clone git://git.code.sf.net/p/congruity/code congruity-code cd congruity-code ./mhgui
-
Based on what you are telling me, you aren't even getting close to talking to the remote, so udev is irrelevant. Don't worry about that for now. Can you please run "dpkg --status congruity" and provide the output? Also, can you please run "mhgui --suds-debug 2>&1 | tee log.txt", attempt logon, and provide the output?
-
Please make sure you are really using the Ubuntu package (reinstall it??). The official package works for me on Ubuntu 16.04. Don't change any udev rules. That's not related to the problem. Also, you shouldn't need to run mhgui as root.
-
Okay, so it looks like the website changed in the past couple of days. That was probably the first problem you saw. If you go back to the Ubuntu package (18-4) it should work now.
-
Fixes to match latest website changes
-
https://sourceforge.net/p/congruity/code/ci/master/tree/
-
Version 18 from Sourceforge definitely won't work. I thought the 18-4 package in Debian/Ubuntu was working, so I'll check that out later. You can either use git master, or if the Ubuntu package isn't working, I can probably provide a fixed one in a PPA.
-
What version of mhgui are you using? Unfortunately, the login fixes are not in a release, so you will have to use git master. I am intending to make a new release soon as I'm adding wxPython 4 and Python 3 support.
-
Can you please provide the output from the command line when you're seeing this failure?
-
Fixes to match latest website changes
-
I don't see any problems on Ubuntu 16.04.
-
Also, it looks like there might be multiple problems(?): the SSL error but you are also seeing a traceback from the password storage stuff. Are you selecting "Store username and password?" If so, can you try without that?
-
No, the URLs in the XSDs are not real URLs so that shouldn't be the problem. I can't reproduce on Fedora. I will try on an Ubuntu 16.04. I don't think I have a 14.04 instance around anymore - I worry that it might be due to its old SSL version?
-
Fixes to match latest website changes
-
suds.TypeNotFound: Type not found: 'a:IsNewUser'
1 >
