No energie information in app dashboard

[HermanHSlagman]

I have installed the app, on/off switching works fine.
I knew that the connected device is consuming power, but I don't see this in the consuming dashboard. The "energiemeter", "ontvangen" and the "energie" levels or not filled (they were zero).

[kasteleman]

Hello, Do you have solarpanels connected because “ontvangen” counts if energy is put back and not consumed. Also no values visible in insights for the other? Regards, Martin Op di 12 feb. 2019 om 21:04 schreef Herman H Slagman < notifications@github.com>

…

I have installed the app, on/off switching works fine. I knew that the connected device is consuming power, but I don't see this in the consuming dashboard. The "energiemeter", "ontvangen" and the "energie" levels or not filled (they were zero). [image: screenshot_20190212-210102] <https://user-images.githubusercontent.com/20515850/52664514-825f3700-2f09-11e9-8488-8ab33ac3e49f.jpg> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFpiKMx-0d_hl-i4vPik27WNJKQuxxVlks5vMx5mgaJpZM4a388Y> .

[HermanHSlagman]

Hi Martin,

I'm consuming electricity with the Plug HA. My (small) electric car is connected.
Please let me know what you mean with "Also no values visible in insights for the other?", I don't understand this, Sorry.

Regards, Herman.

[kasteleman]

Hi Herman, I suspect that the reportlistener isn’t registered and therefore no reports come in. I can’t test it on the newer firmware because i’m In 1.5.13 So have to figure out how to troubleshoot this one. Are you familiar with cli app install? Regards Martin Op za 16 feb. 2019 om 11:36 schreef Herman H Slagman < notifications@github.com>

…

Hi Martin, I'm consuming electricity with the Plug HA. My (small) electric car is connected. Please let me know what you mean with "Also no values visible in insights for the other?", I don't understand this, Sorry. Regards, Herman. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFpiKKgBCzQGbcMKx7AUtHZH6civFFEKks5vN98_gaJpZM4a388Y> .

[HermanHSlagman]

Hi Martin,
Are you familiar with cli app install? Sorry, I'm not. I don't understand what you mean with: I suspect that the reportlistener isn’t registered.
I use Homey version 2.xx

Regards, Herman.

[kasteleman]

Hi Herman, In order to get the reports coming in, some items in the driver must be successful otherwise no data is shown. There are several reports for different apps that this was working for their apps in the older firmware but don’t function anymore since the new 2.x.x firmware. I can not upgrade to 2.x.x at this moment because then some apps won’t work at this moment. So that’s why I can not test with 2.x.x firmware. I only have 1 Homey.......so I was hoping that you’re familiar with the cli method because that could give me some extra debuginfo! Regards, Martin Op di 19 feb. 2019 om 21:58 schreef Herman H Slagman < notifications@github.com>

…

Hi Martin, Are you familiar with cli app install? Sorry, I'm not. I don't understand what you mean with: I suspect that the reportlistener isn’t registered. I use Homey version 2.xx Regards, Herman. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFpiKAZvuc-RDpTKBrQ5FiPw4U6PMv1Yks5vPGVXgaJpZM4a388Y> .

[HermanHSlagman]

I'm sorry Martin, I'm not a programmer and can't help you with debugging this issue.
I have a look at wiki about cli method, but I don't understand the information about my Homey and my the app.
If I can do simple things for you (as an advanced user), I will help you with pleasure.
Regards, Herman.

[kasteleman]

Don’t be sorry Herman. No need for that. I will have a look at it this weekend but it can take some time. Hope you understand. Regards, Martin Op di 19 feb. 2019 om 22:16 schreef Herman H Slagman < notifications@github.com>

…

I'm sorry Martin, I'm not a programmer and can't help you with debugging this issue. I have a look at wiki about cli method, but I don't understand the information about my Homey and my the app. If I can do simple things for you (as an advanced user), I will help you with pleasure. Regards, Herman. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFpiKPB_Vi9x4zbdYA_pBMlIofdlnxscks5vPGmRgaJpZM4a388Y> .

[HermanHSlagman]

I understand, success Martin with solving the issue.

[MischaKluin]

I experienced the same problem.
The Plug functioned fine with Homey firmware 1.5, but after the update of the Plugwise Zigbee Support apk to v 1.0.1 the Plug started to appear buggy. I did send the Plug back to the supplier and contacted Plugwise about the issues I was experiencing:

onoff was communicated propely as soon as there was an event
meter_power was communicated only once; right after the install
meter_received was not communicated anymore (Plugwise firmware is bad: wrong variable type...)
measure_power was communicated only once; right after the install
alarm_poweroverload is still communicated on a regular base (once every 10 minutes?)

Now it seems it is not due to a bad Plug, but to the new App...

I downloaded some old versions of the app (20180426 and 20190125) and installed those by cli, but no improvement. The value for measured_power is communicated once, just after the installation.

[MischaKluin]

As Plugwise decided for a wrong version of the variable for meter_received (max is 256) they also moved the decimal point: their 0,255 kWh is 0,0255 kWh in reality. after reaching this maximum the counter resets...
This will be solved in the firmware update they should release in April.

