Harmony Hub FW 4.15.206
Answered
Hi folks. We are aware of the feedback from some Harmony Hub customers about firmware version 4.15.206.
We recently released a firmware update for Harmony hub-based remotes. A few consumers have told us they are experiencing issues with certain configurations of the these remotes. We will follow up soon with more details.
Thank you for your patience.
-
Watch the threats and torches and pitchforks everyone - they're working on something, a company the size of Logitech can't move on a dime like you'd like them to. Actually, for a company the size of Logitech, this has moved quite rapidly IMHO. My only disappointment so far is the continued lack of response to support tickets with any feedback - still understandable but disappointing.
-
@John-Erik Christensen? a company of this size will immediately know if its a bug or intentional. In no way shape or form is this post mentioning they will fix the issue and restore API access. It is left open ended for a reason. We both know a company of this size has an internal ticketing system and any project manager can say "yes we closed up port 5222" or "no this is a bug we have to fix" Until they come out and say its a bug we should continue to remain upset and disappointed. This post is just buying them time while they think about how to word the response. Honestly I hope they prove me wrong but until they do we should remain vocal. I don't think Logitech wants another Harmony Link issue on their hands. I am surprised Arstechnica hasn't written an article about this yet.
-
Ok.. Ok... OK...
I know people are upset, I can't say I'm not annoyed loosing 2 hours to figuring out what was wrong, then downgrading and blocking....
Please be civil! Making statements in anger before we know anything is lost energy. Save that energy for when we have a response and a plan on what will be done to resolve this issue.
Right now I see two ways this can move forward, both require quick action:
- Revert the change that removed local control, but fix whatever reason it was removed in the first place, be that a security issue or a policy issue, there by returning the functionality a good amount of people relied on.
OR
- Work rapidly with the open source communities affected by this unannounced change to develop an appropriate local control solution.
This is all predicated, of course, on often and meaningful communications with us, the users. @William Wong? please keep us up to date.
For those users that want to do something, submit support request, retweet and make your voice heard. The more people that make their voice heard just creates more awareness of the issue.
-
@djchronz just because they know it's intentional or not, they may not know if the consequences of it were intentional or not. And just because somebody knows why it was done doesn't mean that information gets out to support channels quickly - especially as the decision making and technical staff may have been made overseas and all of the feedback occurred overnight for them; it's 3:42 AM at headquarters, for instance.
-
@Tony Roman? Funny bumping into you here ... !
I've downgraded my hub and blocked several of the domains suggested. myharmony.com was nearly impossible I think ... it seems to be a DNS round-robin between many, many different IPs.
Has anyone devised a way to block the updates but still retain access to the iPhone/Android app which relies upon cloud synchronization? Sadly I use both local and app-based control so I'm stuck with half-functionality no matter what I do. It's a long-shot but I was hoping the updates get pushed from somewhere other than the master cloud-control program (let's call it MCP for short;) I fight for the users!
-
@Eric Schoeller? If you run your own DNS server, you can block based on individual sources at the DNS level, so the fact that it's round robin is irrelevant. You can just route *.myharmony.com to oblivion for particular hosts (127.0.0.1 is a favorite). Also remember you'll need an A and a AAAA record if you have IPv6 service.
-
@John-Erik Christensen? That's a good point. I can just blackhole the DNS queries from the IP of the hub itself. Right now I'm just blocking individual IPs at the firewall level for the hub's IP.
I am worried that the only way to block the update, but allow other traffic necessary for the app through would be doing some deep level of packet inspection, if that were even possible, I'd imagine it's all wrapped up in SSL.
Has anyone rooted the hub itself? I bet I could block updates locally...
-
In case this helps anyone, I downgraded my Harmony Hub this afternoon and blocked its IP from accessing the internet. Since then, over the last six hours I've logged it attempting to reach the following IP addresses: 54.165.126.61, 54.236.3.168, 54.236.3.169, 54.236.3.170, 100.26.13.108
-
@William Wong? Please note that who you see here right now is most likely those that are more involved with the development. Home Assistant automation for example has already made an announcement to its user community about this breaking change. Hence the number of customers impacted is going to be a lot more then what would be seen here.
-
@William Wong? : @Erik Hendrix? is right. There may only be a few users on your community forum, but if you want a real idea of the impact on users, you'd need to also look at the user forums for HomeAssistant, HomeBridge, HomeSeer, Domoticz, Vera, Smarthings, the user's tweeting @logitech on twitter and the reddit users in /r/smarthome, /r/logitechharmony, /r/homeautomation /r/homeassistant. I'm sure I'm leaving more than a few groups out, but that should begin to give you an idea as to the size of this issue.
-
@William Wong? @Erik Hendrix? @Tristan Caulfield?, the Harmony team should have already been aware of these communities and known how big of a disruption this would cause before even considering to implement this change.
Edit to add, if Logitech is just discovering these communities, I will point out that it would be greatly appreciated if Logitech took into consideration their concerns and ideas. I would assume hobbiests like this make up a decent portion of their customers because I can’t imagine average users figuring out how to use this product.
-
I love being trivialized by support as 'A few consumers'
Own 3 hubs which are now bookends for my purposes.
The correct way to handle this.
Revert all users to previous firmware.
Publish websockets API and inform users that you are depreciating XMPP
Remove XMPP in 6-12 months
This is the proper way to support your paying users!
Your disregard for paying customers and their time is astounding.
Please sign in to leave a comment.
Comments
489 comments