It is working good now! Thank you! I am on UI5 and the latest Harmony Hub firmware of 206. I went to Apps… Develop Apps… Luup files… Upload Files… Browse… Checked Restart Luup after upload… Go. No issues yet, I will post this feedback in both threads.
Stay tuned, Reed. And my apologies for the disruption. We will announce something soon. I?m really sorry for the disruption.
On Dec 21, 2018, at 7:38 AM, Reed Simpson reed@chelseagroup.com wrote:
Bracken P. Darrell
You recently updated the firmware in Harmony hubs to block any access from the Vera controller, thereby causing me to lose trust in your company policies relating to the Harmony produce line.
I have used Harmony products for many years ? Now you have given me a reason to look elsewhere.
Thanks Rene for a quick fix that actually works, saved me from downgrading all 7 of my hubs. You’re one of the few app developers that keeps their plugin up-to-date, need more people like you.
Thanks for the quick fix! I can’t get it working however on openluup. I’ve replaced the lua file in “/home/test/vera/cmh-ludl”, but I still get the message:
Please make sure you uploaded the lua file at the beginning of the thread correctly. The version number should change to 2.28b. Make sure you reloaded luup.
Please make sure you uploaded the lua file at the beginning of the thread correctly. The version number should change to 2.28b. Make sure you reloaded luup.
Cheers Rene[/quote]
Hi Rene,
I’ve uploaded the file correctly. I’ve looked at the permissions. When I go to the plugins section in AltUI and click on the file, it shows me the new version. I’ve reloaded luup several times, but it does not refresh to the new version somehow. At the device variables it keeps saying version 2.19. I have deleted all L_Harmony.lua files that were in openluup and uploaded it again, but no success.
Any suggestions? It seems like a caching issue of some sorts or maybe file corruption. I’d rather not uninstall the plugin.
Please make sure you uploaded the lua file at the beginning of the thread correctly. The version number should change to 2.28b. Make sure you reloaded luup.
Cheers Rene[/quote]
Hi Rene,
I’ve uploaded the file correctly. I’ve looked at the permissions. When I go to the plugins section in AltUI and click on the file, it shows me the new version. I’ve reloaded luup several times, but it does not refresh to the new version somehow. At the device variables it keeps saying version 2.19. I have deleted all L_Harmony.lua files that were in openluup and uploaded it again, but no success.
Any suggestions? It seems like a caching issue of some sorts or maybe file corruption. I’d rather not uninstall the plugin.[/quote]
I truly have no idea why it is not being picked up. I just posted the updated plugin in the ALTUI App store so you can also take that route to update.
If I update from the Alt store - will that replace the one I have installed nw and keep the same devices numbers etc - or will I need to “start over”?
I make extensive references to the harmony devices in PLG - so I would not want to re-do all of that.
[quote=“Chelseagroup, post:13, topic:200280”]If I update from the Alt store - will that replace the one I have installed nw and keep the same devices numbers etc - or will I need to “start over”?
I make extensive references to the harmony devices in PLG - so I would not want to re-do all of that.[/quote]
Should all be kept as is. There is a chance a new device instance is created on the No Rooms page. Just delete that and reload.
I have 2 harmony hubs. One was no longer taking external commands. I assume it got update to the 206 firmware. Downloaded the patch from here, Went to apps → Develop–> and uploaded to vera. it uploaded as L_Harmony.lua ( .lzo is a compressed archive). Restarted Vera and it worked like a charm.
Well done Rene !
Just got home and upgraded my three harmony hubs to the 210 version (dev version) which gets XMPP back. Is there any advantage to moving to web socket?
As a user it does not matter what interface. The websocket one has a tiny bit less overhead and for me as a coder is simpler to use.
I have updated the plugin to the websocket one now so you do not need to do any workaround. At the same time it seems that Logitech has stated that the XMPP version will become the local one to use for third party integration. I’ll believe that when they make the API details public. Maybe then it is time to switch back.