Got it, thanks!
What do you mean with “@4.2x”?
For how long have you being using it? How’s the reliability?
Thanks for sharing your situation/ideas!
I use Wasabi too, I was thinking about having another option with data spread across different devices, with extra devices for safety (like SIA). Thanks for your point of view and for the suggestions!
Have you found a way to stream Netflix at 4K?
Well, if you have a look at some examples that @stalker@lemmy.ml posted in a comment here, you can see that’s not impossible and that somebody is already doing it.
Question: why don’t you crate your own Grafana dashboard? Do you have too many servers?
The internal entities, like Helpers, are immediately available
This is my problem:in my main HA instancd the internal entities are in state “unknown” when I reload the configuration. In another instance of HA everything works fine and the thermostat goes back to their previous state when I reload the configuration, in the “main” instance they don’t :(
Yes, the history of there, with some blanks around the time I’ve done some config reload
The recorder was indeed already enabled, I’ve noticed from the home-assistant_v2.db file. Nevertheless I’m still losing everything when I reload the config. I’m not using docker, but HA OS. Any other…shot in the blue? 😁
Ah, interesting!!!
I’ve tried enabling it just by adding recorder:
in it the configuration file that, if I didn’t get it wrong, should record everything without exclusion, but…it doesn’t sensors/switches/thermostat setpoint and state are lost at config reload.
Am I doing something wrong?
I’m sorry if you think that I’m wasting your time. From my point of view, it’s the other way around since all it’s written in the OP! And you still saying to run a packet capture means you didn’t get the point or you know HA less than me!
No, my problem is not just the thermostat! All the sensors and switches loses their state, but while they get them back in a while kapart from the battery powered sensors), the thermostat has to be set back manually.
The thermostat is an entity in HA, there is no phisical thermostat! It’s a generic thermostat!
HA doesn’t query any state. The thermostat is within HA, it doesn’t have to query anything from anything, that’s what I’m investigating. The setpoint is set in HA and HA retains that number.
For MQTT that’s the retain flag, but for HA I don’t know what that is and I really need it!!!
Since the updates comes from the devices and ate not requested from HA, some exposes their statuses in less than a minute, some (like temperature sensors that are battery powered) sends their statuses very less frequently (if the temperature doesn’t change, they communicate every 30/40 minutes.
Oh, I’m rooted, I didn’t know that.