Toyota president Koji Sato also admitted that production volumes of solid-state batteries were likely to be small when the company rolls them out in electric vehicles as early as 2027. “I think the most important thing at the moment is to put out [the solid-state batteries] into the world and we will consider expansion in volume from there,” he said.
SOOOOO not really close.. another press release hyping this up. How small is SMALL? Hundreds?
They clearly are still having trouble scaling production of this technology. It has EXISTED for some time but isn't of use to cars if they can't make hundreds of thousands of them.
Zwave via Z-Wave JS: https://devices.zwave-js.io/ ( I will note that even if a Z-wave device is not on the official known supported list most will work if they are basic devices like a switch)
If you have no plans on recording you may want to look up setting up a stand alone instance of go2rtc and one of the optional cards to support WebRTC and MSE near real time viewing vs home assistants default HLS which is sometimes 15seconds delayed and chunky.
If you are not going to view ALL of the streams at the same time the system requirements and overhead for go2rtc should be fairly low depending on the codecs of your cameras and the devices you want to view on as video and audio support on various devices is all over the map, but go2rtc can transcode on the fly.
Nearly all Zigbee and Z-wave devices JUST WORK or are very close as long as you just double check they are on the compatibility lists. They are also fully local, mature and have devices from switch / hardware makers that are reputable in making switches and outlets. (unlike most wifi devices)
I would also suggest matter devices but that is still beta in home assistant and too EARLY to say anything about the quality of devices that support the limited 1.0, 1.1 specs.
As has been pointed out MANY times on the current CAST items if you have an accident large enough to go through the replaceable parts the crash bars and it DOES damage the cast it is a write off anyway.
Matter supporting devices are still VERY few and far between (some vendors have back tracked from supporting it)
I am not even considering matter an important feature until HA is out of beta for it, it cant even act as a matter bridge yet. This is particularly important if you want HA to be the master of everything and you want to use matter with other systems directly.
For now my setup is all self run docker.. I run the main HA container, zigbee2mqtt for zigbee support, and zwave-js in a docker for zwave support.
By far zwave has the most mature lock / security / control devices
By far zigbee has the MOST / cheapest sensors and other devices (Aqara in particular for sensors)
I would love to consolidate but I am in a complete rebuild of my setup and from the look of it most of my door locks will be going zwave and nearly all my sensors will be Aqara zigbee.
As for which way to go with zibee, I started with ZHA then switched to zigbee2mqtt for a few reasons
zigbee2mqtt has slightly better device support, seems to get device support a litter faster for new strange devices and has a great online database of supported devices.
zha restarts with HA, this includes restarting the zigbee dongle AND NETWORK.. every time to do a full restart of HA you may cause all your zigbee devices to become unavailable till the network comes back up, particularly sensors. Running zigbee2mqtt as a separate docker it only ever gets restarted when I reload it for updates, the network is always VAST and up. When I restart HA the only wait is for HA to connect to MQTT and bang all the devices are back with the correct states
Feedback.. zha has a better UI integration IN HA, however I found using the native zigbee2mqtt webUI it had more real-time feedback for actions such as inclusion, or advanced stuff like binding devices together which requires some odd timing of you pressing device buttons.
zigbee2mqtt was very tunable, from setting up the keys / channels to how often it polls to find out if battery devices have gone missing.
Did a complete furnace and ac install about 2 years ago. Couldn’t find anyone who would sell me a heat pump, constantly given the high cost emergency heat speech even with that place being in the very moderate GVA
If you just have a security concern as you should with all IP cameras put them on an isolated vLAN and punch just rstp access to them through the firewall from a separate local vLAN for the NVR. Don’t give them internet access.
I had a Yale Asure SL with no key for several years and NEVER needed to bypass it, it also had an option to emergency power it from the outside with a 9v battery.
Even then nearly all smart locks have keys, AGAIN the reason I want to do this is to ensure doors are all locked at night and when everyone leaves the house. Some kids and family members are unreliable in locking doors behind them.
The RTSP streams on most older units is really unstable (feeds freeze/stopworking etc) and makes it hard to use in frigate / Blueiris / Even Synology surveillance station.. SOME of the brand new ones are OK but it is really hard to tell as Reolink frequently sells the same "Model" but with completely different hardware revisions and DIFFERENT firmware available per revision.
If you stick with the native reolink HW / Apps / NVRs they are a great value. Lots of bang for the buck.
If you want to use cameras with frigate, look at the frigate and go2rtc projects recommended cameras / forums / git repos for info on models that are known to work.
baby teeth: this will probably differ in what they are called by province / state / country