Hey Jason,
So you are not using any other refresh app like Pollster? For my Envoy system, Andreas actually suggested a refresh every 5 mins, how is 15 working out for you?
I too would like to eliminate the refresh throughout the night
Rick
Hey Rick,
Its working great, RM did a great job handling it and CoRE is doing just as great. The every 15 mins works great since SE only phones home like every 10 or so and it keeps us from hitting our 300 api call daily limit. Thanks for the app suggestion that thing is awesome.
I’m glad it worked out, Andreas has been great 
Tell me about the AND Trigger (not familiar with that) in your Piston
Rick
In the date time condition there is a variable for happens at and I just set it to every 15 mins. Sorry for the short reply typing on the phone lol
OK got it, another condition of date/time…
Thanks, i’ll see how it goes
Rick
Excellent let me know how it goes.
Really liking this new engine
Jason
Well, the refresh is working great every 5 mins (for me) but my graph is not updating
Might need to reach out to Andreas
Rick
I got it, darn DHCP… again
Need to fix that
Rick
The refresh rate depends on the service - Envoy logs data once avery 5 minutes, SolarEdge apparently only once every 15 minutes. In order to get the most accurate/smooth data you would want to refresh at the same interval that the monitor/service does.
The reason why I am using Pollster is historical - when I first set up things scheduling was broken so bad that you couldn’t rely on it. I set up Pollster with the external REST call to make sure that the polling happens when I want it to (I have an always-on server that has a cron job running the external call to Pollster). If scheduling is working correctly (which seems to be mostly the case these days, a solution with RM/CoRE which only polls during daylight hours would be nicer as it will quiet down the “Recently” list for the device. I guess I’ll have to give that a try myself 
You should really set up DHCP reservations based on MAC address on your router if it supports that. Set up once and forget 
Thanks Andreas,
Yes, i have mine set to 5 mins and the core Piston is working great so far
And researching DHCP reservations now
Rick
1 Like
Done (I added it to my ST-Envoy repository which you can link in the IDE and updated the ReadMe to mention the new DTH).
4 Likes
Installed, working, this device type looks great! Excellent work.
2 Likes
One bug, one feedback.
Bug:. Last Month kwH is the same as today’s kwH.
Feedback: Can you get rid of the decimal watts in the display?
Still awesome.
Try the latest version on Github (Version 0.1.2 (20160602))
It seems that “Last Month/Year” are not rolling values for the last 30/365 days but rather accumulative numbers for the current month/year (thus the number was identical to “Today” yesterday which was the first day of the month). I changed the labels and corrected the efficiency calculations to properly reflect this.
Anyone else’s stop reporting?
Getting this from live logging
2:24:52 PM EDT: error java.util.NoSuchElementException: Cannot access last() element from an empty List
d772a874-1e13-4451-8a8c-cf5d0f39b456 2:24:52 PM EDT: trace Querying DB for today’s data…
d772a874-1e13-4451-8a8c-cf5d0f39b456 2:24:52 PM EDT: debug New data: [overview:[lastMonthData:[energy:1378742.1], measuredBy:INVERTER, lastUpdateTime:2016-06-27 14:20:36, lifeTimeData:[energy:8454006.0], lastYearData:[energy:5992519.5], lastDayData:[energy:33089.273], currentPower:[power:6711.5]]]
d772a874-1e13-4451-8a8c-cf5d0f39b456 2:24:52 PM EDT: debug Requesting latest data from SolarEdge…
Mine is pulling in just fine.
Mine is fine also.
Jason, Brian, lucky dogs, mine stopped reporting about 2 weeks ago and no solution yet. Andreas believes it has to do with caching that ST implemented.
Really sucks
Rick
Ok, mine just stopped working in last day or two with this error upon refresh: 1:02:04 PM: error java.util.NoSuchElementException: Cannot access last() element from an empty List
Researching, debugging now, anyone have any ideas?
Diagnostics:
I can see it’s pulling data from SE (excellent, that would be the hardest to fix). Looks like a groovy issue with DTH, digging in more.
Issue is in this code. Power state table has data, but no data for “yesterday” so it is failing. Bug. Working on fix.
log.trace "Querying DB for yesterday's data…"
def powerData = device.statesBetween("power", startOfToday - 1, startOfToday, [max: 288]) // 24h in 5min intervals should be more than sufficient…
// work around a bug where the platform would return less than the requested number of events (as June 2016, only 50 events are returned)
while ((newValues = device.statesBetween("power", startOfToday - 1, powerData.last().date, [max: 288])).size()) {
powerData += newValues
}