[OBSOLETE] Aeon HEM v1 DH Discussion (DTH link in post 411)

I’ve done this so we’ll see how it goes.

BTW, I just updated to the 3/11 version of the handler and now the font is so small on some fields I can’t read it on my phone. And the kWh and cost fields have superfluous text. This is iOS.

It’s not a DTH issue. You can thank SmartThings for introducing more text/rendering issues in their latest release of the Android and iOS phone app.

The kWh and Cost text will fix itself when the values change.

1 Like

Okay. I was aware of the Android issue with v2.3. I didn’t realize iOS was affected too as I had not had the issue with anything else.

They have. It seems trailing zeroes are being dropped now too. So I have a cost of $8.4, not $8.40.

Does this device act as a z-wave repeater when powered from AC?

Is there a dh that has the ability to change at set times throughout the day for my electric companies 3 different rates. Would be nice for better energy monitoring, especially on figuring actual cost of electric water heater.

A DTH really can’t do that because it doesn’t/can’t schedule anything by itself like that. That’s where a SmartApp is needed.

I don’t believe so, and I can’t find anything saying it is, or isn’t.

Can someone clarify how measurement updates actually work with the (latest) @johnconstantelo DH?

I have a USB-powered HEM v1 device, recently installed, and am playing with isolating what devices are behind my unexpectedly high power baseline… I’ve noticed a LONG delay (sometimes minutes) between when I turn stuff on/off and the change gets reflected in the reported power number, even after repeatedly pushing the “REFRESH” tile in the app.

Does the “REFRESH” cause the HEM to perform a measurement, or does it just cause it to report back the most recent (possibly locally stored) measurement it had taken? I’ve configured it to report type 1 (watt change based), and set a 25W change threshold.

I kinda expected to see an updated power number after a few seconds, without having to push “REFRESH” - but thats not what I’m seeing. Sometimes its fast, other times it is a very long time.

As you’ve discovered, based on the parameters in Preferences. I have mine set extremely low because I’m not worried about zwave traffic on my mesh. I’ve been running like this for well over a year without any issues with the device or zwave mesh/performance problems.

I’m not seeing any delays whatsoever when tapping on the Refresh tile, or the main tile. The refresh sends the most current reading at the time a refresh command is sent.

I just tested my performance by turning on a set of 6 “regular” bulb ceiling lights, and within 2-5 seconds I saw the main tile update. I saw the same performance when turning them off.

If you’re seeing really long delays I’d suspect you could have a zwave device on your mesh that could be behaving badly, and/or not routing at all. Assuming you have other zwave devices (routing capable), are your lights performing slow? Does the IDE show in the hub’s event log any of your zwave devices reporting as “not responding”?

Could be a route issue, I have seen the HEM show as “device unavailable” in the app occasionally.
Checked the livelogging and also the hub event log, did not see any non-responding error messages. Updates seem quick right now, I’ll do more testing and log checking tomorrow to see if I can capture one of the “long” response delay events.

BTW, does the “REFRESH” tile have the same effect as pushing the main tile screen?

Checking the device log this morning, one thing I notice is that the HEM sometimes goes “offline”, during which time it does not report a change in power that happens (example below). It then came back online after a bit, but did not report any updated power value. When I refresh it via the app, it then sends the updated power value.

I don’t see any error messages in the hub’s event log related to non-response to messages.

Wondering if I should switch to interval-based reporting rather than power-change to trigger updates?

Does the “going offline” imply a problem in the network? Not sure how to further track that down (falling on my limited ST debug skillset sword).

Yep, sure does.

Are you running on batteries instead of USB by accident (cable not plugged in right)? The HEM should technically never go offline if it’s USB powered and your mesh is healthy. I’ve only seen mine go offline when I’ve had zwave mesh problems.

Is the LED solid red, blinking, or off?

In your event log image, it looks like you were offline for 22 minutes. If you don’t have batteries installed, did you loose power?

Is the HEM far from the hub? If so, what other routing capable zwave devices do you have in between the HEM and hub? Perhaps check on those to make sure are working fine.

Its USB powered, not batteries installed. No power outages to my knowledge.

The LED is solid red, at least when I’ve checked it. Next time I notice it being “offline”, I’ll check then.

The HEM is the farthest device from the HUB, but there are several intervening powered wall switches that should be acting as repeaters. The nearest ones are <20’ from the HEM, with the HEM one level below them (i.e. wood flooring in-between). I originally paired the HEM next to the HUB, moved it to the final location for install, and then repaired the ZWAVE network afterwards.

The nearby switches respond pretty quickly to the ST app, a bit slower when I trigger them through ALEXA but I think that additional delay is ALEXA induced.

I’ll also try a repair of the ZW net again, and livelog during the process to look for any odd responses.

1 Like

Change 03-27-2017:

Added a new device Preference that allows for selecting how many decimal positions should be used to display for WATTS and kWh. Min/max values still use 3 positions, as well as what’s stored for the actual meter reading that’s seen in the IDE for Power and what’s sent to SmartApps (like ones sending data to logging apps).

https://raw.githubusercontent.com/constjs/jcdevhandlers/master/devicetypes/jscgs350/my-aeon-home-energy-monitor-gen1.src/my-aeon-home-energy-monitor-gen1.groovy

2 Likes

I had a prior version ‘no battery in title’ decided to use latest one of 03/27 but now i have tiny text.

I hit refresh on all the buttons/tiles and nill results.

I even did a z-exclusion to remove then readded the device but No dice.

Hit configure, then all the reset buttons, then refresh.

I finally got around to cleaning mine up. It’s almost relaxing to look at now.

2 Likes

Tried that on my iPhone does’t change the text, so small can’t even read it.

Mine is small but not unreadable. Wish ST could get this figured out between Android and iOS.