Domoticz

Open source Home Automation System
https://forum.domoticz.com/

Energy meters has stopped working

https://forum.domoticz.com/viewtopic.php?t=12198

Page 1 of 1

Energy meters has stopped working

Posted: Tuesday 31 May 2016 19:50
by dhanjel
Has anyone experienced this? All my energy meetings are inaccessible, but the "main device" still works as expected.

Image

Most of them are Fibaro Wall Plugs, with the device with Unit 4 added.

Do I use the wrong subdevice?

Re: Energy meters has stopped working

Posted: Tuesday 31 May 2016 22:46
by Plaagje
Did they worked before?
Have you updated Domoticz?
Have you done something prior to this error?

Sent from my Nexus 5X using Tapatalk

Re: Energy meters has stopped working

Posted: Wednesday 01 June 2016 8:18
by dhanjel
They did work at start, at least a day or two.
No update or changes except for adding a couple of additional devices.


Sent from my Nexus 6P using Tapatalk

Re: Energy meters has stopped working

Posted: Thursday 02 June 2016 23:17
by Plaagje
You could try to remove those devices and see if they are interfearing with the energy meters.

Sent from my Nexus 5X using Tapatalk

Re: Energy meters has stopped working

Posted: Saturday 04 June 2016 12:04
by gcoupe
Sometime in the past couple of months, I've started seeing this issue. Utility readings will stop coming in from Z-Wave devices (all Fibaro wallplugs), and the device will display the red bar at the top.

It won't be all the devices, but two or three of them, and always the same ones as far as I can see.

I have to restart Domoticz (version 3.4834) to get the devices reading again.

