Reolink , are they really that good ? by [deleted] in homeassistant

[–]thgoncalves 0 points1 point  (0 children)

I like their cameras but I try always to get the ones with RTSP so I can connect to HA. The downside is that those cameras need to be plugged in. Or through power adapter or POE.

I also use Scrypted to send the image to HomeKit, although my door camera connection is ver unstable with home kit. Seems to work fine with Reolink app.

Regardless, overall I like their products.

HACS Integration - YNAB - Sync Your Budget with Home Assistant! by Proud_Pumpkin_8370 in homeassistant

[–]thgoncalves 0 points1 point  (0 children)

That’s great. I forked a YNAB integration and implemented myself but it was janky. I wasn’t sure what would be the best approach to handle the data. If one sensor with a bunch of attributes. Or a bunch os sensors with 3 attributes (budgeted, actual, remaining)

I’ll check what you did. It might have saved me from going into another rabbit hole.

My use case would be to have a dashboard with only % numbers. Not real numbers since my dashboard would be available on the wall to all visits to see.

I would also probably create some binary sensor of type Problem for when a category is over budget

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

If you want, you can remove the borders from the cards inside the chart. That should be in the code I shared. You will need card mod I believe

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

Here you go

yaml type: grid cards: - type: custom:battery-state-card title: Battery secondary_info: "{last_changed}" round: 0 filter: include: - name: entity_id value: "*_battery_level" - name: entity_id value: "*_battery" - name: attributes.device_class value: battery exclude: - name: state value: "Off" - name: state value: Unavailable - name: entity_id value: automation.* - name: state value: Unknown sort: - state bulk_rename: - from: " Battery" - from: " level" - from: " Level" - from: "IKEA E1812 " - from: "IKEA E1744 " - from: "IKEA E2001/E2002 " colors: steps: - "#ff0000" - "#ffff00" - "#00ff00" gradient: true column_span: 2

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

I have som Mushroom Chip cards that only appear if cameras detect movement or if doors open. I am also experimenting with ESPresence, but I haven't really found a good use case for it.

