@SimoHDK - have a look at the latest release. Total cost is provided by the HA energy management function. This integration does not otherwise retrieve any cost/compensation data from Solar Analytics. I use the Amber energy integration and am able to calculate 5 minutely updated imported and generated costs for charging my car, heating-cooling and hot-water generation. Please get in contact if you would like further ideas.
Please note Release 5 of the code has been published on github. There and many enhancements and extra sensors. See …
Hey Peter,
Awesome work on this, I picked up your original code in December 2021? and only just now seeing all the updates.
With the SA data for Aircon, Electric car etc, is that coming from SA or you assigning a separate entity to it?
Hi @hyboi1 - sorry just saw your question now. I’m no longer actively monitoring this thread because it’s practically closed. For future matters I suggest you add to the discussion on github - specifically the release 5 discussion -
The energy usage for the EV, AC, hot water, stove oven all come via the solar analytics API. I’m not sure what you mean by “or you assigning a separate entity to it”?
Rgds, Peter
All your data like Energy Total Net Cost, EV, water, etc
I don’t get that from my SA. Is it sth else you bought?
Not sure if it’s due to the solar analytics 3G shutdown forcing buying the 4G dongle and installing again.
I got the basics in the energy tab from b4 and that’s it.
Thank you everyone for the amazing work, getting there with my integration between the great work @PeterH24x7 has done and @ddwdiot have been sharing.
@andypnz Can you share your code to access the other CT clamps, I can only seem to find one but I know I have two (one on the shed and one on the spa) as I can see them in the Solar Analytics dashboard. I have tried a number of combinations for example.
json_attributes_path: “$.data.[2].[0]” Is shed (Working YES!)
json_attributes_path: “$.data.[2].[1]” no change from above
json_attributes_path: “$.data.[3].[0]” Looks like Solar generation
json_attributes_path: “$.data.[1].[0]” Solar export to the grid
json_attributes_path: “$.data.[4].[0]” Not working
json_attributes_path: “$.data.[5].[0]” not working
TiA
Solved it !
it was
json_attributes_path [0] [0]
Being a complete noob I didn’t know you could use a 0
Hi @ddwdiot , just came across this post from you when searching for nemy in this forum. You indicated that you have a Lifx bulb tracking the NEM pricing using nemy. Is this correct? If so what Lifx bulb model is this? I was looking at nemy as it provides real-time dispatch pricing at 5 minute intervals but has a hard limit of 200 requests per month before you have to subscribe to a $25/mo plan. Would this bulb have the same limitation?
Hi @menaibluey - Not sure I can be very helpful here as I no longer have that bulb set up (has been repurposed). And this is perhaps off topic as the bulb’s colour changes were via IFTTT and nothing to do with Home Assistant. I can’t recall exactly what bulb I used but there was nothing special about it other than it was a Lifx bulb so worked with IFTTT. I’m no expert but I don’t think the bulb would have anything to do with the request limitation… guessing that’s more about Nemy and IFTTT. Sorry I can’t be more help.