Yesterday, for the first time, the issue occurred with my P1 Meter - and the log showed that no gas or electricity readings were coming in to Domoticz. Once again, a restart of the Domoticz service (I'm running Domoticz as a Windows Service) fixed this.

In the past couple of months I've made a couple of changes in my setup:
- Changed the Z-wave controller from an Aeon S2 USB Stick to an Aeon Gen 5 USB stick.
- Moved Domoticz from a homebuild Windows server (Intel Core i3-based) to an Intel NUC (also Core i3)

I can't be certain which (if either) of these changes coincided with the issue raising its head.

I had thought, up until yesterday, that this issue was caused by some interaction between Z-wave and Domoticz, but yesterday's loss of P1 readings seems to point elsewhere, and is rather worrying.

Re: Energy meters has stopped working

Posted: Tuesday 07 June 2016 13:01
by dhanjel
Plaagje wrote:You could try to remove those devices and see if they are interfearing with the energy meters.

Sent from my Nexus 5X using Tapatalk
I only have a couple of different devices, all types had already been included before so it should not be due to
a specific device type.

I see no issues in the log.

Somewhat frustrating since a lot of my automatic scenes are based on consumption.

Re: Energy meters has stopped working

Posted: Thursday 16 June 2016 13:20
by dhanjel
I still has not resovled this, anyone else with the same issues?
Main device works perfectly fine, but none of the energy meeters.

Code: Select all

{
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 102,
         "Data" : "On",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 2,
         "HardwareName" : "Z-Wave",
         "HardwareType" : "OpenZWave USB",
         "HardwareTypeVal" : 21,
         "HaveDimmer" : true,
         "HaveGroupCmd" : true,
         "HaveTimeout" : false,
         "ID" : "00000601",
         "Image" : "FibaroWallPlug",
         "IsSubDevice" : false,
         "LastUpdate" : "2016-06-07 14:05:05",
         "Level" : 255,
         "LevelInt" : 255,
         "MaxDimLevel" : 100,
         "Name" : "Kök, Kaffebryggare",
         "Notifications" : "false",
         "PlanID" : "6",
         "PlanIDs" : [ 6 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "Status" : "On",
         "StrParam1" : "",
         "StrParam2" : "",
         "SubType" : "Switch",
         "SwitchType" : "On/Off",
         "SwitchTypeVal" : 0,
         "Timers" : "false",
         "Type" : "Light/Switch",
         "TypeImg" : "lightbulb",
         "Unit" : 1,
         "Used" : 1,
         "UsedByCamera" : false,
         "XOffset" : "0",
         "YOffset" : "0",
         "idx" : "17"
      },
{
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "0.0 Watt",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 2,
         "HardwareName" : "Z-Wave",
         "HardwareType" : "OpenZWave USB",
         "HardwareTypeVal" : 21,
         "HaveTimeout" : false,
         "ID" : "0000604",
         "LastUpdate" : "2016-06-16 13:03:19",
         "Name" : "Kök, Kaffebryggare",
         "Notifications" : "false",
         "PlanID" : "0",
         "PlanIDs" : [ 0 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "SubType" : "Electric",
         "Timers" : "false",
         "Type" : "Usage",
         "TypeImg" : "current",
         "Unit" : 2,
         "Used" : 0,
         "XOffset" : "0",
         "YOffset" : "0",
         "idx" : "18"
      },
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "0.0 Watt",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 2,
         "HardwareName" : "Z-Wave",
         "HardwareType" : "OpenZWave USB",
         "HardwareTypeVal" : 21,
         "HaveTimeout" : true,
         "ID" : "0000006",
         "LastUpdate" : "2016-06-07 18:05:04",
         "Name" : "Kök, Kaffebryggare",
         "Notifications" : "false",
         "PlanID" : "6",
         "PlanIDs" : [ 6 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "SubType" : "Electric",
         "Timers" : "false",
         "Type" : "Usage",
         "TypeImg" : "current",
         "Unit" : 4,
         "Used" : 1,
         "XOffset" : "0",
         "YOffset" : "0",
         "idx" : "19"
      },
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "0.0 Watt",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 2,
         "HardwareName" : "Z-Wave",
         "HardwareType" : "OpenZWave USB",
         "HardwareTypeVal" : 21,
         "HaveTimeout" : true,
         "ID" : "0000601",
         "LastUpdate" : "2016-06-08 20:31:22",
         "Name" : "Kök, Kaffebryggare",
         "Notifications" : "false",
         "PlanID" : "0",
         "PlanIDs" : [ 0 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "SubType" : "Electric",
         "Timers" : "false",
         "Type" : "Usage",
         "TypeImg" : "current",
         "Unit" : 2,
         "Used" : 0,
         "XOffset" : "0",
         "YOffset" : "0",
         "idx" : "20"
      }, {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "0.0 Watt",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 2,
         "HardwareName" : "Z-Wave",
         "HardwareType" : "OpenZWave USB",
         "HardwareTypeVal" : 21,
         "HaveTimeout" : true,
         "ID" : "0000006",
         "LastUpdate" : "2016-06-07 14:05:05",
         "Name" : "Kök, Kaffebryggare",
         "Notifications" : "false",
         "PlanID" : "0",
         "PlanIDs" : [ 0 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "SubType" : "Electric",
         "Timers" : "false",
         "Type" : "Usage",
         "TypeImg" : "current",
         "Unit" : 1,
         "Used" : 0,
         "XOffset" : "0",
         "YOffset" : "0",
         "idx" : "21"
      },
Only ídx 18 has a recent lastupdate for some reason.

Image

One Fibaro Wallplug still reports energy for some reason, but the other ones don´t.

Re: Energy meters has stopped working

Posted: Thursday 16 June 2016 13:28
by LouiS22
Have the same issue, I've removed and readded the device.

Re: Energy meters has stopped working

Posted: Thursday 16 June 2016 13:36
by dhanjel
Did that solve it? Did it a couple of times.

Not really a long term solution to the problem :/

It seems like the network keeps dropping / loosing nodes, or it might be random new nodes that appears.
I had no issues whatsoever of this kind with Fibaro and unfortunately this makes the system completely useless for me :(

Its a ~160m2 house with the controller in the middle and ~40 powered devices throughout the house that relays the traffic.

Image

Image

(I am aware that the issue might reside with the z-wave usb stick and its software/firmware, but the end result is in Domoticz)

Additional update, I´m using the UZB z-wave.me stick, might be just be inadequate hardware? (http://z-wave.me/index.php?id=28)

Re: Energy meters has stopped working

Posted: Thursday 16 June 2016 17:45
by dhanjel
I enabled full debug logs from z-wave controller and then just tried to turn off and then on a switch and from what I can see, the energy measurements are reported, but not displayed in Domoticz?

Code: Select all

2016-06-16 17:41:07.215 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - False
2016-06-16 17:41:07.215 Info, Node003, SwitchBinary::Set - Setting node 3 to Off
2016-06-16 17:41:07.215 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0x00, 0x25, 0x34, 0xd3
2016-06-16 17:41:07.215 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x35, 0xd3
2016-06-16 17:41:07.215 Detail,
2016-06-16 17:41:07.216 Info, Node003, Sending (Send) message (Callback ID=0x34, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0x00, 0x25, 0x34, 0xd3
2016-06-16 17:41:07.223 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-06-16 17:41:07.223 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2016-06-16 17:41:07.295 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x34, 0x00, 0x00, 0x07, 0xd8
2016-06-16 17:41:07.295 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x34 received (expected 0x34)
2016-06-16 17:41:07.295 Info, Node003, Request RTT 79 Average Request RTT 61
2016-06-16 17:41:07.295 Detail,   Expected callbackId was received
2016-06-16 17:41:07.295 Detail,   Expected reply was received
2016-06-16 17:41:07.295 Detail,   Message transaction complete
2016-06-16 17:41:07.295 Detail,
2016-06-16 17:41:07.295 Detail, Node003, Removing current message
2016-06-16 17:41:07.296 Detail,
2016-06-16 17:41:07.296 Info, Node003, Sending (Send) message (Callback ID=0x35, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x35, 0xd3
2016-06-16 17:41:07.303 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-06-16 17:41:07.303 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2016-06-16 17:41:07.320 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x35, 0x00, 0x00, 0x02, 0xdc
2016-06-16 17:41:07.320 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x35 received (expected 0x35)
2016-06-16 17:41:07.320 Info, Node003, Request RTT 24 Average Request RTT 42
2016-06-16 17:41:07.320 Detail,   Expected callbackId was received
2016-06-16 17:41:07.331 Detail, Node003,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x25, 0x03, 0x00, 0xd4
2016-06-16 17:41:07.331 Detail,
2016-06-16 17:41:07.331 Info, Node003, Response RTT 34 Average Response RTT 46
2016-06-16 17:41:07.331 Info, Node003, Received SwitchBinary report from node 3: level=Off
2016-06-16 17:41:07.331 Detail, Node003, Refreshed Value: old value=true, new value=false, type=bool
2016-06-16 17:41:07.331 Detail, Node003, Changes to this value are not verified
2016-06-16 17:41:07.331 Detail, Node003,   Expected reply and command class was received
2016-06-16 17:41:07.331 Detail, Node003,   Message transaction complete
2016-06-16 17:41:07.331 Detail,
2016-06-16 17:41:07.331 Detail, Node003, Removing current message
2016-06-16 17:41:07.331 Detail, Node003, Notification: ValueChanged
2016-06-16 17:41:08.288 Detail, Node003,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x03, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xe0
2016-06-16 17:41:08.288 Detail,
2016-06-16 17:41:08.288 Info, Node003, Received SensorMultiLevel report from node 3, instance 1, [b]Power: value=0.0W[/b]
2016-06-16 17:41:08.288 Detail, Node003, Refreshed Value: [b]old value=1.4, new value=0.0[/b], type=decimal
2016-06-16 17:41:08.288 Detail, Node003, Changes to this value are not verified
2016-06-16 17:41:08.288 Detail, Node003, Notification: ValueChanged
2016-06-16 17:41:11.258 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2016-06-16 17:41:11.258 Info, Node003, SwitchBinary::Set - Setting node 3 to On
2016-06-16 17:41:11.258 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0x36, 0x2e
2016-06-16 17:41:11.258 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x37, 0xd1
2016-06-16 17:41:11.258 Detail,
2016-06-16 17:41:11.258 Info, Node003, Sending (Send) message (Callback ID=0x36, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0x36, 0x2e
2016-06-16 17:41:11.265 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-06-16 17:41:11.266 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2016-06-16 17:41:11.283 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x36, 0x00, 0x00, 0x02, 0xdf
2016-06-16 17:41:11.283 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x36 received (expected 0x36)
2016-06-16 17:41:11.283 Info, Node003, Request RTT 24 Average Request RTT 33
2016-06-16 17:41:11.283 Detail,   Expected callbackId was received
2016-06-16 17:41:11.283 Detail,   Expected reply was received
2016-06-16 17:41:11.283 Detail,   Message transaction complete
2016-06-16 17:41:11.283 Detail,
2016-06-16 17:41:11.283 Detail, Node003, Removing current message
2016-06-16 17:41:11.283 Detail,
2016-06-16 17:41:11.283 Info, Node003, Sending (Send) message (Callback ID=0x37, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x37, 0xd1
2016-06-16 17:41:11.291 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-06-16 17:41:11.291 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2016-06-16 17:41:11.307 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x37, 0x00, 0x00, 0x02, 0xde
2016-06-16 17:41:11.308 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x37 received (expected 0x37)
2016-06-16 17:41:11.308 Info, Node003, Request RTT 24 Average Request RTT 28
2016-06-16 17:41:11.308 Detail,   Expected callbackId was received
2016-06-16 17:41:11.384 Detail, Node003,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x25, 0x03, 0xff, 0x2b
2016-06-16 17:41:11.384 Detail,
2016-06-16 17:41:11.384 Info, Node003, Response RTT 100 Average Response RTT 73
2016-06-16 17:41:11.384 Info, Node003, Received SwitchBinary report from node 3: level=On
2016-06-16 17:41:11.384 Detail, Node003, Refreshed Value: old value=false, new value=true, type=bool
2016-06-16 17:41:11.384 Detail, Node003, Changes to this value are not verified
2016-06-16 17:41:11.384 Detail, Node003,   Expected reply and command class was received
2016-06-16 17:41:11.384 Detail, Node003,   Message transaction complete
2016-06-16 17:41:11.384 Detail,
2016-06-16 17:41:11.384 Detail, Node003, Removing current message
2016-06-16 17:41:11.385 Detail, Node003, Notification: ValueChanged
2016-06-16 17:41:12.065 Detail, Node003,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x03, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x0d, 0xed
2016-06-16 17:41:12.065 Detail,
2016-06-16 17:41:12.065 Info, Node003, Received SensorMultiLevel report from node 3, instance 1, [b]Power: value=1.3W[/b]
2016-06-16 17:41:12.065 Detail, Node003, Refreshed Value: old value=0.0, [b]new value=1.3[/b], type=decimal
2016-06-16 17:41:12.065 Detail, Node003, Changes to this value are not verified
2016-06-16 17:41:12.065 Detail, Node003, Notification: ValueChanged
Image

Image

Another observation, it seems that one of the devices with unit 2 might hold the correct value, but not unit 4 as stated in wiki.
Image

Re: Energy meters has stopped working

Posted: Thursday 22 September 2016 9:39
by bigpea
Hi, I have the same problem.. have you resolved your issue?

thanks.

Re: Energy meters has stopped working

Posted: Saturday 01 October 2016 8:57
by gcoupe
I've got the same problem with a couple of my Fibaro wall plugs. Started happening a few months back. Still running v3.4834 stable release (on Windows 10 Pro) from last March.

Re: Energy meters has stopped working

Posted: Sunday 02 October 2016 19:58
by minicraft
Here the same story with my FIBARO FGMS 101 Smoke Sensor
The temperature measurement is disappeared
And changed from LaCrosse TX3 to WTGR800
I use a Raspberry Pi 2 Model B
Domoticz V3.5438

Re: Energy meters has stopped working

Posted: Friday 07 October 2016 23:47
by hamish
I have same problem. Been mentioning it here & on GitHub issues for domoticz for a few months now.

I went as far as hacking the code to try & find what domoticz is doing. And still a bit mystified I'm afraid. I suspect (theory only, no proof or evidence yet) that some of the issue is due to the way Domoticz references devices by a 'DeviceID' that seems to use random numbers of leading 0's depending on something that I haven't really tracked down yet. Its based on nodeid and unit of the wave device, but is inconsistent in that the same nodeid/unitid can get different deviceid's at different times (And a restart of domoticz can seemingly alter this mapping - hence you'll often see the problem appear or disappear as domoticz restarts).

Re: Energy meters has stopped working

Posted: Monday 10 October 2016 20:52
by dijka007
Same problem, Rasppberry Pi 2 , Domoticz 3.5744 . Two z-wave Philio Tech plugs and a Z-stick.
I've added a cron job to restart domoticz daily, after that the voltage reporting works for a short while, usually less than two hours.
All times are UTC+01:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited