Hi, not that I even know what this integration is doing, but this issue is reported on github, just saw it when browsing new issues :
hydrawise binary sensors and switches not available after 2022.12 update · Issue #83540 · home-assistant/core · GitHub
Armin
(emphasis mine)
You dropped a really key part of that sentence, the “while”. The implication being that YAML will be supported while there are still things that can only be done in YAML. You should not expect the YAML to go away at least until the GUI reaches parity. Once that happens then perhaps it will become deprecated, most likely accompanied by an automatic migration unless that poses some unexpected challenge.
Why add a dropdown when you can utilize the automation engine and do whatever you want? I currently use it to schedule heating on/off. Should we add a dropdown for that as well? Where do we draw the line? Then it begs to ask the question: Why even have an automation engine if we can just add dropdowns that do small functions everywhere?
Then why even create a calendar if it has absolutley no function except hold a name and date. It is then merely a toy with no real use.
Sure, you can create whatever integration you want. but it must be allowed to ask if it will ever receive any functionality.
Basically a post-it integration with a nice UI but no Home Automation functionality what so ever.
If you need the advanced scheduling out of the GUI look at HACS Scheduler Integration and Scheduler card. It has very nice ui that would do most likely 90% of what you are asking for. Actually the new Local Calendar has some features that the HACS integration does not have e.g. to have schedule every 2nd week and so on.
I could also do it manually. I am just saying, we now have multiple integrations with similar features and non have all the basics of a modern calendar.
Look at your Android phone. You can have all infos plus a repeat function (set to days, weeks, months, years with freely definable x) and you have alarms & reminders.
That is a basic calendar nowadays.
How is that different from any other helper? Input text, input button, input select, input boolean, input number, counter, etc. All the helpers do absolutely nothing by default. In fact could go further, template integration, derivative, min/max, etc. they all do nothing by default. Their value is entirely in how you use them within automations (sending notifications, changing the state of physical devices, etc.) or how you choose to present them in the UI (dashboards, graphs, etc.)
Local calendar is essentially just a new kind of helper. It allows you to make a schedule. How you choose to use that schedule (notify someone, change lights, change thermostats, change blinds, interface with some other IOT device, etc.) is completely up to you and what you put in your automations.
I get that we’re used to notification options with calendars because pretty much all the personal calendar tools people have used have options like that. But this is really more of a schedule helper. And like all helpers, they do nothing until automations add that functionality.
I really like the Scheduler Integration and it will probably be perfect within a few iterations and I can deprecate my manual json calendar with the corresponding sensors in config. Good Job! 
Then why even bother giving it an entire dashboard? Why not just add it to helpers if it has no more use than the basic helpers?
Either it is a very simple helper or it is a full calendar integration. Right now it is the first, not the latter.
The calendar dashboard is not related to the new local calendar feature. That has been there for a while. It displays any calendars you have integrated with HA. That can be local calendar, caldav, google calendar or other custom integrations you found that make calendar entities. I’m guessing if you’ve never seen it before then local calendar was the first calendar integration you used.
But the dashboard is not specifically for local calendar. It just displays all events across all your integrated calendars.
Yes, it is the first I used because I thought that the local one would finally allow easy maintenance tracking. Unfortunately it is, as you said, nothing more than a very basic helper wrapped into the calendar dashboard (instead of the more useful helper UI).
what devices are you using?
On the Integrations Documentation page, I see some warnings - not sure, since when they were available…
The integration itself seems still be available:
Have you checked, if it is disabled?
In this case, disabled integrations will be hidden from the page itself
Where do I uninstall the local calendar? I added it as integration but it is not listed in integrations nor addons.
I must be blind because I cannot find where to remove it 
After you remove it, you might have to restart. If it doesn’t, that’s a bug. Or simply clearing your cache and refreshing the page may work as well. I’d wager a restart is needed though so that the system knows there’s no calendars.
SSH has an overhead in CPU since it encrypts everything. If you don’t need encryption (like, inside your own house, perhaps?), other filesystems may be faster. I am getting much faster transfer rates with NFS. I still use SSHFS as the default solution where security is needed, and to interact with machines I already have set up SSH access to.
Would be interesting to hear how SMB/CIFS is doing, speed-wise.
But where can I remove it? I cannot find it listed anywhere.
it’s in your integration page
With the state color changed from yellow to light blue it is difficult to see my mqtt sensors at a quick glance if its on or off. Do we have an option to set the color back to yellow without using custom mods?
Ah, did not show up until reboot and did not disappear until reboot.
