Can you show me a way to do else-if in HA with embedding another entire if-then-else statement?
Maybe I’m just ignorant about it should be done in the HA UI. It works, but it’s odd and messy. I can’t imagine they are very happy with what they have right now either.
I’m not understanding your view on this. You can cut, paste, delete, move, and create very easily in RM.
She’s not the prettiest, but she sure can dance! 
Add a condition instead in the "else" portion of the first if/then.
No, but every system has its own way to do things. You can use a choose condition who is a perfect if - else-if way. HE developers told me that automations are not programming, so why stick to this thinking ?
Here is an example of a choose condition. You can add as many choose conditions that you need and why not embedding it in an if-else automation 
Edit : Just for the coding guys (and it is not so complicated) here is the YAML code generated by the visual editor that you can also edit directly in the interface :
Yes you can. The way RM does feature this is weird. Many times when editing an if condition I was not able to edit it and ended up with a *** xx *** error in my rule. It is absolutely not intuitive and the way to do it by selecting a menu in a pop-up that switches to another series of pop-up menus, then validating your changes to come back to the first series of pop-up menus, to validate again ... In HA this is a simple and visual process, just clicking on toggles and seeing clearly where you are in the hierarchy and what exactly you change.
As a very casual observer of this conversation, which I think is a good one... It is interesting to explore peoples experiences with other home automation platforms like HA, Homey, Smartthings, etc... To me, it feels like once we get into the "nitty-gritty" of what each platform can or can't offer to the point of logic options in the rules engine, plus other finer details, I think it does lend itself to both HA and HE being viable options for different users. Not to say one is better than the other, (well I think we know which one is better ), or that all users should adopt both HA and HE, just that each have enough small, but potentially meaningful features that some users will find benefit them more than what is available in the other platform. So, a reasonable number of users could benefit from having both platforms available to use.
Basically.... It depends.... Or maybe that should be It deepens....
I agree. To be clear, I do actually not know what I will do, and it will take probably some month before I will know it. HE is actually the best system I've ever used for production. Due to holidays, I did not have much time to go further in my testing for HA. Some things are sure for me, HA has a lot more integrations and the UI is more appealing and modern, but HE has a better integration of variables. HA sometimes needs to go to YAML to do special things, but in HE you have also to handle CSS or even Groovy. Nearly all my tests are done with devices connected over HE. I will buy some devices and try them with a direct connection to HA, to see how well or bad it performs with Zigbee and Z-Wave. I will soon get a Bluetooth router to test Tread and Matter. Only after a lot of testing, I will decide what to do finally.
Another point is that my C-7 begins to get slow with all my integrations and rules, and HA can easily be migrated to one of my mini PC with an Intel N100 processor and 16 GB of RAM to have endless power.
If one would build a system that is rock solid like HE, has good radios like HE, has the mass of integrations of HA, the nice dashboards of HA, the platform independency of HA and the nice user interface of Home Pro, mainly for rules (like node red in an Apple fashion) , I would buy it, even for 1000 bucks.
Sounds like you already have it....
Nope, I have 80% of it by using 2 systems. Node Red in HA is not really equivalent to the interface of Homey Pro. So I have 40% + 40% + 0%
Sounds like the 80/20 rule also applies here.... 
It'll be interesting to see if zwave js gets Zwave LR support and/or other zwave improvements faster now that SiLabs is working with HA/nabu casa. Even though SiLabs doesn't "own" zwave, they clearly have the most dev experience in it.
Hubitat's "z" radio advantage may disappear. 
Same could happen with Matter as well. Not crazy to think that long term HA may stop using the bootleg google Matter backend and switch to using SiLab's, since they offer one as well.
It feels like, from this and other conversations, there are likely enough people who prefer the HE way of thinking when it comes to automation and defining rules, but that doesn't meant it is the right UI.
Personally I'm in the camp that a complete UI re-write should / will eventually happen in HE. We can sit here and defend it til the cows come home, but we'll be the only one's using it if that's the case. Eventually, to expand the user-base, there will need to be a fundamental shift.
If that happens, and I hope it does, that will hopefully open up a chance to step beyond the competition and pave a different path, whatever that may be.
Looks like a press release for a support contract . I'd hope that Silicon Labs would offer a direct line to all the major controller makers, including Hubitat.
Nope. It is more than that.
They don't. There are definitely resources that zwave alliance members have access to of course, and various SiLabs techs participate in that, but there is no magic direct life-line to SiLabs devs, per se, now that SiLabs isn't the full owner of zwave alliance.
But whatever, who knows what (if anything) will come out of that deal/contract/support. Might take years to see anyway.
Not sure how you get more from this, but maybe:
=$$
But many, many other people would not.
I think if this thread has demonstrated anything, it’s that preferences and opinions can vary widely among home automation hub users.
Because I have other resources closer to the deal I have directly talked to. No one said my comment was based on the press release alone - that was your assumption.
Absolutely correct as there is zero other information on the internet and I don't have any reason to know that you would have inside information.
I would call it quality tangential information more than inside - none of it came from the people directly on the team working together.
Honestly it is too early in the relationship to know exactly how it will go. There are thoughts and hopes on both sides, but it is too early to know if those will bear fruit.
Thus my speculation.
EDIT: And zwave js is a whole 'nother topic altogether. My opinion - as long as the core is primarily coded by 1 person (maybe could argue 2) , it is going to have a hard time adding features and surviving long term - open source or not. OSS only works if people contribute their time and skills, and not enough of that is happening on that project in my opinion.
Example - Al is on parental leave again (which is great), but that means basically zero development and coding for 3+ months...
Download the Hubitat app