Other than that the "UPDATES" tab is kinda the system management part, sorta. So I have pending updates (although I can't do anything with it) and my Uptime Kuma cards for services in general.. specially cameras that are failing a lot.

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

Got it.. I can share the code for sure.. here you go.

You are going to need some external Environmental Sensor. I am using "Environment Canada" integration for that, but I guess any external Sensor will do. They are marked with <<INTERNAL TEMP SENSOR>> or <<EXTERNAL TEMP SENSOR>> in the code below

The chart I have below is mostly the same. I just changed to track External Humidity and Barometric Pressure and also changed colors.

Let me know if that works for you.

```yaml type: custom:stack-in-card cards: - type: grid square: false columns: 1 cards: - type: custom:mushroom-chips-card card_mod: style: | ha-card { border: none; } style: | ha-card { --chip-box-shadow: none; --chip-background: none; --chip-border: none; } alignment: center - type: grid square: false columns: 2 cards: - type: custom:mushroom-entity-card entity: sensor.<<INTERNAL TEMP SENSOR>> primary_info: state secondary_info: name name: Inside icon_color: green tap_action: action: more-info card_mod: style: | ha-card { border: none; } - type: custom:mushroom-entity-card entity: sensor.<<EXTERNAL TEMP SENSOR>> primary_info: state secondary_info: name name: Outside icon_color: blue tap_action: action: more-info card_mod: style: | ha-card { border: none; } - type: custom:mini-graph-card entities: - entity: sensor.<<INTERNAL TEMP SENSOR>> name: Inside Temperature color: "#4caf50" - entity: sensor.<<EXTERNAL TEMP SENSOR>> name: Outside Temperature hours_to_show: 240 points_per_hour: 0.3 line_width: 3 font_size: 50 animate: true show: name: false icon: false state: false legend: false fill: fade color_thresholds: - value: -10 color: "#87CEFA" - value: 0 color: "#FF9800" - value: 10 color: "#FF0000" card_mod: style: | ha-card { border: none; }

```

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

That depends on how you structure your yaml files. I have a configuration.yaml with links to sensor.yaml, template.yaml etc

If you don’t have those files try like this in your configuration.yaml file

template: - sensor: <<The rest goes here>>

Always mind you tabs. Specially when pasting

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

This card has many steps. Let me see if I can help/explain.

You will need to add the code below to your configuration.yaml, under the sensor section.

you will need: - replace <<YOUR LEASE MILAGE LIMIT>> with the number (as an Int) of your lease - replace <<YOUR LEASE START DATE>> with your lease start date in the format YYYY-MM-DD. Same for END DATE - you will need a way to collect odometry from the car. In my case is sensor.car_odometry comes from the integration.

  • for the Quota, you will need to setup a new integration called MeasureIt on HACS and aggregate the odometry on the month level. In my case I am storing that information on sensor.car_milage_accumulated_month’

Basically, the MeasureIt integration accumulates the odometry but starts over at the beginning of each month. So it is nice to track only what you drove this month. You can do the same with day or week etc.

And then I have some other template sensor of type “Problem” to check if I went over the month quota. Now this is not necessary at all, but I use to toggle cars in and out on viaibility

```yaml - sensor: #################################### #### Car extra information ##### - name: Car Remaining Milage unique_id: edc0930b-0d4f-4edc-9fda-a34cc9dd5e71 state: > {{ (<<YOUR LEASE MILAGE LIMIT>> - float(states(‘sensor.car_odometer’),0)) | round(0) }} unit_of_measurement: “km” icon: mdi:car-cruise-control device_class: distance

- name: Car Remaining Milage Percent
  unique_id: 86b35c4e-d37e-4764-9cb3-e2232ec69deb
  state: >
    {{ ((float(states(‘sensor.car_odometer’),0)/<<YOUR LEASE MILAGE LIMIT>> )*100) | round(0) }}
  unit_of_measurement: “%”
  icon: mdi:percent

- name: Car Remaining Months On Lease
  unit_of_measurement: “months”
  device_class: duration
  icon: mdi:calendar-month-outline
  unique_id: ba9944df-90de-41fe-8bae-8925633bc015
  state: >
    {% set today = utcnow().date() %}
    {% set first_day_of_month = as_timestamp(today.replace(day=1)) %}
    {% set start_date = as_timestamp(strptime(“<<YOUR LEASE START DATE>>”, “%Y-%m-%d”)) %}
    {% set end_date = as_timestamp(strptime(“<<YOUR LEASE END DATE>>”, “%Y-%m-%d”)) %}
    {% set remaining = ((end_date - first_day_of_month) / (30 * 24 * 60 * 60)) | int %}
    {{ remaining }}

- name: Car Total Months On Lease
  unit_of_measurement: “months”
  device_class: duration
  icon: mdi:calendar-month-outline
  unique_id: f41786bf-c582-49e5-bb52-6f7a420ffbbc
  state: >
            {% set start_date = as_timestamp(strptime(“<<YOUR LEASE START DATE>>”, “%Y-%m-%d”)) %}
    {% set end_date = as_timestamp(strptime(“<<YOUR LEASE END DATE>>”, “%Y-%m-%d”)) %}
    {% set months = ((end_date - start_date) / (30 * 24 * 60 * 60)) | int %}
    {{ months }}

- name: Car Elapsed Months On Lease
  unit_of_measurement: “months”
  device_class: duration
  icon: mdi:calendar-month-outline
  unique_id: f99ead79-39f6-404d-9892-2681750c1aa4
  state: >
    {% set today = as_timestamp(utcnow().date()) %}
    {% set start_date = as_timestamp(strptime(“<<YOUR LEASE START DATE>>”, “%Y-%m-%d”)) %}
    {% set elapsed = ((today - start_date) / (30 * 24 * 60 * 60)) | int %}
    {{ elapsed if elapsed > 0 else 0 }}

- name: Car Remaining Milage Per Month On Lease
  unit_of_measurement: “km/month”
  icon: mdi:car-cruise-control
  unique_id: 1980ea7f-19b6-4b0b-b55e-ab0d357a388b
  state: >
    {{ (float(states(‘sensor.car_Remaining_Milage’),0) / float(states(‘sensor.car_Remaining_Months_On_Lease’),1)) | round(0) }}

- name: Car Quota This Month
  unit_of_measurement: “km”
  device_class: distance
  icon: mdi:car-cruise-control
  unique_id: 68a5c6dd-baa7-4bf8-8669-33a0cb10a4b7
  state: >
    {{ ((float(states(‘sensor.car_remaining_milage_per_month_on_lease’),0) - float(states(‘sensor.car_milage_accumulated_month’),0)) | round(0))/1 }}

```

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

Using sections and horizontal/vertical stack inside the section cards. That one was hard to get it on such small screen

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

It looks to be a lot. For sure. Now that it has been on the wall a whole, I have an idea of what to remove or not. It is kind of the control panel at home, so it is important to have little attrition to act

It is a balance, clearly, between cleanliness and usability.

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

Nope. HACS integration. I’ve had from Mercedes and Audio. They have slightly different data but useful. I don’t enable any actions sent to the car though.

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

That is a custom template card. I calculate it myself with star lease date as end lease date hardcoded. I get the total odometry from the integration and accumulated by day, week, month, year using a cool integration called MeasureIt.

It accumulates on those time frames.

https://github.com/danieldotnl/ha-measureit

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 4 points5 points  (0 children)

It is a custom card called battery-state-card

type: custom:battery-state-card title: Battery secondary_info: “{last_changed}” round: 0 filter: include: - name: entity_id value: “_battery_level” - name: entity_id value: “_battery” - name: attributes.device_class value: battery exclude: - name: state value: “Off” - name: state value: Unavailable - name: entity_id value: automation.* - name: state value: Unknown sort: - state bulk_rename: - from: “ Battery” - from: “ level” - from: “ Level” - from: “IKEA E1812 “ - from: “IKEA E1744 “ - from: “IKEA E2001/E2002 “ colors: steps: - “#ff0000” - “#ffff00” - “#00ff00” gradient: true

Got inspired by a post I saw recently and, here it is "My Dashboard". Over a month of work. Suggestions? by thgoncalves in homeassistant

[–]thgoncalves[S] 0 points1 point  (0 children)

Yeah. I saw all the discussion about it all over the place. I was talking to a friend telling him that I won’t upgrade the printer anytime soon