homey app run
while having a Cloud Homey selected, the Homey CLI will automatically guide you to install all the required tools. It will then run the app on your computer and connect it to Homey Cloud."platforms": [ "cloud" ]
or "platforms": [ "local", "cloud" ]
.platforms
flag to your App, Driver and Flow manifests.platforms
and connectivity
properties:connectivity
are:lan
cloud
ble
zwave
zigbee
infrared
rf433
rf868
App
, Driver
or Device
instances:App#onUninit()
, Driver#onUninit()
, and Device#onUninit()
. These methods will be called when your app is destroyed so you can perform cleanup in them. For example:setInterval()
and setTimeout()
. You should not call these directly, instead you should use this.homey.setInterval()
or this.homey.setTimeout()
. These act exactly the same as their regular counterparts but will automatically be cleared when your app is destroyed..catch(this.error);
Device#setCapabilityValue()
which returns a promise. In order to prevent unhandled promise rejections you should add .catch(this.error)
.homey:app:<appId>
permissions. Likewise the homey:manager:api
permission that allowed an app to use ManagerApi and the Homey Web API is not allowed./
is different. On Homey Pro, /
is your app's directory, and on Homey Cloud, /
is the Linux root.require('./assets/foo.js')
or path.join(__dirname, 'myfile.svg')
.homey:manager:api
permission is not allowed to be used.