kigmatzomatB
This is a Matter device, right? Well, Matter doesn’t support power monitoring. Just like Matter lights don’t support dynamic events.
One theory is that Google and/or Amazon weren’t prepared to support power monitoring based events or dynamic lighting so they voted it down. Another theory is that endpoint device manufacturers intentionally removed a key feature from the spec to ensure you would still need their app/cloud so they could have vendor lock-in/data harvesting/etc. Third theory is “Why not both?”
Despite Matter having been hobbled, it is still the best IoT mass-market solution as when Meross inevitably obsoletes these devices, they will still be locally controllable. (Some would argue an MQTT based solution is better but as there’s no 3rd party validation, you can get insecure products like the Nexx garage door opener)
I , however, detest IoT and stick with zwave devices, which have no innate ability to be on the internet, can’t get firmware “downgrades” or be hobbled by a cloud outage and all get 3rd party validation.
It is highly unlikely you will get such a device in less than 3 years for the simple reason that it has a constant power supply greater than 2 watts. In that scenario, it should either be wifi for the range or act as a wifi/thread bridge (aka border router) to augment the thread mesh without the homeowner needing to worry about their existing mesh*. In either case, control would happen over wifi.
The CSA (Matter management group) needs to increase the number of wifi/thread bridges on the market to make battery-powered Thread-only devices viable. This is a greater priority than having mains-powered Matter devices that can only act as thread relays.
*Thread relays have the same issue as zwave/zigbee relays: you have to daisy chain them across your home to extend the mesh contiguously. This means some people need to put relays in places they don’t need any functionality other than to be a range extender. With wifi/thread bridges you can use wifi’s orders of magnitude greater power budget to extend the Thread network in a non-contiguous fashion.
As an fyi, wired sensors are pretty much universal. You could swap the panel out with a newer one that supports ethernet via an Envisalink board. Then you can integrate it with 2-way control to a homeseer/hass/etc. The Elk m1 and DSC Power16 would be upgrades.
I don’t use IoT, I use zwave so power budgets are small. Wireless sensors get a cr123 battery that lasts a year or more.
PoE is an option for things like shades/blinds. Alternately you can get those AV-style recessed wall boxes that have 110 outlets that you put a cover over, though you need to plan for a large enough valence to conceal it or some architectural detail.
Use a non-ip based automation tech. ZWave, zigbee, insteon, knx and RadioRa2 are popular choices.
Pick a controller that doesn’t need the cloud. Hubitat, HomeSeer, ISY994 and HomeAssistant are likewise popular. These controllers at most need internet access for initial set up and software updates.
You can lock them down completely or open specific ports for emails, remote access, etc.
Read the wiki. Its full of terms and info you can use as jump off points.
Did Matter 1.2 address the gaps in 1.1 or 1.0? Is there power monitoring on smart plugs? Lighting scenes? Light sensors?
Did CSA take advantage of wifi bandwidth and support cameras and/or video doorbells?
No?
Didn’t think so.
Oh, support for robovacs.
And there was an article about jailbreaking vacuums.
https://www.theverge.com/23934731/valetudo-robot-vacuum-hacking
Interesting.
What the other poster listed will work but its not legit in all jurisdiction. There’s no alarms before the door closes, which is a no-no for remote operated doors many places. (Possibly inculding your insurance policy)
GoControl makes a zwave garage door controller with flashing light and audible alarm. Its not cheap, usually running $70-100.
accessory switches, at least in th4 Jasco world, muat be paired to a primary zwave switch in a 3 or 4 way configuration. it uses low voltage signaling over the traveler rather than carrying the full load.
the panel will only know about the primary as it controls the circuit.
there are hubs/bridges and then there are controllers.
Every smart device requires a controller because the truth is, none of them are smart. At most you get a timer, which, let’s be honest, was available back in the 60s. It’s the controller that does IF/THEN logic, tying multiple devices together
Hubs/Bridges let two different technologies talk to each other. Your router is a wifi hub/ethernet bridge you already bought. So you don’t need any bridges to connect Kasa devices. At least as long as your router can handle the number of devices. Many consumer routers are only given enough CPU/RAM to handle maybe two dozen devices.
So the question you need to ask yourself about Kasa is where is the controller? Who owns that? Who can turn it off? What happens if they do? For most Wifi devices the answer is “in the cloud, owned by the manufacturer, who can turn it off whenever they want and there’s a good chance your switches become dumb switches”.
Zigbee/ZWave needs a bridge, which is often a USB stick on a PC that acts as a controller or is integrated into a dedicated controller. Every $40 zwave radio is good for 232 devices. Zigbee devices vary but the vast majority are good for 100+ and even the most under-specced Hue hub is good for 50 zigbee bulbs.
I use HomeSeer running on a mini PC with a zwave usb radio to control my 80+ devices. if Homeseer goes under, I lose remote control until I set up a VPN server. But all my devices will still follow all their programming, I can add new devices, new rules, and let it continue to run for years if I choose.