💵 Lovelace: Personal Capital Plugin/Card

#1

I’ve created a custom component for Personal Capital (US only, sorry) that grabs account details into sensors with an accompanying custom card to show the data on the frontend.

image
image.png886×758 12.5 KB

You can pick which categories you want to monitor in the component and each category in the card is expandable to view details on balances and when data was last refreshed. I hope to add more features over time, primarily to the card, but wanted to share my current progress. Enjoy!

configuration.yaml

sensor:
  platform: personalcapital
  email: [email protected]
  password: 12345
  unit_of_measurement: CAD
  monitored_categories:
    - investment
    - cash

lovelace

resources:
  - url: /local/pc-card.js?v=0
    type: module
.
.
.
      - type: custom:pc-card
        title: Money
1 Like
#2

So this could be used to simulate being on an electricity meter? When you run out of cash all the lights turn off?

#3

I don’t know how that would work

#4

I don’t know how that would work

It’s probably best that it doesn’t :wink:

I was wondering if this model could support the Open Banking API, but it seems the API is only for use by "registered third parties’ which seems to rule out open source implementations.

#5

Ah, I see. Yes, you need to be able to connect it first via Personal Capital service which is far from a complete list of all institutions.

#6

Used this for a bit, but awhile ago it broke so I removed it. I am now reenabling it and for some reason can not get this darn custom card to work.Keep getting custom element doesn’t exist. PC is configured and works.
For the Lovelace config I have the pc-card.js saved in my /www. I tried changing the url in my LL config to /pc-card.js?v0.0.3, didn’t work.

In my Lovelace:

resources:
  - url: /local/pc-card.js?v=0
    type: module
    .
  - type: custom:pc-card
    title: Money

am I missing something here?
are package.yaml required now? my other custom cards/plugins work without it

#7

If you go to /local/pc-card.js do you see the file?

#8

yes it is in my /www folder. config/www/pc-card.js

I copy and pasted newest raw text from GitHub to see if that was the issue, still didnt work. Maybe I am missing a step?

log:

http://hassio.local:8123/local/pc-card.js?v=0:3:24 TypeError: undefined is not an object (evaluating 'Object.getPrototypeOf(customElements.get("hui-error-entity-row"))')
#9

That code was removed in February. You likely need to clear your cache

#10

ahhhhhhg. so simple. thank you!

1 Like
#11

Possible to have the sensor history display more than one day of history?

#12

It grabs whatever is available, so no

#13

I don’t understand… (this is when I start pulling up other sensors and see the few I check all only show one days worth of statuses (I think I was thinking of the frequent changes in the weather plugin and didn’t think past that) )…Oh. I see now…

I’m pretty new to this whole ecosystem… but would something like Grafana be a possible solution? …I imagine there has to be a parallel somewhere… ie: if you wanted to track your energy consumption over time… or your network usage… lots of things have data that would be better reviewed through a larger scope… having an easy chart to look at might make it easier… progress becomes easier when you see the effect of previous efforts?

#14

I totally misunderstood your initial question. The history of a sensor is dictated by the recorder and is by default set to 10 days.
That being said, when you look at a sensor via more-info, only the last 24 hours is shown. If you want to see more, look at the history panel or add a history-graph to your frontend and extend the hours:

#15

That makes sense… it also sounds like something better left until I move my install from SD-based to SSD or HDD-based.

Thank you very much. (Bonus points for the answer that points back to HA in the larger sense.)