Home Assistant has not native support for dishwasher, washer machine or oven, it use a lot selects, number and sensors, or, in the best case, use a climate for oven.
That is not user friendly.
We need some new platforms where set program, select some options and start it.
There are dozens of different brands of appliances, and none are using a uniform API, if they even expose their API to the users.
Yes, the appliance manufacturers are not user friendly.
Climates, lights, switch⌠All have differents brands and API , but HA unifique all them.
My purpose is a Oven type where I can set temperature, program and time, or Washing Machine where set Program and Delay Time.
I can do it now in HA but with âuglyâ controls, I want a specific platforms and views.
What you are looking for is a platform. Not an âentity typeâ. Platforms are generally written with an integration.
There are platforms for lights and switches, but they were developed along with the light integration and the switch integration. If there is an integration for your appliance, there could be a platform for it. If itâs just the appearance you donât like, there are dozens of custom cards on HACS that are highly configurable.
I havenât ever seen an oven with network connectivity- who makes such an appliance? My Washer and Dryer are LG, and there is an integration for them.
Home Assistant is open source. You could always learn Python and write an integration and platform.
Platforms, correct, I edit the the post.
My oven has connection, it can be integrated in Home Assistant and it is showed as âclimateâ, I can set temperature and Program as âpresetâ, yes, it works, but It is not correctly because a oven is not a climateâŚ
My Dishwasher and Washer have connection too. I have a lot of selects, inputs, sensors⌠I need set each one before press start button.
And I sure that you washer config is different of my washer config, because each integration developer do it different because there not a specific platform for this.
PD: I did a few components and I helped to oven integration in hOn
Doesnât matter what phrase you use, we understand.
Oddly enough, I had a conversation with the guy who does most of the alexa development for HA cloud about this the other day. We need to start a architectural discussion about this on github to get the ball rolling.
In order to get washer/dryer devices in alexa, weâd need to have matching platform/domain in HA.
What brand?
I use a climate entity for my oven, it works well.
Not OP, but for what itâs worth Iâve got a Bosch oven in the UK that is connected
Haier.
PD: I do not recommend ItâŚ
This is on the radar but in a different way.
I really want to stop introducing more types of entities (like wash machines, dryers, and the like). Instead, Iâm currently working out a concept of actual devices that allows for different sorts of devices.
Instead of making everything an entity, we could have an actual âDryerâ device, which would have a power sensor, energy sensor, on/off switch, program selector, current running state sensor, start button (and stuff like that), etc.
This will move âdeviceâ in Home Assistant from being a way to group entities, to something that gives meaning and context to entities.
Only issue with this is the interface with Alexa. The current implementation is 1 to 1 entity to exposed device in alexa
That is not an issue, it will be a solution for both Alexa and Google (who both DO work on device level, just Home Assistant doesnât yet) 
That sounds to me like the way things already work.
As an example. Home assistant does not have a pump entity, so my hot tub pumps have to use fan entities. Thatâs what the issue is. They are already under the hot tub device.
Iâm very curious on what this will look like. Is this related to this discussion: New Entity Proposal: Cooker ¡ home-assistant/architecture ¡ Discussion #501 ¡ GitHub or something else?
I always have the device in mind when I do something in Home Assistant. They are very intuitive for performing actions or to navigating to entities. When I read the forum, devices are heavily discouraged from being used in automation. Everytime Iâm tempted to use a device, I change my mind because Iâm afraid @TheFes delete my automation to save me from myself 
.
I fully understand why adding more entities is not a good way forward. I still find it weird that a binary sensor, light and lawn mower are all entities while the way they are used is very different.
Binary sensor has a ton of flavors.
Light is commonly a single entity with a ton of attributes.
Lawn mower needs extra entities (like a battery) to be fully functional.
Having some better hierarchy with fundamental/abstract entities, physical entities and devices/appliances for grouping and context could help a lot. This is just one way of looking at it and there are many, many other ways of doing things and with a lot of dept to each option.
I like how what seems to be a pretty basic question touches on deep architecture and modeling topic. I hope you can give us some insights in the current thought processes and design directions since I think itâs really fascinating. I hope you can bare all the comments and just keep doing your thing to make something awesome for all of us to enjoy.
If you never saw it, it doesnât mean it doesnât exist 
Both my oven and induction cooktop from NEFF have built in WiFi. But theyâre not the only manufacturer that produces such devices. Right now I can find 354 ovens and 231 cooktops available in Germany that have built in WiFi. Out of those, Bosch, Gaggenau, NEFF, and Siemens implement Home Connect protocol, which has Home Assistant integration.