would you spoon feed us by let us look at your configuration parameters? I just got mine two days ago, and I too, stuck at device not refreshing, device kept “sleeping”, device claim to be on battery while it’s on usb, etc.
and we have no idea any of how to configure the device, especially for those who knows nothing about bitwise operation.
thanks in advance
Since I dont’ know anything about bitwise operations, I am struggling to understand how to configure this device.
Has anyone managed to make sense out of the official “calculation spreadsheet,” which contains DBS09104 (Gen1 tab) information?
thanks in advance
https://aeotec.freshdesk.com/helpdesk/attachments/6044361983
Under the zwave control panel > device “energy meter” > node config options my settings read 782 for group #101 (Group 1 Reports) and 10 for group #111 (Group 1 Interval). If those two changes don’t provide updates every 10 seconds to current and power then I’ll share my entire node entry in the .XML this evening when I have a chance, gentlemen.
thank you.
zwave control panel was the first thing i go through. and for some reason, none of my input get inserted despite that seems to acknowledge the change:
2018-01-28 12:09:23.003 Info, Node002, Value::Set - COMMAND_CLASS_CONFIGURATION - Group 1 Reports - 101 - 1 - 782
2018-01-28 12:09:23.003 Info, Node002, Configuration::Set - Parameter=101, Value=782 Size=4
2018-01-28 12:09:23.004 Detail,
2018-01-28 12:09:23.004 Detail, Node002, Queuing (WakeUp) ConfigurationCmd_Set (Node=2): 0x01, 0x0f, 0x00, 0x13, 0x02, 0x08, 0x70, 0x04, 0x65, 0x04, 0x00, 0x00, 0x03, 0x0e, 0x25, 0x1a, 0xce
2018-01-28 12:09:23.004 Detail,
2018-01-28 12:09:23.004 Detail, Node002, Queuing (WakeUp) ConfigurationCmd_Get (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x70, 0x05, 0x65, 0x25, 0x1b, 0xc9
2018-01-28 12:10:04.463 Info, Node002, Value::Set - COMMAND_CLASS_CONFIGURATION - Group 1 Interval - 111 - 1 - 60
2018-01-28 12:10:04.463 Info, Node002, Configuration::Set - Parameter=111, Value=60 Size=4
2018-01-28 12:10:04.463 Detail,
2018-01-28 12:10:04.463 Detail, Node002, Queuing (WakeUp) ConfigurationCmd_Set (Node=2): 0x01, 0x0f, 0x00, 0x13, 0x02, 0x08, 0x70, 0x04, 0x6f, 0x04, 0x00, 0x00, 0x00, 0x3c, 0x25, 0x1c, 0xf3
2018-01-28 12:10:04.463 Detail,
2018-01-28 12:10:04.463 Detail, Node002, Queuing (WakeUp) ConfigurationCmd_Get (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x70, 0x05, 0x6f, 0x25, 0x1d, 0xc5
does it has anything to do with this strange value range?
An Integer between 2147483648 and 2147483647
huh?
Am I the only one who encounter this issue?
Hmm. What version of HA are you currently running? And what is your zwave stick/device. You could always try to shut down HA and manually enter 782 for the 101 entry and 10 for the 111 in the z***.XML file. In the past I had issues getting the panel/zwave device to accept/change my config while HA was up/running.
My HA is on hass.io, version 0.62.0.
I am using this Nortek husbzb-1 usb stick as my zwave/zigbee device.
the zwcfg_XXXX.xml look very intimating.
So, I stopped HA and manually changed the value. the value changed.
all i have to do now is figure out what value does it detect.
Which version of firmware are you guys using?
Is there anything wrong with version 3.67?
Im using 3.67. seems to work…
Is there any way to upgrade without a PC? Mac only household…
I’m getting pretty sporadic behavior. I’ve tried setting refresh to group 1 and 2 refresh to 10 and 30 seconds, and then monitor the zwave bits via the GUI. It seems to randomly be setting the interval of 1 and 2 between 10 to ~380 seconds. Not consistent, not the same on both, and random with every restart. I’ve set these via the zwcfg file.
While standing in front of my utility meter, I saw the Aeotec refresh and show 359w while the utility meter was showing 280w. Anyone else compare their accuracy to the utility meter?
I gave up on mine. It was never anywhere near accurate, even when I could get it to report. I left mine hooked up so its basically just a repeater now.
I bought a Sense some time ago and it reads very accurately. At the end of the month, the total usage was very very close to my bill. Liking it so far. Definitely not a cheap option though. There is also a Hass component for it now.
Yea, I feel like there’s a reason I only paid 30 bucks for mine…you get what you pay for.
I’ve been following this thread to configure my DSB09104 clamps. I have tried the xml from @Scott_Johnston with no luck. My desire is to read current/ongoing readings from clamps 1, clamps 2, and the total of both. Initially it displayed a low value and has been climbing through the weekend. I’m using Hass.io 0.66 (was 0.65 until it updated this weekend).
config looks like:
zwave:
usb_path: /dev/ttyACM0
polling_interval: 30000
Any assistance is appreciated.
Good afternoon. So you don’t need the polling_interval in your config. Earlier in this post I mentioned changing 101 to 782 and 111 to 30 (30 seconds). I recently wiped my z-stick so had to set up my HEM again. I ran into the issue of the device not taking/saving input from the zwave config panel. It’s because the HEM needs to be “listening” within 1-3 seconds after you hit the “set config parameter” button. I’d start with the “USB powered option” first…The HEM doesn’t normally report but once every 4 minutes if it “thinks” it’s powered by batteries.
drop down to usb option, put 1 in box. Immediately after hitting “set config parameter” press the button on the HEM (under the battery cover). It should take the value.
do the same for option 101, entering 782 in the box. After pressing the “set config parameter” make sure you press the button on the HEM
Finally, do the same for option 111, entering 30 (30 seconds) or another option if you wish to receive more/less frequent updates.
I would run the following command in a terminal and watch to see that the device does indeed wake and the updates start occuring after the values are accepted.
tail -f /home/homeassistant/.homeassistant/OZW_log.txtWhere does the sensor.energybaseline come from. In the platform energy baseline there is no sensor.
How do I create that, all the rest of it works the automation and script works.
Below reads the file “energybaseline.txt” and extracts the value
This shell command creates the file…(make sure you put your password where the “XXX” are)
(Check paths used in scripts since most will not use a user called “ha” like my home dir paths above)
And if you save the file in your homeassistant folder you’ll have to ensure it’s whitelisted under the homeassistant: part of your config
whitelist_external_dirs:
- /home/homeassistant/.homeassistant/
I am running hassio as a docker on ubuntu 18.04.
when I run the command in terminal it works.
for example…
linuxbox@linuxbox:~$ curl -X GET -H ‘Content-Type: application/json’ ‘http://10.0.10.27:8123/api/states/sensor.aeotec_zw095_home_energy_meter_gen5_energy?api_password=mysupersecretpassword’ -o /usr/share/hassio/homeassistant/energybaseline.txt
and output looks like this.
{“attributes”: {“friendly_name”: “Energy Meter kWh Total”, “node_id”: 4, “power_consumption”: 493.345, “unit_of_measurement”: “kWh”, “value_id”: “144115188147978242”, “value_index”: 0, “value_instance”: 2}, “entity_id”: “sensor.aeotec_zw095_home_energy_meter_gen5_energy”, “last_changed”: “2018-06-10T01:39:23.344852+00:00”, “last_updated”: “2018-06-10T01:39:23.344852+00:00”, “state”: “5.82”}
if I go to the information tab in hassio it shows the config path as:
Home Assistant
0.71.0
Path to configuration.yaml: /config
if I use that path I get nothing.
for instance this command:
energybaselineshell: “curl -X GET -H ‘Content-Type: application/json’ ‘http://10.0.10.27:8123/api/states/sensor.aeotec_zw095_home_energy_meter_gen5_energy?api_password=anothersupersecretpassword’ -o /config/energybaseline.txt”
Correction, if I run that script in hassio I get nothing using both paths.
I am actually having the same problem with my python scripts and other shell scripts. Because there are so many different installation possibilities with and without environments, on a pi or not on a pi, different flavors of linux or inside a docker container. I am confused about the path that hassio needs/sees (requires) inside of the docker container.
see my other post regarding paths.
Well I’m not a Hass.io user so, unfortunately, I can’t help you with the path issue. I can say that when I run the command in raspbian as pi it doesn’t save… Need to be homeassistant user or root. Also, you have whitelisted directories in your config? Safest bet would be to whitelist folder where your config and stuff sit and send the output of the curl command to a file in that folder.
I think you are on to something…I got this in the logs…
Press the button to load the full Home Assistant log.
2018-06-09 17:37:09 ERROR (MainThread) [homeassistant.components.sensor.file] ‘/config/energybaseline.txt’ is not a whitelisted directory
Yeah? Did mention it above. 