Should 433Mhz be in the next gen Hubitat Hub?

Somewhat of click bait, but I think honestly I would totally pay for an upgrade from my current HE if you guys released a version that supported 433Mhz and 315Mhz for existing sensors and switches.

There isn't an option on the market that makes it "easy" to bring in those types of transmitters like alarm sensors etc into Hubitat.

Anyone else think this would be a cool idea?

Most of those use proprietary protocols.

3 Likes

Which exactly existing sensors and switches are you referring to?

1 Like

I think he means Honeywell alarm system sensors and similar devices

1 Like

I suspect there would be limited interest. However the rtl433 project seems to be able to do this if you're technically inclined. IMO BT support would be more useful.

1 Like

I'd rather see bluetooth supported first. There are so many devices that need a raspberry pi bridge or something.

4 Likes

BLE makes for an extremely poor home automation wireless protocol, hard pass.

From what I can tell, from the outside, Hubitat is focusing on the future which is "Z-Wave Long Range" hub and spoke networks. No more dependency on lots of repeaters to build a healthy mesh, most devices can home run to the hub.

2 Likes

Forgive my ignorance if some of my assumptions are off, but at least BLE is a protocol right? 433 MHz is a frequency, and as @dman2306 pointed out, there could be several kinds of device protocols on that frequency, with a tendency towards proprietary implementations.

2 Likes

Yes you are correct that BLE is a protocol and 433MHz is a frequency. However what I think you are missing is the fact that only some frequencies are "shared spectrum" and some are "licensed spectrum". For example BLE shares the exact same shared spectrum as your home 2.4GHz Wi-Fi router, which is yet another reason not run both BLE and 2.4 Wi-FI protocols in the same household as they can step on each other.

433MHz is like the 908MHz that Z-Wave uses, it's proprietary and is either lightly licensed or fully licensed spectrum which only certain licensed vendors can operate protocols over.

I have zero 433Mhz devices and many BLE. So dispute the opinions on which protocol we should be using, to answer the OPs question, I don’t care about 433Mhz support at all. However I would benefit from BLE. The reality is, regardless of opinions, there are many devices available that are BLE only.

3 Likes

The king has spoken!

I don't think either the Bluetooth or 433Mhz is a bad idea, but I don't think many people would want to pay for them to be built in. And I don't know how often they would be used compared to Zigbee and Zwave.

Maybe like the new Wifi feature where you buy your own antenna, they could add support for a Bluetooth receiver, and you just have to plug one in IF you want it. The 433Mhz probably will be tougher, I don't know of any dongles for that like there is for Wifi and Bluetooth.

3 Likes

I'd certainly like both BT and RF but especially RF as I have some multi gang extention leads and also a blind that uses this.

1 Like

I agree that 433mhz is less than ideal, and not an implementation that should be promoted over the likes of protocol based mesh networks. That said, there is and will continue to be many devices in the home that are "proprietary" with a level of complexity to reverse engineer using training algorithms that ranges from easy to impossible. If the overwhelming majority of those devices are of the former, than the idea is to have a bridge to bring those devices into your home automation.

That bridge could be a separate accessory, or built into the hub, The idea of it being in the hub was to make it easier and native vs. requiring 6mo of experience and coding skills to realize them into your home automation system.

Maybe the Bond bridge does this already. I just thought this being a feature that standardizes hardware, and opens up the device support and library to a community level vs. uber niche module.

I believe 433MHz devices are far more prevalent in Europe compared to North America. That might explain the lack of excitement on this side of the pond. :wink:

4 Likes

My own view is its better to do a few things really well, than to try and do a lot of things sort-of well. There are still gaps in the Z-wave implementation (many control classes are several versions behind) and I understand Zigbee is still not Version 3 (though I'm less certain about that). Seems to me the priority needs to be getting these fundamentals 100%, then consider what's next (and, it seems, it looks like the smarthome industry may be heading to 'thread' as the unifying protocol, which I understand is based on the Zibgee physical layer, so that seems a more natural direction anyway for a going-forward product).

For 433Mhz - could you use RFXCOM theLAN interface version ? Has loads of protocols supported in the device.

With a suitable driver for HE

http://www.rfxcom.com/epages/78165469.sf/en_GB/?ViewObjectPath=%2FShops%2F78165469

You know about this, right? SONOFF 433 RF Bridge Convert 433MHz RF Remotes into WiFi wireless

It's like 30€.

Or you could just use a Broadlink RM Pro. Works very well with HE. Would still be nice to have it built in though.

2 Likes

Maybe Bluetooth Mesh is going to be a thing someday, but I’ve had this Gateway since May of 2020 and there’s only a handful of Bluetooth devices compatible with it, and the only repeaters are 220v bulbs I cannot use in North America for normal house lighting if I wanted to.

And the devices that they’ve added that are functionally the same as Zigbee are the same price, or more expensive, and do not communicate as far. Plus they require a new repeater which I will only be able to use for that small number of devices, and as I already pointed out, are not available to me.

You guys do realize that Bluetooth solves nothing where compatibility is concerned right? Tons of BLE devices on the market that cannot be used with everything is what we have. The gaps are as wide as ever, they’re just on another protocol now.