Got it. FWIW, I’m using a Silicon Labs UZB-7 USB Stick (Silabs SLUSB7000A / SLUSB001A).
I updated to zwavejs v10 in anticipation of updating HA and my Zooz Door sensor ZSE41 stopped reporting the open/closed state. It never went unavailable but it just never changed states.
I downgraded back to v9 and it’s working again.
But my Zooz motion sensor worked with no issues on either version.
Thanks for your reply. I had the same issue, my ESPHome addon was old and did not exist in the addon-store. Uninstall en ReInstall the latest fixed that.
Probably the person meant “checkboxes” to disable/enable automations.
Before:
Now:
To disable/enable - a user must go to menu:
YES - I find this change not convenient.
I myself to not enable/disable automations very often. But for test automations this is a usual scenario for me. And sometimes I just do not want to create a dedicated card to specially enable/disable automations.
5 Likes
4 Likes
Oh, then yes, I agree.
This trend toward hiding everything useful deep in the bowels of clicks is getting kind of tedious.
7 Likes
It as though whoever is designing this is doing so on a 5 inch phone screen 
3 Likes
It was slider to enable or disable automations now I have to press the dots and I then I have enable and disable automations. I use to change them while waking up in the middle of night any of the heating ones. This two click process… whose idea was this ?
5 Likes
Frankly you shouldn’t need to do this. Automate it.
1 Like
Ok, the scenario is ducted heat works with outside temperature. So the automation is set to change temperature settings every hour. However, when it rains or temperature changes are more abrupt then say 18 is still hot and then I have set it to manual temp at that time that also means I need to skip the next couple of next few automatic adjustment for the day.
As a good developer, I have always considered all scenarios. It when developer believe everyone will be like that and that is not the case.
I’ll find a solution to undo this but dislike to this change remains
The problem is your browser. Try changing the size of the window.
Exactly what I mean.
Similar to what Android 12 on Pixel ( a so called improvement)-- a two click process to select internet option of wifi or mobile data
1 Like
Hello, I just updated to 9.3 and when I click on system I now get a blank page. I went back to 9.2 and all is fine. I tried to update again to 9.3 and same issue. Any ideas?
3 Likes
Same with my system as well when I updated to 9.3, (Raspberry Pi 4).
Good to know others are seeing it as well, and it isn’t just me/my system.
1 Like
Same issue here after updating Core to 2022.9.3 - System page is NOT showing
2 Likes
Have you cleared your browser cache?
Same here, and yes cleared cache and different browsers. Container version 2022.9.3 on unraid. System menu is empty. rolled back to 2022.9.2 and it’s back
Same here
Please fix
Phil
There was a new frontend release with 2022.9.3. You should still be able to get to the info page and read the version number here 
I can confirm the issue on a x86_64 based mini pc with the latest frontend: Settings → System shows a blank page.
2 Likes