Look at the parent folder of a users github to find the list of things they’ve created.
That is the latest I see, updated 15 days ago.
2 Likes
The latest is:
03-29-2017 : Made changes to account for ST v2.3.1 bugs with text rendering.
and the code can be found here: (make sure to get the RAW file to ensure you’re copying all of the code)
2 Likes
@johnconstantelo I’m getting wild numbers for energy - I believe you put in measures to prevent this with power. Is it possible to do something with energy? Maybe filter out any value that isn’t within 1 kWh of the previous value? I guess that might be an issue when resetting energy usage? This seems to have started in late March for me.
Sometimes it is a low value - here you can see it is just a decimal point issue.
Sometimes a high value - here I have no idea, but you see it returns to normal.
Wow, now that’s not something I’ve seen before. Does that happen after you reset energy values?
I use your reset app to match up with my bill. But I’ll reset early and see what happens.
Edit - but yes this shows it across resets. April seems worse than March.
Hey John - still having the same issue after two resets. Any other thoughts or suggestions?
Hi @greg, I honestly have no idea why that’s happening. Have you updated the firmware yet? If not, give that a try. If so, maybe resetting the device? I’d hate for you to lose any automations, but if you reload the firmware (even if you’ve updated) it will do a factory reset - and then you can do a Replace in the mobile app and rejoin the device and not lose your automations.
1 Like
@johnconstantelo - If I am not using batteries, should I still use this DH?
Hi @whoismoses,
Yup! Just go into the device’s preferences and turn off the option to display battery info:
1 Like
Just wanted to respond in case anyone else sees an issue like this - so today I was going to update the firmware to try to fix my issue. But I checked and I’m not seeing those crazy values in my chart. For a moment I thought oh, well maybe it was a google sheets issue. But then I remembered that I screen shotted those values from the IDE. Anyway, my issue appears to have fixed itself, retroactively? I made no changes and offer no explanations.
1 Like
I’m trying to understand the frequency of power data updates I’m getting. I’m using the latest DTH (03-29-2017 version), and have set the update period to 21600s (~6hrs) - -yet I’m still getting on average 6 to 7 updates per hour for each of the two HEMs (v1) I have. I do have reportType=0 selected. There doesn’t seem to be a correlation between the update rate I select and what I am actually getting.
I turned of the ST “device health” feature too, thinking that may’ve been causing additional poll events.
Any ideas? bump… @johnconstantelo
Related question: when using the reportType=1 option, there are knobs for both percentage change and minimum watts value change to trigger updates… are those two qualifiers used as an “OR”, or as an “AND” function?
(Only reason I care about the update frequency is that I’m using grovestreams to capture my power data, and last month I ran into an overage on amount of IO that was allowed, and suspect the power data was behind that.)
thanks
Hello, could you possibly tell me how you built this graph?
I actually found that last night and got it all hooked up, great post.
2 Likes
It almost sounds like the HEM isn’t getting config data saved/received. I’ve seen this happen when the device is joined close to the hub and then moved away a fair distance. I’ve had trouble with my HEM reporting when I did that, so I did a factory reset and did a Replace in the mobile app to rejoin it at it’s permanent location. Doing this preserved the device in ST, which allowed me not to have to redo all the SmartApps associated to the HEM.
Have you updated the firmware yet? I don’t have the release notes, other than it’s suppose to help resolve crazy high readings.
After you set the reportType and interval, and then click Done, what does the IDE show for Preferences for the device? It should look similar to this:
I believe it is an OR condition from what I’ve experienced. Here’s what Aeon’s documentation says:
The HEM also has the ability to reduce network traffic by reporting only when there is a significant
change in wattage draw (configurable either by percentage or wattage increase).
I did join the HEM(s) near the hub, then moved them far away. Never
updated the FW, did not see any compelling fix when I checked the revision
docs - will do that when I get some time.
The preferences in IDE look to match what I configured the device to.
Will see what the FW update/refresh/rejoin does to improve the behavior.
thanks!
1 Like
man… I should not have purchased this GEN5…
Why would you say that? Did you intend to get the v1 instead?
nothing but problems, only one clamp seems to be providing me with anything but the number 0 on my split phase US install…I don’t get it, I installed it correctly too. Seems like v1 allows for more tinkering. Any ideas why I am showing no pole data for my second clamp? I can switch em, provides the same result only visa versa…
