What Should HE Staff Tell to World in LA?

[sburke781]

I'm not someone closely tied to the commercial aspects of HE, but do, like all users, benefit from the mutual success of the platform.... So....

What should we whisper in the ears of those with larger (virtual) wallets / purses than ourselves....? Personally I would be shouting the local angle, but maybe I would be influenced by local data breaches that have occurred in my area... without affecting me (thankfully).

[wayne.pirtle]

I had the privilege of going to CEDIA in Dallas and met @mike.maxwell and @bcopeland at the Hubitat booth. They are definitely pushing the local advantage of HE. I think being at these shows is helping to get the word out, especially to integrators.

[vitaliy_kh]

1. All controls must be ONLY local.
   Clouds could/should be used only for maintenance and initial setup.
   But better not to be used at all.
2. All APIs for every device/ecosystem must be published.
3. And of course, all Standards must be real, no any fassiness alowed.

[neonturbo]

@vitaliy_kh

• All controls must be ONLY local.
  Clouds could/should be used only for maintenance and initial setup.
  But better not to be used at all.
• All APIs for every device/ecosystem must be published.
• And of course, all Standards must be real, no any fassiness alowed.

• All controls must be ONLY local.
  Clouds could/should be used only for maintenance and initial setup. optional, not necessary for any function.

Edited to state my position.

Local only, period. From setup to integration to use. No more of these IOT devices that become bricks when the company stops supporting them, or goes out of business. The e-waste is terrible, and the amount of money spent for devices that prematurely are put out to pasture is disgraceful.

[miketech]

Interesting question. In my opinion, it is not that easy. I started discussing with a friend of mine, why I chose HE and he Home Assistant.

For me, HE is the perfect mixture of a list of certain points:

• Support of many devices
• Powerful rule engine that enables complex automations
• I get an API to add further functionality in my preferred language

But even though:

• Easy installation
• Runs out of the box (do not have to install it on a rasppi first)
• Alexa support of the box

Thus, HE for me is for people who have a deeper IT know how, but do not want to install and configure everything from scratch. Just a perfect mixture.

However, the downside is: This mixture is a niche. For newbies it is too complex. For hardcore IT nerds maybe they like Home Assistant more. But maybe this is the strength.

What would I tell others?

"You get a powerful smart home platform that runs out of the box".

btw: The local aspect is not that important for me. It is a nice addon.

Currently, it is a B2C product. Would you like to place HE as B2B? Then, we have to think about other advantages. Here, the combination of local automations with an API to extend it by custom functionality could be an interesting point.

Regards,

Mike

[garyjmilne]

@miketech

The local aspect is not that important for me. It is a nice addon.

I think most people are referencing security when they talk about this but for me speed and reliability are more important as those affect every single operation.

[miketech]

Ok yes, you are right. When it comes to speed and reliability this is interesting.

Mike