Should I create two sun-monitor devices when I have PV panels in two orientations, e.g NO and ZW?
In that case, can I someway add the two devises together?
Connecting two or more inverters to a single electricity meter (e.g., HomeWizard) works perfectly. An added benefit is that an electricity meter provides much better data than an inverter. Three arrays are set up this way at my mother’s place. The forecasting is impressive.
@Gruijter Using the (just added) solar panel device and settings:
The result is:
Maybe this behaviour is intended, but it seems the year start value is used for both the year and month reported values. Both ‘month start’ en ‘year start’ values are added manually after creating the device.
As of August 1st, Zonneplan is also switching from hourly to 15-minute rates. Naturally, I’ll just set up a 15-minute rate device. But can I continue using the same hourly flow cards? Or do I have to convert everything to period flow cards?
Depends what you want to achieve. You can keep the existing 60m DAP device and flows. But prices will be averaged per hour.
If you want to optimally use the 15 minute prices you need to create a new DAP15 device and new flows.
edit: I was on an old version that caused some issues when moving to 15 minute rates, didn’t realize that. Solved after updating.
@Gruijter I have a weird bug in the Power by the Hour app Version v8.4.1 TEST. When I use the “Provide prices JSON for This day” card it sometimes gives me all the same values. For example at this moment the output is:
[0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381,0.3381]
Even though the preview shows:
{'0':0.2747,'1':0.2678,'2':0.261,'3':0.2606,'4':0.2672,'5':0.2721,'6':0.272,'7':0.2678,'8':0.2625,'9':0.2516,'10':0.2409,'11':0.2317,'12':0.20,'13':0.15,'14':0.12,'15':0.11,'16':0.12,'17':0.20,'18':0.2772,'19':0.2927,'20':0.3052,'21':0.2944,'22':0.2856,'23':0.2725}
The weird thing, this is not always the case. sometimes it works just fine.
The card “Provide prices JSON for tomorrow” works just fine. Current output using the same method:
[0.3424,0.3356,0.3277,0.3276,0.3281,0.337,0.3468,0.3465,0.3369,0.3196,0.2984,0.2491,0.2024,0.1736,0.1736,0.2008,0.2598,0.2941,0.3075,0.3461,0.3673,0.3838,0.3778,0.357]
Any idea?
The “preview” uses sample data in general AFAIK.
Ah, I did not know that. Still the data that gets delivered in the tag is incorrect. I am sure it should not be a flat “0.3381” 
Hi all,
I’m trying to set-up a small battery for a “nul op de meter” deployment. With flows (manually building one) seems to be hit or miss when it’s charging. It will only get worse if i introduce an extra battery…
I’ve found this app and it seems it can do it for me (smoothing one or two batteries). I think it’s called XOM? But i don’t understand how it works and how to implement in in flows?
Would anyone care to let me know if i can do it with this app and how or where to look/read?? 
My Homey is from 2019 and i’ve added the Zendure SolarFlow 800 Plus to Homey already.
Thanks!
Hi
Just to make sure, is the card in the picture using the number of 15min periods when checking the lowest value when the actual device is 15min period device? Or is this card checking the lowest hours before 7 o’clock in this case. I’m getting activations of this card too often so trying to track where I have made a mistake.
New version 8.10.0 is ready for testing: https://homey.app/a/com.gruijter.powerhour/test/
- Many stability improvements
- Reduced memory footptint and lazy loading
- Extensive review and revision of time handling functions
- Fixed grid forecaster
- Homey-api@3.19.2
This version focuses on stability. Memory footprint is significantly reduced for users that do not use all drivers. Some app crashes were fixed, and all functions/flows that use time or time windows have been extensively reviewed for edge-case issues.
New version 8.10.1 is ready for testing: https://homey.app/a/com.gruijter.powerhour/test/
- Behind the scenes preparations
- Added app-2app pricing api @Menno_De_Braak please test extensively!
- Massive README rewrite
This version opens up the Day Ahead Prices from Power By The Hour to other apps and Homey scripts. For instance the app Ultimate EMS will be using this to get Day Ahead prices.
Other Homey apps and HomeyScript can query prices or listen for real-time slot pushes via the new PBTH Inter-App API:
GET /dap-prices— fetch all current future price slots (use once during app init)- Realtime event
dap-prices-updated— emitted on slot changes and price updates.
See README.dap-api.md for full API reference and code examples.
While at it, the PBTH documentation was completely rewritten to describe use cases and how to set that up: [APP][Pro] Power by the Hour: Insights per hour, day, month and year
New version 8.11.0 is ready for testing: https://homey.app/a/com.gruijter.powerhour/test/
- Behind the scenes preparations
- Charts upgrades
- Massive memory spike reduction
The graphs, especially battery monitor, have been updated/upgraded. It now shows yesterday, today, tomorrow or next hours, similar to DAP. It now also includes the planned/real power and SoC.
Secondly a major app stability improvent was introduced by significantly reducing overall and spike memory usage. This should prevent Homey from killing the app.
How do I get this image in Battery Monitor?
I have the Nexus, but I don’t see this option.
Is this because of the Zonneplan app in Homey?
If the Nexus app is using the (relatively new) default capabilities that Homey has defined for batteries PbtH should be able to pick it up.
New version 8.12.0 is ready for testing: https://homey.app/a/com.gruijter.powerhour/test/
- Fix multiple flows
- Fix charts
- Fix power sign handling
- Fix data source fetching
- Fix SoC and Power Insights fetching
- Fix Solar timezone handling
- Fix updateMeter bug
- Add graph settings
Multiple important fixes in this version. So if y’all test it to be good, I will release it as stable asap.
New version 8.13.0 is ready for testing: https://homey.app/a/com.gruijter.powerhour/test/
- Added grid directional settlement schemes for import/export netting
- Added peak demand (capacity tariff) tracking for grid
- Fixed grid weekly load forecast accuracy
- Fixed EV charger pairing, SoC chart, and retrain button
- Fixed capability migration and naming
- Improved min/max power detection accuracy
- Replace xml-js with fast-xml-parser
- General stability improvements
This has many ‘under the hood’ changes and preparations for future app releases.
BREAKING CHANGE: the min/max power tracking capabilities have been changed (improved)
Homewizard app will use this API to get prices (v3.19.1) for the battery policy.
