I really wish that what we got instead of "Hey, your device can connect to smart-things.com and do stuff, ain't that need!" we had "Hey, this device speaks Protocol 1.2.3 over bluetooth which you can import to smart-things.com or other services".

There really is no reason why a phone couldn't, for example, have a home management app on it that manages all the IOT devices over bluetooth or other protocols directly rather than needing an internet connection.

>I really wish that what we got instead of "Hey, your device can connect to smart-things.com and do stuff, ain't that need!" we had "Hey, this device speaks Protocol 1.2.3 over bluetooth which you can import to smart-things.com or other services".

I made a conscious decision to build out absolutely everything HA-related that I could using Zigbee and Z-Wave devices. I intentionally avoided anything based on wifi and proprietary apps. It's basically what you're describing. I switched from SmartThings to Home Assistant about a year ago, and everything flipped over without any real drama.

As others have said, Matter is another step in this direction with the end goal of making setup a little bit easier; it's still incredibly immature at the moment, though. But Z-Wave and Zigbee are both here now and work fine.

Same here, when I was getting started I bought some wifi light bulbs, realized they expected you to have them connected to the internet and immediately returned them, instead getting zigbee ones. Has been working for years with zero issues, was great when Philips started going cloud focused for their Hue bulbs since I didn't have to worry about it affecting me.

I bought a bunch of zigbee light switches years ago. A couple of them have failed and I replaced them with dumb switches. For my use case I found I was rarely using them as anything other than dumb switches anyway.

I'm currently doing home assistant + zigbee/zwave as well for everything. The main issue I have is it seems like the amount of those devices being released is fairly limited. It can be hard to find devices for some applications (like high current switches, for example).

Be that as it may, the issue is also that you can't take your phone and hook up directly to these devices which is the bigger issue for wider adoption, IMO. It's fine for someone like me that has a home server laying around where I can plop in HA. But what about the average consumer who's only device is probably their phone and maybe a smart speaker?

That's more the problem I was talking about that needs addressing.

The iPhone 15 pro has a Thread radio, so we may start to see it become more common.

Yeah, that's specifically what Matter+Thread are intended to address. The intention is that most devices that aren't battery powered and have an internet connection can act as a Thread border router and build out a mesh from there. The controller can be practically anything from that point.

Neither Matter nor Thread nor Matter+Thread requires an Internet connection in order to chooch.

(And that's kind of the entire point.)

This exists, it’s “Matter”, and it’s a smart home local-first IP based protocol. It’s available through the SmartThings, AppleHomeKit, and GoogleHome apps, as well as other smaller companies (eg. Alexa).

It can operate over WiFi/Ethernet, as well as thread and Bluetooth.

Edit: the implementation is also open source, and you can roll your own

> There really is no reason why a phone couldn't, for example, have a home management app on it that manages all the IOT devices over bluetooth or other protocols directly rather than needing an internet connection.

>> This exists, it’s “Matter”

Sadly, I am not sure Matter will solve the problem. Not because it cannot solve it, but because what I see in the industry manufacturers will not solve it.

I have tried several (e.g., Aqara, Google, GE) Matter products that supposed to "just work", but they did not. Every one of the devices I tried failed or made it extremely onerous to function with non-native hubs.

At 3.5% profit margin for the hardware, there is little incentive to truly interoperate. The money is in subscriptions, locking the user into an ecosystem that makes them dependent for the life of the product.

(Caveat emptor - I am an old crotchety, jaded grouch.)

Does pairing (or network joining or whatever it's called) work in Matter? Or is this going to be like Bluetooth where 30 years later the most fundamental underlying workflow still finds new and innovative ways to be completely broken for the most basic tasks?

Pairing mostly works. Matter is still "new", despite having been in the cooker for a few years, and there are glitches to the setup process, but it works eventually.

I've got a few cheap Matter light bulbs that I've picked up mostly just to play with, starting a few months ago.

This fleet has several random and forgettable names on the packaging and exactly two (also unmemorable) manufacturers so far.

Pairing is a little weird: It seems to broadly involve a pocket supercomputer with Alexa or Google Home or Home Assistant or whatever, and scanning a QR code.

This QR apparently begins Bluetooth handshake between the light bulb and the pocket computer, wherein things like WiFi information seem to be exchanged.

After that, Matter devices (in my application at least) just live on WiFi.

This all happens without needing weird(er) apps, overseas clown accounts, or manufacturer-specific hardware. It is local. (Well, Home Assistant is local. The others...are whatever hybrids they are.)

And multiple local control systems (like the three I've already mentioned) can each monitor and control each Matter devices directly. There's probably a limit, but it's nice to have these things non-interactively interacting. ;)

And they seem to be working fine. Boring, even. Right now I just have all of my IoT stuff on the same VLAN/SSID as everything else because it is easy, but I have 100% confidence that these Matter devices would continue to boringly Just Work if I were to isolate them to their own VLAN with zero WAN access.

(Maybe that's something I will work on when setting everything up again after the next move.)

Cool, that sounds promising, I'll have to play around with it some time!

Iirc, Matter uses BT LE for adding devices; not sure if that's required or just a supported option, though.

Yay?

> I really wish that what we got instead of "Hey, your device can connect to smart-things.com and do stuff, ain't that need!" we had "Hey, this device speaks Protocol 1.2.3 over bluetooth which you can import to smart-things.com or other services".

The problem is that end users suuuuuuuck.

Oh, by the way iOS and Android do everything in the universe to make using Bluetooth absolutely miserable. Which Android or iOS version are you running? Which buggy Bluetooth stack did Samsung saddle you with? Oh, we retired that version of the app 18 months ago, please, for the love of God, update it. And, oh, you're using a shitty cracked Chinese version of the app <facepalm>.

If I make the users connect to the "cloud", I can control the device, the backend talking to the device, and the front end talking to the user. I now know exactly what the versions are, and the Chinese can't pirate the app. The customer support is orders of magnitude easier.

From the perspective of the device developer, the "cloud" is simply a no-brainer on every single front.

You, as a local-only user, simply won't pay anywhere near enough money to make supporting you worthwhile.

If you want to cloud delete you may be able to install valetudo on your roborock. You still get a local control via webpage or the (foss) app.

https://valetudo.cloud/pages/general/supported-robots.html

Valetudo has been awesome on my Roborock S5s. It does occasionally hang up so I have some reboot cludge scripts, but in general its pretty solid. And way more than you can ask for from some random guy on the internet.

On my dreame t is rock solid. Better than any OEM IOT software by a long shot.

Agreed - can't tell you how many cloud connected devices I've had that completely stopped working. Like my Mellow Sous Vide. Most of my house now is Z-wave and Zigbee.

I just bought a bunch of Shelly wall switches and US outlets. They are very affordable and use an open source OS on what I think is an ESP32 enabling Bluetooth and WiFi. They have an IoT cloud thing paired with their app BUT you can disable their cloud or use your own cloud URL, enable RPC over http or UDP and write your own code, use MQTT, local web server in the switch, etc. The outlets are just relays though they measure load current and voltage. Bonus is they do not need to be commissioned through an app - you can do everything over a browser or http calls via curl so you can use whatever OS and even script it.

My only gripe is the wall switches do not have any ability to accommodate retrofitting a 3/4-way setup which is quite common for stairwell and hallway lighting.

Edit: here's the dimmer API for reference https://shelly-api-docs.shelly.cloud/gen2/Devices/Gen2/Shell...

Just look at the ones that support Tasmota (or ESPhome).

Those use opensource software, integrate nicely into home assistant, and well.. are "local first".

For lights and relays (haven't bought the others yet) i;ve been really hapoy with the quality of athom devices. Tasmota, esphome and wled support natively.

Thanks, didn't know them but their products seem real good. I'll have to try them.

Wifi iot can be good, but it depends on a few factors

Devices with local API, be it binary or http, are one part of the equation. There are systems like esphome that are best in class.

The other part is getting a decent router and Wi-Fi infrastructure to support them. Most consumer routers crap their pants after 30 or so devices

I used to be vehemently against Wi-Fi. Internet of things stuff, but when I got my new house, my current house I've been building it out in a hybrid approach. Approach. Lighting loads are controlled via lutron, and then non-lighting loads are a mixture of Z-Wave, zigbee, and Wi-Fi devices running ESPhome. My Network infrastructure is a unifi system. It's been more or less bulletproof

Good for you!

I depend on nothing in the cloud and I only have encrypted backups in the cloud secondary to local back ups. I even download my email in Thunderbird.

Apple is criminal when it comes to cloud dependence. An iPhone is mostly useless without an iCloud account. With GrapheneOS and Android there is no dependence on the cloud. I am just pissed that the android phone makers keep getting rid of SD card expansion.

I will never own an IoT device though. I never saw the convenience of them over the hassle and cost.

WiFi is terrible for IoT anyway. Look into other procotols such as Zigbee, they don't connect to the internet, ever.