Aeotec DSB09104 Home Energy Meter not updating in HASS

I was able to get this all sorted. I ended up installing and configuring zwavejs2mqtt. Here are my settings that worked to give me the whole home w and kwh data I was looking for.

Im using the DSB09104 (firmeware 3.64) with ZwaveJStoMQTT. Seems the Energy feature has revived interest in this device… Im struggling to get mine set up appropriately and had a few questions

  1. Im in the US with it connected to the mains (150A service) coming in to my circuit panel. Do I understand correctly that Operating Voltage param should be set to 120V (Im guessing 120V per clamp, 240V total)? I initially set it to 240V and my readings seemed very high.

  2. I have Solar and feed electricity back to the grid. Anyone figured out how to configure HEM to properly account for the direction? Right now I think the Electric consumed kWH sensor is increasing regardless of direction. My “usage” appears to be slightly less then my solar production each hour.

  3. Am I correct that I only need to report the “Whole HEM” values and can disable the individual clam sensors (at least in HASS)?

  4. Is there anyway to see additional data such as voltage, amp, etc. I believe this is useful for troubleshooting power issues.

Thanks!

For 1, I initially had the same thought as you but I believe you want 120v. I “tested” it with my EV charger which outputs 7 kw and confirmed when its set to 120v and I begin to charge my care the value goes up ~7 kw.

For 3, this is what I did. You might want the solar input clamp though for your production.

For 4, I don’t believe this gen model supports these values. I believe, but could be wrong, that the further gen versions do support more values (gen5?).

One thing I have not been able to get working correctly is the kwh report. It’s reporting way higher than it should. I suspect that 1 the Basic setting needs to be changed but I have been unsuccessful in getting them to stick.

And 2 I think the value is is actually reporting wh rather than kwh although this is just a suspicion.

Has anyone had any luck getting this part working?

With the latest Z-Wave JS update, I’m finally able to see the parameters! Will start testing now.

I give up on trying to get mine to work. Im gonna buy a shelly em and use the clamps off the aeotec on it.

Were you ever able to get the kWh report working correctly? I seem to be having the same issue.

Guess this explains it…

And a word of warning using the kWh value. This value is a lifetime value that the meter keeps. It will keep increasing until it rolls over or the meter receives a ZWAVE Meter Reset command, which Home Assistant currently cannot do.

https://www.reddit.com/r/homeassistant/comments/6q1af0/comment/dku8p61/?utm_source=share&utm_medium=web2x&context=3

Nope. Currently debating getting a Sense HEM.

EDIT

Ended up ditching the Aeotec and got a Sense.

Hi, I have had one of these sensors for a while. I am just getting around to trying it and see the long drama over getting this to work. I assume HA has been updated along with the zwave plugin since some of this thread was posted. Is there a current day way to get this working? Do the zwcfg.xml files from half a decade ago still apply? I tried the screenshot of the settings from last year and while I get the devices, they don’t update.

Thanks!

1 Like

I am also looking to revive this topic for “modern” 2024.2 HomeAssistant. There is long list of settings in the configure screen for the DSB09 device. Mine happens to be running firmware 3.60 and it worked with SmartThings a few years ago.
I’ve gone through several topics here on this. I am able to get reports from my HEM but only one every 6 hours or so (or the data only changes once every 6 hours).
I have Param 3 off (toggled earlier today), Power Change to 10W, percentage to 10%, automatic report group 1 enabled for each clamp and total, Report Interval 60 seconds for all 3 groups.

I don’t understand what the Groups refer to, the channels make sense (I have two channels and total). This particular device is connected to my mains so really just care about total on this one. Is there a need to repeat all settings across all three groups?

So has anyone recently installed/configured one of these? I think this topic is the most detailed and others point to this one.

Thanks in advance!

1 Like

Did you ever make progress with this? My home came with a DSB09 and I finally got around to connecting it to ZWave. So far the integration with HA seems pretty rough and I’m not sure how much effort this thing is worth. It is running firmware 3.60.

1 Like

@HAVAn They are very frustrating to use as it seems they don’t respond to configuration changes most of the time. I have three DBS09 running v3.60; one hem on mains, two hems with clamp for laundry washer, dryer, oven and hvac. The one on my mains only reports power changes once per 6 hours or so now. Not sure what got it into that state and haven’t been able to change it back to once per 60sec, or % based, or anything reasonable.

Aeotec support was very responsive but after emailing back and forth for couple weeks I have kind of given up hope. He did not have access to this model to test with but he did seem somewhat familiar with HA. The config screen in HA is pretty good I think compared to the way people used to have to configure it with older smart home platforms. They had to do the bitwise math to create the 5(?) configuration bytes. Home Assistant has 40 inputs and I assume creates the 5(?) configuration data bytes from that.

I’ll try to go through his emails and summarize a few key points to help understand these things.

Thanks for responding. My problems seemed to be cleared up just by getting a better signal on my ZWave network. I assumed I was having a lack of updates due to a bad configuration like I’ve read about in these old threads, but it actually seems to be working fine now that I have a signal established, with updates set to every 60 seconds. I guess fingers crossed it continues to work. I am trying to decide if its worth the effort/risk to update the firmware.

I updated the firmware on mine to 3.67 (removed, updated firmware, added), I didn’t notice any changes (would be interesting to know what changed in each version. They all sent data for about 30min then became unavailable. A few days ago I removed/re-added one HEM yet again for my Mains HEM, and it has been working well using automatic report (Selective Reporting OFF).

Finally someone who figured out the settings!

I’ve been fighting one of these (was a gift, got around to installing for EV plugs) and couldn’t get it working worth anything using the “config” dropdowns.

Doing a factory-reset and then setting the value 6926 (6912+14) for parameter 101, size 4, unsigned did the trick. Now even after a power-cycle I’m getting updates as expected!

Thank you!

1 Like

Or not. We had a power outage for a couple hours and now I’m back to no updates from power clamps.

I’d like to update the firmware on my gen1, but I am not seeing a way to connect it to a PC. Can you tell me how you updated yours? OTA?

Update: I can set the numerical parameters by hitting the button on the HEM after each change, as described. However, hitting the button does not help with any of the config “switches” and I’m not seeing updates at the specified intervals.

I don’t own this device, but I searched for a manual and found https://opensmarthouse.org/zwavedatabase/84. Under the Reference tab there is an “Advanced Functions for Developers” document. I opened the document, and found a section on upgrading the firmware:

Device Firmware Upgrades (DFU):

When upgrading software via DFU programs, remove the batteries from the HEM and plug in the USB cable from your computer to the HEM. Follow the on-screen instructions from the DFU software program to complete the upgrade. After a successful upgrade, remove all power from the HEM (USB and batteries) and exclude/remove the HEM from the old network.

According to another of your posts you have been in contact with Aeotec already for other help. Did you ask them about this at all?

See new topic: