-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entity does not exists & less than 1 undefined #20
Comments
I am having the same exact issue. It appears that an MQTT entry is created, however, the time stamp is invalid. This is my config type: 'custom:check-button-card'
title: Brushes
entity: sensor.naomi_brushes
text: month(s)
color: Green
severity:
- value: 6 months
color: Red
- value: 4 months
color: Yellow
This is the corresponding MQTT data that is sent when I click the button {
"timestamp_friendly":"Invalid Date",
"severity":[
{
"value":"6 months",
"color":"Red",
"seconds":15778476
},
{
"value":"4 months",
"color":"Yellow",
"seconds":10518984
}
]
} Any suggestions? |
@DunklerPhoenix Since things don't appear to be very active around here... Might I suggest that you somehow redue the number of potatoes that need sucking up? This would eliminate your problem by removing the need to monitor your Kartoffelsauger. |
Any update on this? This is my mqtt payload: edit: I've found out that he does this after every hass restart. edit2: The solution was to add discovery to mqtt.
|
Had the same issue. This also happens if your mqtt server does not have persistence, e.g. data is lost after restarts, basically mimicking the problem above, but no way to fix it without deleting the entity in HA first. |
Heho.
I have two problems.
The first one is the creation of Entities. The entered sensor entities does not exists thats correct, then I click on "Create" and the bar becomes green, but after a reload its blue with this message again.
What can I do against this?
The second problem is that the text shows "less than 1 undefined" even after I entered the "text" value. Is this problem related to the first?
Greetings
Marco
The text was updated successfully, but these errors were encountered: