Okay, update to version 0.6.10
You can just await like before:
await BL.init({homey:this.homey});
Also the decode is the same, only an NPM update needed
I am pushing BLL now, so everyone should be updated in 4 hours.
All changes are in the NPM package, so you can push when you want after updating the NPM.
The donāt need the latest BLL for this to work correctly, since, when there is an error, it will just resolve and hide it, not raise an error or anything.
New chapter in my journey through some of your apps.
Because I was experiencing some issues with Device Capabilities and Homey 2023 I made some adjustments to my AVDs. I have disabled the corresponding flows and have set all devices with reflection and response in the AVD.
Now I run into a setting on some devices where I donāt yet know what to enter (I donāt understand it yet but hope to understand that soon).
For example, with one of my Eufy sensors I have to enter a BLL expression and Iām stuck on that for now.
Well, you are setting a Textfield, but the capability is a Boolean (Contact Alarm).
Either create a Yes/No field with those settings, so you do not need a BLL expression, or do you want some special text?
B:LL expression is required when the reflect capability is different then the Fieldtype.
I needed to get the current hour as a tag so i started to build a app and added other things I thought could be useful for someone.
I made a lot of flowcards.
It looks like this
I can add a flowcard to retrieve date-parts as number.
It wouldnāt need this many flowcards, just a pickerlist with all the date-parts that BLL supports.
Please use the topic for Homeyscript testers, I would recommend discussing issues with topic starter Jeroen (Athom), and read the updated docs posted there, thanks!
But, while I looked it up already, this might fix it, Johan; it seems like apiPut has to be replaced by put