Any idea why?
I added the permission “homey:manager:api” in the new version, I’m affraid it is the reason for it!
The user need to validate something?
remark: the screen captures show the date of 5th October for both versions, but 0.7.4 is almost one month old. 1.1.4 is based on 1.0.0 which introduced the new permission, and it’s almost 5 days old already.
Ok so done is done, but still I need the users to switch to the new version.
Can I pubish a version which doesn’t require the permission to force them to update “automatically”?
I undersntand it is not possible to make this permission “optionnal”, it’s all or nothing.
=> I more and more feel like Ahtom BV is playing the same way as Steve JOBS => decide what the users have right to do or not … I hate Apple because of that
Between the “inconsistentcy of the SDK, local API and web API”, the impossibility to handle dynamic enum values, and this permission constraint, I start to be very very very annoyed …
I spent so many hours to workaround the SDK constraints already, it would be enough to fix the SDK itself … let’s not talk about their documentation …
The permission “api” is required because of the inconsistency in the SDK, local API and web API of Homey.
Compared to local API, Web API require the bearer token, but both require the api permission.
You need local API to retrieve all the zones of the home
You need Web API to:
Change a device name
Change a device zone
Delete a device
That’s why I introduced this permission requirement.
So currently, I end up with several issues:
Old users tested and gave up the ESPhome application before I even published anything
It would be nice for them to take a new look They may like it
Old version had a memory leak (big)
They may have given up, it would be nice to onboard them again
Some users are on the old Driver (either old version or new version of the app)
I want them to switch to the new driver (Wizard), it will enhance their experience
How I’m planning to handle the mess:
1/ Have a notification sent every morning (8am?)
=> You are using an old version, upgrade!
=> You are using old driver, switch!
2/ Put a warning on all concerned devices!
=> Same message
The messages themself will be worked out, and should be translated in all languages.
In a perfect world, it would be nice to include a link (to the user guide) in the messages, but I don’t think it is possible.
How is this even going to work? You’re going to publish a new version of your app with the permissions removed (otherwise it won’t get updated automatically and your users won’t be getting the notifications), and then what? Where will they be able to find the new app version that you want them to upgrade to?
Not until you can be fairly sure that everybody has updated to it, otherwise you’ll run into the exact same issue. But without publishing 1.x your daily notifications are pointless.
It all seems a bit convoluted to me, to be honest.
No, your situation is that your users are running an older version that doesn’t get automatically updated to the new version because the latter has different permissions.
I’m not saying that it’s impossible for a Homey to be running an older version, I’m saying that you cannot explicitly (get your users to) install a particular version of an app unless that version is either the current live or test version.
