I don’t think this has automatically changed. I think we need to do this manually…it would help to have some guidance on ‘how’ 
The urls still have the lovelace string in the url. I don’t believe you need to change anything.
Add this to your configuration.yaml:
logger:
default: warning
logs:
homeassistant.components.recorder.migration: debug # or 'info' if you prefer less logs
4 Likes
Of course I don’t “need” to change anything to keep my HA working, but if a change in this release is that “Lovelace” is now replaced by “Dashboard”, I’d like to embrace that change by no longer seeing “Lovelace” in the URLs.
I note my Config → Dashboards still directs to http://homeassistant.local:8123/config/lovelace/dashboards rather than e.g. /config/dashboard/dashboards after the upgrade. Is this planned to change?
He already put a note in the readme, I just figured people reading the release notes would want to know.
1 Like
No need, there’s a big Heads-up warning users.
Hoping to figure it out, but it’s going to need some dev assistance.
And they’re very busy!
So yeah, need all the help I can get, if you know of a way to adjust the new web socket handling in custom-ui, do’nt hold back.
I have linked all the PR’s that cause this, and Paulus’s explanation in the Release party
2 Likes
It’s a bug which will be solved with next patch release (2022.4.1)
I think something is wrong with your install or you have a custom component or something. calculate_offset is no longer in the code base anywhere. Maybe try to update again?
I am using trigger.event.data in a number of templates in automations, all of which are now broken.
This is the error in the automation trace:
Error: Error rendering data template: UndefinedError: 'dict object' has no attribute 'event'
The documentation does not mention any change either.
Would this have any effect or allow for emulated_hue to emulate a v2 hub?
wondering if this is per design, or if we have an issue:
shouldn’t they be ‘off’?
I did notice this: Forced update failed Entity.xxxx. not found. · Issue #69492 · home-assistant/core · GitHub which also seems a bit surprising, maybe related?
please see if you recognize this?
other instance: yes they should be ‘off’
ok, now what 
Ill add to the issue.
Do you also have zha issues with conbee on 2022.4.0 and will it also be fixed in 2022.4.1
1 Like
No issue here with ZHA and my conbee 2.
Do you run HAOS? I do and I have no issue at all
1 Like
Im running debian/supervised and with the update 2022.4.0 im having a lot of issues with my zha zigbee network and conbee2. I moved back to 2022.3.8 there i zha works fine
why the actual value is not changed rather then just adding another db entry to make the global statistic tally correct
It does change the actual value though, so something did not work as expected.
Can you open an issue and tag it with the recorder integration please?
I see that the utility meter, groups, etc. has not been migrated to the UI automatically. This will be done in future updates or do we need to do it “manually”?
You may need to update ZHA dependencies or SQLite manually. Check this issue: ZHA & Home Assistant Version 2022.3.1 no longer works · Issue #67780 · home-assistant/core · GitHub
1 Like
Guys my ıp cameras stop working with this update, what is going on?
type: picture-elements
title: Garden PTZ Cam 01
camera_image: camera.ptzcam1
elements:
- type: state-icon
tap_action:
action: call-service
service: ptz_camera.move_left
service_data:
host: 192.168.1.18
entity: camera.ptzcam1
icon: mdi:arrow-left-drop-circle
style:
bottom: 45%
left: 5%
color: white
opacity: 0.5
transform: ' scale (1.5, 1.5) '
- type: state-icon
tap_action:
action: call-service
service: ptz_camera.move_right
service_data:
host: 192.168.1.18
entity: camera.ptzcam1
icon: mdi:arrow-right-drop-circle
style:
bottom: 45%
right: 5%
color: white
opacity: 0.5
transform: ' scale (1.5, 1.5) '
- type: state-icon
tap_action:
action: call-service
service: ptz_camera.move_up
service_data:
host: 192.168.1.18
entity: camera.ptzcam1
icon: mdi:arrow-up-drop-circle
style:
top: 10%
left: 46%
color: white
opacity: 0.5
transform: ' scale (1.5, 1.5) '
- type: state-icon
tap_action:
action: call-service
service: ptz_camera.move_down
service_data:
host: 192.168.1.18
entity: camera.ptzcam1
icon: mdi:arrow-down-drop-circle
style:
bottom: 10%
left: 46%
color: white
opacity: 0.5
transform: ' scale (1.5, 1.5) '
- type: state-icon
tap_action:
action: more-info
entity: camera.ptzcam1
icon: mdi:arrow-expand-all
style:
top: 5%
right: 5%
color: white
opacity: 0.5
transform: ' scale (1.5, 1.5) '
camera_view: live
- platform: generic
name: ptzcam1
stream_source: rtsp://admin:@192.168.1.18:554
still_image_url: rtsp://admin:@192.168.1.18:554
rtsp_transport: udp
authentication: digest
username: admin
verify_ssl: False
Hi I see this when I do a test with “Check Home Assistant configuration”
[08:40:27] ERROR: The configuration check did not pass!
[08:40:27] ERROR: See the output below for more details.
Testing configuration at /tmp/config**
INFO:homeassistant.helpers.storage:Migrating core.entity_registry storage from 1.5 to 1.6
Failed config
General Errors:
Integration error: zwave - Integration “zwave” not found.
Successful config (partial)
Any suggestions?
try setup through UI, generic camera from intergrations.
1 Like