How did you get te bearer token, Peter? @Peter_de_Vos
So uneanable itš
Will do
Weirdā¦
Please restart the app and see if that fixes that problem. Does a āself-deleting-flowā work?
Iāll have a look at it, although I doubt that I can upload a new buildā¦ For now you can only disable 2FA I guess
Thanks,
So I disabled 2FA, logged on, got a bearer token and restarted the app.
I made a flow ādelete messages older than 1 dayā.
It worked, but Homey got unrespinsive and the Timeline Manager got paused by Homey.
Restarting both Homey app and Timeline app solved it for now.
And Iāve 2FA is enabled again after this.
It works, but the notification wonāt dissapear yet (set to 1min, now 5mins have passed)
Category pick works here, but messages donāt disappear.
No hurries!
Cheers
Iām afraid I made a bit of a design flawā¦ I donāt āsaveā the token, just hold it in memory. Only the credentials are stored, not the token itself. So every time the app (or Homey) is restarted it needs to obtain a new token, but with 2FA enabled that will fail.
Iāll change that in the next version.
I never experienced Homey becoming unresponsive. I did experience that sometimes the deletion of flows wasnāt shown in the mobile app. After restarting the mobile at they were gone. The webapp does show the deletions immediately; I guess that does a pull, while the mobile app uses a websocket
1 Like
The flow works
Perhaps I donāt understand the issue, but apps donāt require any credentials to be able to use the Web API. Only the correct permission (in app.json).
Hi,
Iām using the REST Api because otherwise I donāt seem to have the right persmission to do certain stuff. My app.json includes the homey:manager:api permission, but I canāt get it to work, but maybe Iām missing something, the documentation isnāt what one hoped for.
this.homey.api.get(āhttp://127.0.0.1/api/manager/notifications/ownerā)
gives me an āmissing_permissionā error, while
var response = await fetch('https://' + cloudId + '.connect.athom.com/api/manager/notifications/owner', { method: 'GET', headers: { 'Authorization': 'Bearer ' + bearerToken } })
gives me a a nice list. But that way I need the Bearer Token, and for that it needs the credentials.
If you know of a way to do it without the REST Api please let me know, that would make things much easier.
1 Like
Apologies, it looks like Athom has decided that SDKv3 apps arenāt allowed to use the Web API ānativelyā anymore, which is still allowed for SDKv2 apps (like HomeyKit).
This is the code Iām using (in SDKv2):
const { HomeyAPI } = require('athom-api');
ā¦
const api = await HomeyAPI.forCurrentUser();
Thanks. Thatās too bad then!
After having a quick look I doubt that I will be able to get de 2FA working. Peterās memory problem can undoubtedly be solved/prevented, but without 2FA working a lot of people canāt use it, of need to disable it every once in a while.
Talking on Slack to the Athom devs, they seem to suggest that it should still work. Iāll let you know if we can solve the issue.
2 Likes
Thanks, I can really appreciate it!
I got the Web API working again from an SDKv3 app, but sadly, notifications are off-limits using it 
Wouldnāt it be possible to make the app available in the Community Store?
2 Likes
Hi Uwe,
That is of course a possibility, but as I am using API keys that can only be used for development purposes it doesnāt feel right.
Iāll wait for Athom to reply on my request for my own API keys. If they deny that request I might reconsider though. 
In the meantime Iāll look at the issues from both Peters.
3 Likes
