August 3Aug 3 I'm on 1.0.1 using to get to my ecobee. I see there is a 2.0.17 standard version but when I click update nothing happens. I already paid the $30 for v 1.0.1
August 9Aug 9 I have the exact same issue. I purchased the Standard Perpetual license, but there is no option to update to 2.0.17.......@Jimbo.Automates, is that a bug or is it necessary to uninstall the entire plugin and re-install it?
August 16Aug 16 Sorry for the delay, didn't get a notice that I was mentioned.@Michel Kohanim & @bmercier , This was due to changing the plugin name after it was released. Do these guys have to repurchase and ask for a refund?
Tuesday at 05:06 PM3 days On 8/15/2026 at 11:37 PM, Jimbo.Automates said:Sorry for the delay, didn't get a notice that I was mentioned.@Michel Kohanim & @bmercier , This was due to changing the plugin name after it was released. Do these guys have to repurchase and ask for a refund?A repurchase should not be necessary.But an uninstall and reinstall may be required. PG3 is sensitive to the plugin name. But licenses are based on the nsid. So unless the nsid changed, a repurchase is not necessary.If the nsid changed somehow, I can update the licences.
Wednesday at 03:07 PM2 days Solution Thanks @bmercier So for those having the issue you will have to delete and reinstall, sorry about that but we had to change the name of the plugin and early adopters got bit.
Thursday at 07:23 PM1 day I can confirm delete and reinstall let me upgrade. I just had to re-pair my Ecobee thermostats with HomeKitHub and the rest of my setup was back up and working fine. Edited Thursday at 07:23 PM1 day by Freddy Kilowatt
Create an account or sign in to comment