Also strange is the naming of the variables measured by the Plug:
meter is used for energy, so values measuring energy in (k)Wh
measure is used for power, so values measuring power in W
I would suggest:
meter_power energy_(in/ delivered/ import)
meter_received energy_(out/ received/ export)
measure_power power_now
The implementation of measure_power was correct, as the value for reversed power (by e.g. PV) was displayed as a negative number

[kasteleman]

First thing: how do you plan to get the new firmware on the device? Homey does not support ota. Second item: I suspect the reportlisteners not to be registered correctly during driverinitializing However I currently can’t test it for the 2.x.x firmware nor debug it, because I’m on 1.5.13 and can not upgrade due to other apps installed on my Homey that will stop working after a upgrade. However judging the suggestions you made, you are familiar with cli method of running applications? If so please provide the output of Athom app run. Regards, Martin Op do 21 feb. 2019 om 17:02 schreef MischaKluin <notifications@github.com>

…

As Plugwise decided for a wrong version of the variable for meter_received (max is 256) they also moved the decimal point: their 0,255 kWh is 0,0255 kWh in reality. this will be solved in the firmware update they should release in April. Also strange is the naming of the variables: meter is used for energy, so values measuring energy in (k)Wh measure is used for power, so values measuring power in W I would suggest: meter_power energy_import meyer_received energy_export measure_power power_now The implementation of measure_power was nice, as the value for delivered power (by e.g. PV) was displayed as a negative number — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFpiKIAmVoxMZjp8GsOOBBk5U8cCFb40ks5vPsMlgaJpZM4a388Y> .

[MischaKluin]

Onderstaand de output van de app versie van 2018-04-26
Ik zal later ook de output van de laatste versie posten.

— Profile your app's performance at https://go.athom.com/app-profiling?homey=5aa8f8b205eff5043791a40d&app=com.plugwise.zigbee
─────────────── Logging stdout & stderr ───────────────
Warning: Trying to access Homey.env.HOMEY_LOG_URL but the environment variable has not been set!
2019-02-21 18:29:55 [log] [PlugwiseZigbeeApp] init
2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ZigBeeDevice has been inited
2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ------------------------------------------
2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] Node: 6b5a86ea-ad4d-48e4-b27d-f4e1f88f3c8d
........
2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- acActivePowerOverload : 0
2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ------------------------------------------
2019-02-21 18:29:56 [err] [ManagerDrivers] [Plug] [0] registerAttrReportListener() -> error could not configure attrReport_0_genOnOff_onOff { Error: data is not defined
at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190)
at JSON.parse ()
.....
2019-02-21 18:29:56 [err] [ManagerDrivers] [Plug] [0] registerAttrReportListener() -> error could not configure attrReport_0_seMetering_currentSummDelivered { Error: data is not defined
at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190)
....
at _combinedTickCallback (internal/process/next_tick.js:142:11)
at process._tickCallback (internal/process/next_tick.js:181:9)
(node:8915) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)

AthomAppRun 20180426.txt

[MischaKluin]

2019-02-21 18:34:56 [log] [ManagerDrivers] [Plug] [0] [dbg] Polling clusterId 'haElectricalMeasurement' for capabilityId 'alarm_poweroverload'

[kasteleman]

