Guys I cant get GPIO working on RPI5 any idea?
Another problem I face with Xiaomi cameras, cant get them to stream video to HA
Youâre using multiple deprecated yaml fields. One of which was fully removed close_comm_on_error
Happy to try and upgrade again without these, but are you sure they caused all these error messages related to a serial connection?
The config will not load if you have an invalid config.
The deprecation occurred
also that release
It will retry by default on empty if retries
is greater than 0, you have it set to 3. So all you need to do is delete them but keep retries: 3
You guys are seriously not suggesting entity-device-naming like above ?
In My âWorldâ entity-names is mend for the System to handle, the shorter the better, without to many âunderscore/dashesâ etc.
There are Multiple ways of âhandlingâ short-names, And these are also worldwide known âconceptsâ , or just find âinventâ your own, which make sense , in your head, and in reflection to your âproperty/environment/Devicesâ etc
And an Area can be whatever you want it to be.
I have 2 Areas in my TV-Room(Which Btw is an Area also ) so that makes it 3 Areas
I have Areas covering 2-3 Rooms
2-3 Areas(For Specific Functions, related to the heating system) in the PanRoom( Which is also an Area )
I have 4 outside Areas ( And i have not decided, or considered whether they should be âgroupedâ in a Floor ( seems ridicules to me )
I have 3 âBalconies/Verandasâ , Yes they are at itâs respective âFloor Levelâ, But itâs considered Outside Area
Garage, 3 step Down, or wheelchair slide if you prefer, No itâs not a floor(plan) Itâs a Garage period.
Cut loose, donât hang up your self on " Common Concepts, or Established structure " in Law and Planning" , you are blinding your self, and blocking your imaginations . Get out of your enforced paradigm , and use your âhiddenâ childish imagination , and logic
Great! some of your instructions Iâm doing already whenever I do a major change configuration but this is an extensive step by step.
Currently my automation do not start by an â_â
As soon as I perform the upgrade most likely I will probably try the migration and see how it goes. Thank you.
Ok, i dont know how i would have figured this out from the error message, but i tried it and everything works fine now.
Thanks you so much!
Looks like that HA doesnât fully support that caracter set like probably many others. Why you where expecting to be fixed in this version?
Watch out. He said -
, not _
.
One is a list, the other isnât.
Good catch! Thank you.
Youâve given me plenty of reasons to avoid the feature, since Iâd like to keep my config in packages. Thanks for the write-up.
How did you get that display?
Itâs the standard Gauge Card
Try sending Bram lots of to get that feature implemented!
Anyone else seeing energy dashboard glitching during a restart?
Awesome filtering options! Thank you
As a feature request i would like to suggest adding a way to edit the default âGroup byâ filter. Everytime I enter the Automations page I have to change the Group by to Areas instead of Categories
It should be, it was missing a set of credentials for some (not all) users, I think depending on the app they created an account with. The missing credentials were added, plus if you have any shared appliances you should be able to see those. Let me know if you have any issues, we donât have a ton of devices and logins to test with, but with what we were able to test with it was working fine.
Relplying to myself in case anyone was following. (I doubt it but donât like leaving the report hangingâŚ)
A second upgrade to .1 went fine.
Digging thru the logs on the snapshot that blew up MQTT, it was likely the age old problem of supervisor not waiting long enough for things to respond â and deciding to ârepairâ all the Dockers⌠which is well documented and generally ignored. Ha.
Cause: Shared storage was slow from other activities going on on it during the HA upgrade. Supervisor had a hissy fit as best as I can tell, and made it worse by reconfiguring every docker in the pile. Ha.
Just a known risk of running supervised I guess. It uses hard coded timeouts and has no real indication from the Docker that itâs busy or what the load average or iowait are on the hardware.
Well known issue. Throw faster hardware at it.
(In my case, avoid upgrades when shared storage is busy. Supervisor is brittle in that scenario. No big deal⌠my choice to use itâŚ)
After updating to 2024.4 my voice commands on echo keeps responding with the device is not responding. Any ideas?
Yes, I have the same problem.
Now I get this error and donât have any Homematic devices
2024-04-07 08:15:28.193 ERROR (MainThread) [homeassistant.config] Unknown error calling homematic CONFIG_SCHEMA - '<' not supported between instances of 'bool' and 'str'
2024-04-07 08:15:28.224 ERROR (MainThread) [homeassistant.setup] Setup failed for 'homematic': Invalid config.
Logger: homeassistant.config
Quelle: config.py:1564
Erstmals aufgetreten: 07:39:23 (1 Vorkommnisse)
Zuletzt protokolliert: 07:39:23
Unknown error calling homematic CONFIG_SCHEMA - '<' not supported between instances of 'bool' and 'str'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config.py", line 1564, in async_process_component_config
return IntegrationConfigInfo(component.CONFIG_SCHEMA(config), [])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 272, in __call__
return self._compiled([], data)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 595, in validate_dict
return base_validate(path, iteritems(data), out)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 387, in validate_mapping
cval = cvalue(key_path, value)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 818, in validate_callable
return schema(data)
^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 272, in __call__
return self._compiled([], data)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 595, in validate_dict
return base_validate(path, iteritems(data), out)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 387, in validate_mapping
cval = cvalue(key_path, value)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 595, in validate_dict
return base_validate(path, iteritems(data), out)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 387, in validate_mapping
cval = cvalue(key_path, value)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 595, in validate_dict
return base_validate(path, iteritems(data), out)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 387, in validate_mapping
cval = cvalue(key_path, value)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/schema_builder.py", line 818, in validate_callable
return schema(data)
^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/voluptuous/validators.py", line 755, in __call__
or 'value must be one of {}'.format(sorted(self.container)))
^^^^^^^^^^^^^^^^^^^^^^
TypeError: '<' not supported between instances of 'bool' and 'str'
This is my config, which has been working fine
# Homematic CCU
homematic:
interfaces:
hmip_gf:
host: 192.168.88.73
port: 2010
username: !secret hm_usr_admin
password: !secret hm_pwd_admin
resolvenames: json
hmip_gf_groups:
host: 192.168.88.73
port: 9292
username: !secret hm_usr_admin
password: !secret hm_pwd_admin
path: /groups
resolvenames: json
rf:
host: 192.168.88.73
resolvenames: json
username: !secret hm_usr_admin
password: !secret hm_pwd_admin
ip:
host: 192.168.88.73 #war 127.0.0.1
port: 2010
groups:
host: 192.168.88.73 #war 127.0.0.1
port: 9292
resolvenames: "json"
#username: !secret hm_usr_admin
#password: !secret hm_pwd_admin
path: /groups
wired:
host: 192.168.88.73
port: 2000
resolvenames: jsonp
username: !secret hm_usr_admin
password: !secret hm_pwd_admin
hosts:
gf_ccu3:
host: 192.168.88.73
username: !secret hm_usr_admin
password: !secret hm_pwd_admin