No energie information in app dashboard #4
Comments
|
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 <
[email protected]>
… 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>
.
|
|
Hi Martin, I'm consuming electricity with the Plug HA. My (small) electric car is connected. Regards, Herman. |
|
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 <
[email protected]>
… 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>
.
|
|
Hi Martin, Regards, Herman. |
|
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 <
[email protected]>
… 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>
.
|
|
I'm sorry Martin, I'm not a programmer and can't help you with debugging this issue. |
|
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 <
[email protected]>
… 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>
.
|
|
I understand, success Martin with solving the issue. |
|
I experienced the same problem. onoff was communicated propely as soon as there was an event 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. |
|
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... Also strange is the naming of the variables measured by the Plug: |
|
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 <[email protected]>
… 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>
.
|
|
Onderstaand de output van de app versie van 2018-04-26 — Profile your app's performance at https://go.athom.com/app-profiling?homey=5aa8f8b205eff5043791a40d&app=com.plugwise.zigbee |
|
2019-02-21 18:34:56 [log] [ManagerDrivers] [Plug] [0] [dbg] Polling clusterId 'haElectricalMeasurement' for capabilityId 'alarm_poweroverload' |
|
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 <[email protected]>
… — 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>
.
|
|
Thanks. I could give you access to my Homey with fw 2.0.2 ... |
|
Thx for asking, but at this moment not needed.
Op do 21 feb. 2019 om 18:41 schreef MischaKluin <[email protected]>
… Do you still want the output for the latest version of your app?
—
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/AFpiKOH1sLV9lDd4hokG_PH2Z_7Jr6_gks5vPto4gaJpZM4a388Y>
.
|
|
PowerOverload was fixed properly on Jan 29th ! Every 5 minutes: As is OnOff |
|
Poweroverload doesn’t report in intervals so in order to get those values
it needs to get polled.
5 min is chosen in order to not overload the zigbee network by using
polling. You have to minimize the use off polling as much as possible!
The fixed “introduced” on Jan 29 was the firmware 2.x.x compatibility to
get the app installed and displaying custom capabilities.
At that moment I wasn’t aware off the problem with the reportlisteners
because (as said before ;-) ) I could not test it.
Op do 21 feb. 2019 om 18:46 schreef MischaKluin <[email protected]>
… PowerOverload was fixed properly on Jan 29th !
Every 5 minutes:
2019-02-21 18:34:56 [log] [ManagerDrivers] [Plug] [0] [dbg] Polling
clusterId 'haElectricalMeasurement' for capabilityId 'alarm_poweroverload'
2019-02-21 18:39:57 [log] [ManagerDrivers] [Plug] [0] [dbg] Polling
clusterId 'haElectricalMeasurement' for capabilityId 'alarm_poweroverload'
2019-02-21 18:44:57 [log] [ManagerDrivers] [Plug] [0] [dbg] Polling
clusterId 'haElectricalMeasurement' for capabilityId 'alarm_poweroverload'
—
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/AFpiKJ6cSCXQEn_TuhcZwS8ZV1x5k7kAks5vPttbgaJpZM4a388Y>
.
|
|
I know about reducing the pollling load. |
|
Thx for the offer. I will certainly get back to you the moment I have a new
build to test.
Are you on slack? If so, let me know. I can send you dm
Op do 21 feb. 2019 om 19:01 schreef MischaKluin <[email protected]>
… I know about reducing the pollling load.
If you would make a build (even with frequent polling) I will be able to
test on fw 2.0 via CLI.
—
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/AFpiKIPW2llafDnJq76YprphYEU1OIzRks5vPt7egaJpZM4a388Y>
.
|
|
I'm on Slack. |
Friend of mine has a USB Zigbee stick, and I live very close to the Plugwise devs... |
|
Top.
Btw, Please send me a dm on slack
… On 21 Feb 2019, at 20:26, MischaKluin ***@***.***> wrote:
First thing: how do you plan to get the new firmware on the device? Homey does not support ota.
Friend of mine has a USB Zigbee stick, and I live very close to the Plugwise devs...
—
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/AFpiKGynr2Qst9dxpG8CegOnCr39cGZwks5vPvLegaJpZM4a388Y>.
|
|
I'm on Slack, but not yet part of the Homey workspace... |
|
Results for 1.0.2 (22df413 ) Capability | Type | Value | Edit value | Last Updated |
|
Ok, I put a new version for the plug on github.
Op do 21 feb. 2019 om 21:15 schreef Mischa <[email protected]>
… I'm on Slack, but not yet part of the Homey workspace...
—
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/AFpiKD7gn5sulTCJ_hvp4UaGfHZeAR1nks5vPv5LgaJpZM4a388Y>
.
|
|
Ah, you did already notice.
No errors on the reportlisteners?
Op do 21 feb. 2019 om 22:01 schreef Mischa <[email protected]>
… Result 1.0.2
Capability | Type | Value | Edit value | Last Updated
onoff | boolean | true | truefalse | 47 seconds ago
meter_power | number | null | |
meter_received | number | null | |
measure_power | number | null | |
alarm_poweroverload | boolean | false | | 1 minute ago
—
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/AFpiKA39LS4ZnPwj7tclv7G5W5ESbkxMks5vPwkigaJpZM4a388Y>
.
|
|
2019-02-21 22:04:06 [err] [ManagerDrivers] [Plug] [0] registerAttrReportListener() -> error could not configure attrReport_0_genOnOff_onOff { Error: data is not defined |
|
Did not alter the onoff reportlistener, but the others also give errors.
Could you test for me what happens if you remove the plug within Homey and
after that reinclude it?
Op do 21 feb. 2019 om 22:06 schreef Mischa <[email protected]>
… 2019-02-21 22:04:06 [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)
AthomAppRun20190221a.txt
<https://github.com/kasteleman/com.plugwise.zigbee/files/2891263/AthomAppRun20190221a.txt>
—
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/AFpiKGFlw9D4iMidvcWUa61duSj5Ewqkks5vPwpFgaJpZM4a388Y>
.
|
|
Will try now... |
|
Heb ik net gedaan:
V1.0.1 geïnstalleerd
Plug toegevoegd
V1.0.2 geïnstalleerd met CLI
measure_power meet alleen verbruik (positief), geen opwekking door PV (vroeger negatief)
meter_received werkt (maar met Plugwise firmware bug...)
meter_power | number | 0 | | 3 minutes ago
-- | -- | -- | -- | --
meter_received | number | 0.008 | | 3 minutes ago
measure_power | number | 1 | | 5 minutes ago
alarm_poweroverload | boolean | false | | 11 minutes ago
[AthomAppRun20190405a.txt](https://github.com/kasteleman/com.plugwise.zigbee/files/3047570/AthomAppRun20190405a.txt)
Homey insights toont meter_received niet ...
|
|
Er is een aparte “capability” voor ontvangen energie. Ik heb alleen geen
mogelijkheid om dat te testen. Kan je nog eens een debuglog sturen op het
moment dat je zeker weet dat er energie wordt ontvangen?
Groet,
Martin
Op vr 5 apr. 2019 om 12:55 schreef Mischa <[email protected]>
… Hoi Martin,
Heb ik net gedaan.
V1.0.1 geïnstalleerd
Plug toegevoegd
V1.0.2 geïnstalleerd met CLI
measure_power meet alleen verbruik (positief)
Van: kasteleman ***@***.***>
Verzonden: vrijdag 5 april 2019 12:41
Aan: kasteleman/com.plugwise.zigbee <
***@***.***>
CC: Mischa ***@***.***>; Comment ***@***.***>
Onderwerp: Re: [kasteleman/com.plugwise.zigbee] No energie information in
app dashboard (#4)
Hallo,
Kan je de plug een keer uit netwerk halen en weer toevoegen, of heb je dat
al gedaan?
Groet,
Martin
Op vr 5 apr. 2019 om 12:28 schreef Mischa ***@***.***>
> Met de Homey update 2.1.0 werkt het uitlezen van de plug weer.
> helaas mist nu de meest waardevolle functie: registreren van
> opgewekte/teruggeleverde energie ...
>
> —
> 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/AFpiKITKtvjw4mfFULCcwaKy7ilu5koLks5vdyUzgaJpZM4a388Y
>
> .
>
—
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/AtpCyr_3kkDAhWjCiXfat93OAHXvAlaNks5vdyhVgaJpZM4a388Y>
.
—
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/AFpiKO4xTmW6ujUsVnfx0QFDRHJd25m9ks5vdyungaJpZM4a388Y>
.
|
|
At this moment the PV delivers around 50 Watt of power.
|
|
Had je wat aan de data en kan ik evt al iets testen? |
|
Volgens de data lijkt alles binnen te komen:
2019-04-06 18:39:53 [log] [ManagerDrivers] [Plug] [0] ----
currentSummReceived : [ null, 24060 ]
Maar dat is bij de start. Daarna stopt de logging. Nieuwsgierig of er
aansluitend nog wat binnen komt.
Maw je kan kijken of er na wat langere tijd wat binnen komt op het
moment dat er stroom wordt teruggeleverd.
Groet,
Martin
Op ma 15 apr. 2019 om 12:05 schreef Mischa <[email protected]>
… Had je wat aan de data en kan ik evt al iets testen?
—
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/AFpiKBgIpcV4f20NHPmcuLGfNZ3AGIIaks5vhE8FgaJpZM4a388Y>
.
|
|
AthomAppRun20190415a.txt Capability | Type | Value | Edit value | Last Updated currentSummDelivered wordt goed verwerkt, nu geen verbruik... |
|
meter_received | number | 0.174 |
Die waarde loopt niet op en/of wordt getoond in de Homey app?
Op ma 15 apr. 2019 om 17:53 schreef Mischa <[email protected]>
… AthomAppRun20190415a.txt
<https://github.com/kasteleman/com.plugwise.zigbee/files/3080990/AthomAppRun20190415a.txt>
Logging 40 minuten, aflopende opbrengst zonnepanelen.
Capability | Type | Value | Edit value | Last Updated
onoff | boolean | false | truefalse | 3 minutes ago
meter_power | number | 0 | | 3 minutes ago
meter_received | number | 0.174 | | 3 minutes ago
measure_power | number | 0 | | 10 hours ago
alarm_poweroverload | boolean | false | | 2 minutes ago
—
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/AFpiKD8WVRcBpPLjGtASHE1cJ4aoHHU9ks5vhKBngaJpZM4a388Y>
.
|
|
meter_power loopt nu niet op omdat de plug wordt gebruikt voor het meten van zonnepanelen. |
|
Pushed a version to GitHub to allow value below -2 for measure_power. |
|
Ik heb de nieuwe software geïnstalleerd, Plug opnieuw met netwerk verbonden. Capability | Type | Value | Edit value | Last Updated Measure power wordt niet ververst en app werd na 10 minuten lopen afgesloten |
|
Dank je wel voor de feedback.
Zie dat 1 aanpassing niet werkt (out of range) Zal ik dus moeten
terugdraaien en verder onderzoek noodzakelijk.
Groet,
Martin
Op za 11 mei 2019 om 20:19 schreef Mischa <[email protected]>
… Ik heb de nieuwe software geïnstalleerd, Plug opnieuw met netwerk
verbonden.
Hieronder de resultaten uit Homey Developer Devices en de log file.
Capability | Type | Value | Edit value | Last Updated
onoff | boolean | true | truefalse | 9 minutes ago
meter_power | number | null | | 16 minutes ago
meter_received | number | null | | 16 minutes ago
measure_power | number | 6.3 | | 28 minutes ago
alarm_poweroverload | boolean | false | | 11 minutes ago
AthomAppRun20190511.txt
<https://github.com/kasteleman/com.plugwise.zigbee/files/3169348/AthomAppRun20190511.txt>
—
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/ABNGEKEKTCF6AVPYTZUCKYDPU4EZNANCNFSM4GW7Z4MA>
.
|
|
Ik heb een nieuwe versie gepushed. Wil je die testen en de log wederom sturen? |
|
Doe ik, laat de app 15 minuten lopen. Ik zal morgenochtend een run doen met zonlicht en log uploaden |
|
Meter Received krijgt regelmatig data binnen, lijkt me niet goed geformatteerd. |
|
ok, measure_power report listener was nog niet aangepast. Daarom alleen initieel een waarde. Aanpassing gedaan en tevens de andere weer teruggezet naar readUIntBE. Graag testen. Heb je toevallig een andere manier om de waarden te vergelijken? |
|
instantaneousDemand werkt nu perfect: Dank! Homey Insigths presenteert overigens alleen de waarden voor Energie (instantaneousDemand ???) en Energiemeter (oncurrentSummDelevered). Blijft ook lastig: vb |
|
oncurrentSummReceived [ 0, 28610 ] 0.194 gaat fout met formatering middels readUIntBE |
|
oncurrentSummReceived had ook te maken met een foute implementatie van Plugwise in de firmware van de Plug: een te kleine variabele genomen (2 bytes). Morgenochtend is er weer zon ... |
|
Data ziet er nu goed uit, oncurrentSummReceived is werkbaar zo. De onChange kaart in Homey Flow voor "Ontvangen meterstand is veranderd" werkt nu nog niet. |
|
Hallo,
Weer niet of het dan goed in de gui. Mbt de flow moet ik even induiken.
Op ma 13 mei 2019 om 12:33 schreef Mischa <[email protected]>
… Data ziet er nu goed uit, oncurrentSummReceived is werkbaar zo.
Nog mooier zou zijn om de waarde *10 te communiceren, dan is het in Wh
De onChange kaart in Homey Flow voor "Ontvangen meterstand is veranderd"
werkt nu nog niet.
AthomAppRun20190512b2.txt
<https://github.com/kasteleman/com.plugwise.zigbee/files/3172412/AthomAppRun20190512b2.txt>
—
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/ABNGEKE5ODGB3ND6CZTIDELPVE7ZJANCNFSM4GW7Z4MA>
.
|
|
2019-05-13 09:38:32 [log] [ManagerDrivers] [Plug] [0] currentSummDelivered [ 0, 0 ] 0 Alleen de decimaal iets verplaatsen zou voor de GUI toch geen probleem moeten zijn? onChange kan te maken hebben met de naamgeving in de logging? |
|
Voor de waarde niet, maar wel voor de omschrijving. Maw Moet ik Dan ook
zien aan Te passen. Flow komt door custom capability
Op ma 13 mei 2019 om 13:39 schreef Mischa <[email protected]>
… 2019-05-13 09:38:32 [log] [ManagerDrivers] [Plug] [0] currentSummDelivered
[ 0, 0 ] 0
2019-05-13 09:38:32 [log] [ManagerDrivers] [Plug] [0]
oncurrentSummReceived [ 0, 29380 ] 293.8
Alleen de decimaal iets verplaatsen zou voor de GUI toch geen probleem
moeten zijn?
Dus van [ 0, 29380 ] 293.8 naar bv [ 0, 29380 ] 2938.0
onChange kan te maken hebben met de naamgeving in de logging?
currentSumm... vs *on*currentSumm...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4?email_source=notifications&email_token=ABNGEKARXFPQZGBKCURG4TDPVFHP3A5CNFSM4GW7Z4MKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVIBLTI#issuecomment-491787725>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABNGEKDP4EXMNUEQTRJ4O6DPVFHP3ANCNFSM4GW7Z4MA>
.
|
|
Aanpassing gedaan. Ik heb zelf nog niet kunnen achterhalen waarom de flow het niet doet. Ook wordt icoon van ontvangen stroom niet goed weergegeven in de GUI. |
|
Geïnstalleerd en getest, doorgeven van waarden werkt prima nu.
|
|
Fixed icons for the plug. Weet nog niet waarom de onChange niet werkt. |
|
Vandaag de nauwkeurigheid van de meter geverifieerd en werkt prima zo. ENERGIEMETER ONTVANGEN ENERGIE Voorbeeld: Ik kan evt de iconen in hoge resolutie maken.
|
|
pushed new version: Power_received_changed trigger changed |
|
Mooi. 2e run: helaas geen workflow afgegaan door trigger meterReceived .... |
|
In Homey Insights zijn nu slechts 2 waarden zichtbaar: |
|
Kleine aanpassing gedaan. Alledrie zijn in mijn opstelling zichtbaar. |
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).
The text was updated successfully, but these errors were encountered: