this is not working, you need border-width, but this is only for the outside but not the inside lines any tipps? padding not working in my tests
Why are we discussing CSS stuff here?
Any idea how one can align the table so it shows all columns (instead of just cutting the content)? I think itās a classic styling or maybe a flex-table-card specific issue, isnāt it?
- type: custom:fold-entity-row
head:
type: section
label: Watchman Report
style: |
.divider {
background-color: transparent !important;
}
padding: 0
open: false
entities:
- entity: script.system_watchman_report_generieren
name: Watchman Report generieren
icon: ''
- type: weblink
url: /db21ed7f_filebrowser/dashboard/
name: Watchman Report ansehen (vollstƤndig)
icon: mdi:note-edit
new_tab: false
card_mod:
style: |
a {
text-decoration: none;
}
- type: custom:collapsable-cards
title: š Vorschau Report
defaultOpen: false
buttonStyle: 'font-size: medium; background-color: var(--divider-color);'
cards:
- type: custom:vertical-stack-in-card
cards:
- type: entities
entities:
- entity: sensor.watchman_missing_services
name: Fehlende Dienste
- type: conditional
conditions:
- entity: sensor.watchman_missing_services
state_not: '0'
card:
type: custom:flex-table-card
title: ''
entities:
include: sensor.watchman_missing_services
columns:
- name: Dienst
align: left
data: entities
modify: x.id
- id: id_state
name: Status
align: left
data: entities
modify: x.state
sort_by:
- id_state
style: |
ha-card {
border-width: 0px;
margin-top: -23px;
}
- type: custom:vertical-stack-in-card
cards:
- type: entities
entities:
- entity: sensor.watchman_missing_entities
name: Fehlende EntitƤten
- type: conditional
conditions:
- entity: sensor.watchman_missing_entities
state_not: '0'
card:
type: custom:flex-table-card
title: ''
entities:
include: sensor.watchman_missing_entities
columns:
- name: EntitƤt
align: left
data: entities
modify: x.id
- id: id_state
name: Status
align: left
data: entities
modify: x.state
- id: id_occurrences
name: Vorkommen
align: left
data: entities
modify: x.occurrences.split(':')[0]
- name: Zeile(n)
data: entities
modify: x.occurrences.split(':')[1]
sort_by:
- id_state
- id_occurrences
style: |
ha-card {
border-width: 0px;
margin-top: -23px;
}
Is it possible to have the referenced file Located In:- "automations.yaml:2754,2789" linked to the actual file, pretty much a hyperlink to automations.yaml:2754,2789?
Need help with this error message which shows up every time I restart HA:
Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:239
integration: Sensor (documentation, issues)
First occurred: 11:10:18 PM (1 occurrences)
Last logged: 11:10:18 PM
The unit of sensor.watchman_missing_entities (items) cannot be converted to the unit of previously compiled statistics (None). Generation of long term statistics will be suppressed unless the unit changes back to None or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this.
Go to Developer Tools ā Statistics. You may or may not be able to fix the issue.
Or exclude this from being kept in the statistics. Not sure why you would want this?
Ha. That just moves the issue. You then get this unfixable issue in Dev Tools Stats:
1 Like
You can just delete it now?
Nope. The entity still exists but is just not recording data.
You can disable the entities though. That clears the errors and stats issue.
1 Like
Well, the ting is that this entity generaliy works very well. Despite this error, it correctly reported several incidents this morning, so deleting our disabling it seems like a bad idea.
It seems like itās just in a special situation that this entity throws this error, but otherwise it works well.
How can i isolate the culprit and solve this without taking such drastic measures as killing the whole entity?
Set the UoM as entities (anything but none) via your customize.yaml, restart and click the fix button on the stats issue. Choose the recourse that works for you when prompted.
But, as said, do you really need this in the permanent longterm stats? Removing it from long term stats doesnāt mean you wonāt have any history. Youāll still have the normal history as per your recorder settings. That said, Iād even exclude the entity from there, because all you really need is the current state. Recording history will bloat your DB if you have a fair bit of missing entities, since all of those strings of entity IDs get stored in an attribute in your DB ā repeatedly.
Thatās a very good point, Sir. So, now Iāve added all three Watchman sensors to the exclude list of the recorder. However, that alone doesnāt solve the error, right? Itās just prevents recording of the states of these sensors.
Iām uncertain as to what UoM means and what it does. Could you explain a bit more? Perhaps a syntax sample?
Many thanks in advance.
Sorry, itās unit of measurement.
Do you use YAML?
No, fixing the stats issue is separate. This was just a separate recommendation.
Do you mean; Do I know how to use YAML (Yes), or did I use YAML to implement the Watchman Inetgration (No)
I asked, because the link I posted requires you to edit YAML.
You can do some things via the UI too, but I donāt use the UI for this kind of thing:
Ok, I think I can edit YAML fairly well, but only as far as I understand the objectives.
You wrote āSet the UoM as entitiesā. What does that mean?
First of all, thereās no configurable variable named Units-of-Measurements in the core integration. The closest I can find is one named unit_system which is either Metric or US.
Secondly, how can a variable be āset as entitiesā ?
last but not least, even if I did understand your proposal, what good would āsetting it as entitiesā do in terms of solving my problem?
Please explain in more (accurate) detail.
This link is about setting it in YAML: Home Assistant Core Integration - Home Assistant
This one is about using the UI: Customizing entities - Home Assistant
Letās go for YAML.
You need this in your configuration.yaml:
homeassistant: # you'll have this already
customize: # you might have this section already
sensor.watchman_missing_entities:
unit_of_measurement: entities # or items; see note below
I havenāt had to set a UoM for my sensor, so Iām not sure what went wrong in your case. Mine has UoM items, but it doesnāt matter too much in this case whether you set it to entities or items. You just need to set it to something other than none in order to fix the stats issue.
Letās continue this via DM or a separate post if youāre still stuck, since itās not related to this topic anymore.
Like Watchman, but it gives me an error I canāt findā¦
Hovering ālovelaceā it gives me : storage/lovelace:328
I went to the Raw Configuration Editor, but canāt find it.
Any idea ?
Hy community,
I have one issue with a group of spots which are used in an automation. If a spot gets unavailable, I donāt get a notification from Watchman, because the state of the group isnāt āunavailableā. How are you working with Watchman and groups regardings this topic?