Thx fir the quick reply. The output confirms there is a issue with the reportlisteners: Plug] [0] registerAttrReportListener() -> error could not configure attrReport_0_seMetering_instantaneousDemand { Error: data is not defined That was working in the 1.5.x firmware. Have to look in to that. Regards, Martin Op do 21 feb. 2019 om 18:33 schreef MischaKluin <notifications@github.com>

…

— Profile your app's performance at https://go.athom.com/app-profiling?homey=5aa8f8b205eff5043791a40d&app=com.plugwise.zigbee ─────────────── Logging stdout & stderr ─────────────── Warning: Trying to access Homey.env.HOMEY_LOG_URL but the environment variable has not been set! 2019-02-21 18:29:55 [log] [PlugwiseZigbeeApp] init 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ZigBeeDevice has been inited 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ------------------------------------------ 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] Node: 6b5a86ea-ad4d-48e4-b27d-f4e1f88f3c8d 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] - Battery: false 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] - Endpoints: 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] -- Clusters: 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- zapp 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- genBasic 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : genBasic 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- zclVersion : 1 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- appVersion : 4 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- manufacturerName : Plugwise 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- modelId : 160-01 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- powerSource : 1 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- genIdentify 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : genIdentify 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- identifyTime : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- genGroups 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : genGroups 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- nameSupport : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- genScenes 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : genScenes 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- count : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- currentScene : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- currentGroup : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sceneValid : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- nameSupport : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- genOnOff 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : genOnOff 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- onOff : 1 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- genAlarms 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : genAlarms 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- genTime 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : genTime 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- genOta 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : genOta 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- seMetering 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : seMetering 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- currentSummDelivered : [ 0, 20 ] 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- currentSummReceived : [ 0, 0 ] 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- status : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- unitOfMeasure : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- multiplier : 1 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- divisor : 10000 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- summaFormatting : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- demandFormatting : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- meteringDeviceType : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- instantaneousDemand : 76 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] --- haElectricalMeasurement 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- cid : haElectricalMeasurement 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- sid : attrs 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- measurementType : 1 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- totalActivePower : 73 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- powerMultiplier : 4294901760 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- powerDivisor : 4294967040 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- acAlarmsMask : 4 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ---- acActivePowerOverload : 0 2019-02-21 18:29:56 [log] [ManagerDrivers] [Plug] [0] ------------------------------------------ 2019-02-21 18:29:56 [err] [ManagerDrivers] [Plug] [0] registerAttrReportListener() -> error could not configure attrReport_0_genOnOff_onOff { Error: data is not defined at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190) at JSON.parse () at jsonToObject (/opt/homey-client/system/helpers/jsonfns.js:1:1083) at function.e.data.map.e (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1379) at Array.map () at HomeyClient._onMessage (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1372) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:762:12) at _combinedTickCallback (internal/process/next_tick.js:142:11) at process._tickCallback (internal/process/next_tick.js:181:9) message: 'data is not defined' } (node:8915) UnhandledPromiseRejectionWarning: Error: data is not defined at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190) at JSON.parse () at jsonToObject (/opt/homey-client/system/helpers/jsonfns.js:1:1083) at function.e.data.map.e (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1379) at Array.map () at HomeyClient._onMessage (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1372) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:762:12) at _combinedTickCallback (internal/process/next_tick.js:142:11) at process._tickCallback (internal/process/next_tick.js:181:9) (node:8915) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:8915) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. 2019-02-21 18:29:56 [err] [ManagerDrivers] [Plug] [0] registerAttrReportListener() -> error could not configure attrReport_0_seMetering_instantaneousDemand { Error: data is not defined at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190) at JSON.parse () at jsonToObject (/opt/homey-client/system/helpers/jsonfns.js:1:1083) at function.e.data.map.e (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1379) at Array.map () at HomeyClient._onMessage (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1372) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:762:12) at _combinedTickCallback (internal/process/next_tick.js:142:11) at process._tickCallback (internal/process/next_tick.js:181:9) message: 'data is not defined' } (node:8915) UnhandledPromiseRejectionWarning: Error: data is not defined at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190) at JSON.parse () at jsonToObject (/opt/homey-client/system/helpers/jsonfns.js:1:1083) at function.e.data.map.e (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1379) at Array.map () at HomeyClient._onMessage (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1372) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:762:12) at _combinedTickCallback (internal/process/next_tick.js:142:11) at process._tickCallback (internal/process/next_tick.js:181:9) (node:8915) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) 2019-02-21 18:29:56 [err] [ManagerDrivers] [Plug] [0] registerAttrReportListener() -> error could not configure attrReport_0_seMetering_currentSummDelivered { Error: data is not defined at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190) at JSON.parse () at jsonToObject (/opt/homey-client/system/helpers/jsonfns.js:1:1083) at function.e.data.map.e (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1379) at Array.map () at HomeyClient._onMessage (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1372) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:762:12) at _combinedTickCallback (internal/process/next_tick.js:142:11) at process._tickCallback (internal/process/next_tick.js:181:9) message: 'data is not defined' } (node:8915) UnhandledPromiseRejectionWarning: Error: data is not defined at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190) at JSON.parse () at jsonToObject (/opt/homey-client/system/helpers/jsonfns.js:1:1083) at function.e.data.map.e (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1379) at Array.map () at HomeyClient._onMessage (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1372) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:762:12) at _combinedTickCallback (internal/process/next_tick.js:142:11) at process._tickCallback (internal/process/next_tick.js:181:9) (node:8915) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3) 2019-02-21 18:29:57 [err] [ManagerDrivers] [Plug] [0] registerAttrReportListener() -> error could not configure attrReport_0_seMetering_currentSummReceived { Error: data is not defined at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190) at JSON.parse () at jsonToObject (/opt/homey-client/system/helpers/jsonfns.js:1:1083) at function.e.data.map.e (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1379) at Array.map () at HomeyClient._onMessage (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1372) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:762:12) at _combinedTickCallback (internal/process/next_tick.js:142:11) at process._tickCallback (internal/process/next_tick.js:181:9) message: 'data is not defined' } (node:8915) UnhandledPromiseRejectionWarning: Error: data is not defined at Object.JSON.parse (/opt/homey-client/system/helpers/jsonfns.js:1:1190) at JSON.parse () at jsonToObject (/opt/homey-client/system/helpers/jsonfns.js:1:1083) at function.e.data.map.e (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1379) at Array.map () at HomeyClient._onMessage (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/lib/HomeyClient.js:1:1372) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:762:12) at _combinedTickCallback (internal/process/next_tick.js:142:11) at process._tickCallback (internal/process/next_tick.js:181:9) (node:8915) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFpiKAUuV9LviQD41jIBOPL2e5fYocsgks5vPthugaJpZM4a388Y> .

[MischaKluin]

Thanks.
Do you still want the output for the latest version of your app?

I could give you access to my Homey with fw 2.0.2 ...