Logitech's stance on local APIs


#22

I’m surprised. how a company can cripple your product!!
This used to be a great company, but…
دوربین مداربسته


#23

Hi everyone,

I am on the Harmony team with Ian and Todd.

I’m pleased to announce that our latest Harmony mobile app update, version 5.6 for iOS and Android, along with Harmony firmware version 4.15.250, will begin rolling out this coming Friday, February 15, 2019. With this mobile app update and latest firmware release, XMPP is now an option in the Harmony mobile app. By default, Harmony firmware will keep XMPP disabled, but via this new setting, motivated users can enable it.

For those of you already using the special firmware version 4.15.210 with XMPP access, when your hub upgrades to 4.15.250, you can easily re-enable it by following the instructions posted here. You will not need to use the cumbersome firmware update process as you did in December. If you experience any issues, please let us know in our forums, We’ll do our best to respond quickly and sort it out.

Going forward, future firmware updates will respect your current setting, so this should be a one-time action on your part.

For anyone interested, on March 3rd, an engineer from cyber security firm Tenable will be giving a talk where he will describe his experience exploring potential vulnerabilities with Harmony Hubs. It was Tenable’s research and communication with us that originally led us to the potential risks.

Happy Home Automating, everybody :slight_smile:


Update to accessing Logitech Harmony Hub’s local API via XMPP
#24

Thanks for the heads up Will. I’ve put the message on our social media to spread the word. https://twitter.com/home_assistant/status/1096187885726982144


#25

This is great news! Restores my faith in the Logitech brand!


#26

So, how is it going to be in HA now? Since websockets is in use now, will we have an option to use xmpp again?


#27

I have an issue with Harmony hub (4.15.250), I have the following error in HA (0.87.1) log:

ERROR (MainThread) [aioharmony.hubconnector] XXX.XXX.X.X: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: ',
ERROR (MainThread) [aioharmony.hubconnector] XXX.XXX.X.X: Unable to retrieve HUB id

#28

I’ve also had this issue since 87. I was running the official harmony firmware and even replaced it with the developer firmware and it has not fixed the issue


#29

Same issue here Harmony hub (4.15.250), HA (0.87.1)

> Platform harmony not ready yet. Retrying in 30 seconds
> Unable to connect to HUB
> Unable to retrieve HUB id
> Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '

Was working on developer firmware


#30

I have this errors, too.
But I haven’t enable the harmony component?!? Why do I have this error???

#remote:
#  - platform: harmony
#    name: Wohnzimmer
#    host: 192.168.2.66

Log:

019-02-18 18:20:15 ERROR (MainThread) [aioharmony.hubconnector] 192.168.2.66: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-18 18:20:15 ERROR (MainThread) [aioharmony.hubconnector] 192.168.2.66: Unable to retrieve HUB id
2019-02-18 18:20:15 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-18 18:20:15 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 150 seconds.

#31

identical problem here, this morning everything was fine…


#32

Have you guys enabled it in .250… See here

you can easily re-enable it by following the instructions posted here


#33

I have. It did not fix the issue. It’s not actually required to do this either. HA works just fine without the developer firmware. I went ahead and installed it anyway just to see if it would make a difference,which it did not.


#34

But the developer firmware was not needed, it was only needed if you wanted to make of the old xmpp version from 86.3 and before, after 86.4 HA was using websockets…

So maybe now in 250 , maybe it’s the websockets that’s causing issues?? So if you are on 250, just load the harmony.py file as a custom component from an older ha release, so if that works, then xmpp is workin again… So then we know it’s a websockets issue


#35

btw, the ones on 250 firmware, was this done automatically ? so was the develoer 210 automatically updated to 250 version? or you guys did this manually?


#36

It was done automatically.


#37

crap :slight_smile:
then its best to load an older harmony , enable xmpp again in your harmony app
this one for example : https://www.dropbox.com/s/avnwkrc1om11bt6/harmony.py?dl=0
place that .py file in this folder config\custom_components\remote
that should work , then you are using xmpp instead of websockets
because if you guys are on 87.x release and 250 firmware, then its an issue with websockets, not XMPP


#38

Ahh makes sense (kinda). I was not on 250. I was on the most current version of firmware when I first had the issue. Might have been 87.0. Then I updated firmware to .250 just in case. I thought (looks like I might be wrong) the both web sockets and xmpp worked. Either way. I’ve seen these errors with both versions of the harmony firmware. I don’t think it’s a harmony issue


#39

Old harmony.py file works with the new firmware with xmpp enabled. Thnx.


#40

for the moment a good woraround? so that concludes that there is an issue with websockets now for users with 86.3 and above?


#41

Seems so. Mine upgraded this evening and now my automations have broken. Enabling xmpp doesn’t help