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
Was there an intentional change in the behavior of the timer integration? Previously the state of the timer would always change to idle before the timer.finished event fired, now it always changes after the event fires. This breaks some conditional logic i was using in some automations.
Have no idea is my issue related to .4 or not.
Got a very crucial issue while attempting to test another issue.
A whole storage-mode dashboard was replaced by another storage-mode dashboard - i.e. I got 2 (almost) same dashboards:
- Assume dashboard_1 has 20 views, dashboard_2 has 10 views.
- You need to move card_X from some view on dashboard_1 to some view of_dashboard_2.
- Result: dashboard_2 becomes SAME as dashboard_1 - only this card_X is a difference.
And a json file for this lost dashboard is overwritten with a content of another dashboard.
What I tried to do:
- Opened that json file of the overwritten dashboard.
- Pasted a content of the same file from a backup.
- Cleared a cache just in case.
- But still the dashboard is shown as a copy of another dashboard.
- Fixed only after rebooting HA.
Consider this as a quiet alarm for those who prefer to keep everything in UI & convince others.
Same here! How to fix?
After a front page update the page was working again
I tried it again and now it worked like a charm - same browser, same cache. No idea what the issue was yesterday.
That’s true, but I prefer to have an additional backup of the entire HA system just in case I can’t access the HA internal restore function. At least it seemed like that was the case yesterday. Maybe a cleared cache could have solved this. Anyway I’m happy it works now.
Thanks for your advice!
I really love the new organization tools, especially for my automations it’s really helpful.
However 
I am missing at least two ‚levels‘
A) I would like to have one more ‚top-level‘ above Floors, my installations covers three different houses, for that it would be helpful to have a ‚house‘ level.
Also I would love to incorporate the zones someway.
Maybe both can be added somehow.
Beside that I hope the integrations will pick up this organization schedule soon. Especially for the HomeKit Bridge Integration it is currently very difficult to entities to a bridge. Having some hundred entities, it’s always a time consuming scrolling to find the entity I want to add.
Furthermore, what is the rationale behind having different categories for automations, devices, entities? And would it be possible to have multiple categories for one device/entitiy/automation?
Anyway thanks to all of you for your incredible work
1 Like
Also having this issue. Any ideas on how to fix?
Beside “Add label” other sorting topics should faciliated like “Add area”. So I can mark a ton of devices and entities and assign them the respective areas, labels etc.
You have to convert to the new template style.
For the life of me I can’t get this to work (NWS has gotten rid of forecasts now, so I’m forced to upgrade my forecast methodology). Here is my attempt at an automation:
- alias: "Weather Forecast Updated Hourly"
id: 'my_unique_id'
initial_state: true
trigger:
- platform: time_pattern
minutes: /30
- platform: homeassistant
event: start
action:
- service: weather.get_forecasts
data:
type: hourly
target:
entity_id: weather.nws_weather
response_variable: hourly
weather:
- platform: template
name: "Weather Forecast Hourly"
condition_template: "{{ states('weather.nws_weather') }}"
temperature_template: "{{ state_attr('weather.nws_weather', 'temperature') }}"
temperature_unit: "{{ state_attr('weather.nws_weather', 'temperature_unit') }}"
humidity_template: "{{ state_attr('weather.nws_weather', 'humidity') }}"
pressure_template: "{{ state_attr('weather.nws_weather', 'pressure') }}"
pressure_unit: "{{ state_attr('weather.nws_weather', 'pressure_unit') }}"
wind_bearing_template: "{{ state_attr('weather.nws_weather', 'wind_bearing') }}"
wind_speed_template: "{{ state_attr('weather.nws_weather', 'wind_speed') }}"
wind_speed_unit: "{{ state_attr('weather.nws_weather', 'wind_speed_unit') }}"
visibility_template: "{{ state_attr('weather.nws_weather', 'visibility') }}"
visibility_unit: "{{ state_attr('weather.nws_weather', 'visibility_unit') }}"
precipitation_unit: "{{ state_attr('weather.nws_weather', 'precipitation_unit') }}"
forecast_hourly_template: "{{ hourly['weather.nws_weather'].forecast }}"
Don’t get worked up over what’s in the template or not there, I’m trying to get the syntax to work and then I’ll figure out where everything goes. I get the following log error:
Automation with alias 'Weather Forecast Updated Hourly' could not be validated and has been disabled: extra keys not allowed @ data['weather']. Got [{'platform': 'template', 'name': 'Weather Forecast Hourly', 'condition_template': "{{ states('weather.nws_... <snip>
I was using this for reference: Template Weather Provider - Home Assistant. Running 2024.4.1.
Same here: so the question is, what parameters are missing (baudrate as an example is only necessary for a serial communication)?
I couldn‘t find any information what was changed between version 2024.3.3 and 2024.4.1 regarding the Modbus integration. After downgrading to 2024.3.3 everything is working again.
you should take out the weather part there, as it is now, it is written to be part of the automation, and that is not an option, as is written in the error.
you want that to be on its own (so at the same level in the config as automation: )
btw, why the initial_state?
You’re mashing together an automation and a template entity. You have to choose one or the other, you can’t mix and match yaml.
What do you want? An automation with the information in a notification or a template entity to put on your dashboard?
Well, I started with the trigger-based template sensor linked by Taras but I got that same error. So I tried modifying it based on the quick blurb in your post to which I replied.
So I thought these were automations that created/updated a sensor but I obviously don’t have the syntax down correctly. Ideally I want the sensor instead of the weather entity but I get the same error in either case. I’m going to keep spending time on it, I usually get these things, but I’m certainly missing something from the examples I’ve seen linked.
From your reply, it appears I don’t want an automation but I create a sensor with the trigger? (I haven’t used one of these as of yet, thus my confusion). That makes sense, I saw the triggers and assumed it was an automation.
And as to Mariusthvdb question, I was (apparently incorrectly) creating an automation and it’s my default to include the initial_state in case I want to disable it by default for some reason. Yes, I know I can flip a switch in the UI, old habits die hard.
Yeah, this stuff goes in the template section of your configuration.yaml. There’s an example in the documentation to make a sensor from a weather get_forecasts call.