![]() ![]() schema config - update the JSON schema config available on platformatic.db.schema.json.migrations apply - apply migration files.migrations create - generate do and undo migration files.You can find more details about the configuration format at: Platformatic.db.json, platformatic.db.yml, or platformatic.db.tml in the current directory. If not specified, the configuration specified will be loaded from -c, -config : Path to the configuration file.So again I’ll be taking the vanilla route. Given that I generally run “as vanilla as possible” and as the statement by Fishwaldo and others that future ozw upgrades will be modular and transparent, I think I’ll stick with that.įurther, when the standards are ‘opened up’ then there will be ‘something’ put in the ozw slot so it will probably be rewritten as needed or as an ‘official core’ dropped in (with suitable modifications around it to accommodate given the current explanation of Z/IP, the avoidance of discussing cost and (to be honest) my conceptual usage scenarios … I don’t see what benefits Z/IP would bring me. Given this, it sounds like the “HA New Z-wave Implementation” will be the one containing the extra layer and the Z-wave2MQTT one ‘more native’ - that is unless mqtt itself is a layer on HA itself so mqtt translated in, processed, and then translated out again. To be honest I’m not sure why it’s there as the MQTT structure doesn’t extend into the mesh (but then it’s a closed proprietary system, so maybe it does ! ) and I suppose any wrapper needs “ A” protocol. So I was wrong when I told 'there was no mqtt in the “HA New Z-wave Implementation” ’ Z/IP: Is not supported yet by Home Assistant but in theory the new Home Assistant component should be able to also talk to Z/IP gateways instead of/in addition to the OZW Thanks, that’s very informative. It’s talking to the Z-Wave mesh through the OpenZwave daemon using mqtt as the transport protocol. New Z-Wave component (as discussed in this post): Will be an official homeassistant component to replace the current Z-Wave component and translates Z-Wave mesh/devices into something HomeAssistant can understand. Translates Z-Wave mesh with all it’s devices to MQTT world, to be used by every platform that understands MQTT, including Home Assistant offcourse. Zwave2mqtt: NodeJS wrapper around OZW libs, very actively maintained and provides full functionality. Will most likely be phased out once new implementation(s) are better. It can also be implemented into Hass, just like other hubs like Hue, vera and such.Ĭurrent Z-Wave component in Hass: openzwave 1.4, wrapper around ozw. See it as a proprietary hub and OZW as the opensource software hub. Z/IP is the closed source approach but would require special hardware/hubs or additional software licensing costs. ![]() It’s goal is to use MQTT to communicate with Z Wave devices while in the OZW Daemon approach (where we’re working on), MQTT is only used as transport between clients, no translation happened yet. Zwave2mqtt is a node wrapper around the OpenZwave library, translating the mesh and it’s devices into MQTT topics. ![]() So you can see this OpenZwave Daemon as an alternative to the Z/IP specification, living in the open source/community world. Or attach OZW Daemon directly to other platforms like Node Red. So the new Home Assistant implementation is just one of the clients for the OZW Daemon, there will also be a control panel etc. It uses MQTT as the transport protocol because it’s well known and easy. It “translates” the Z-wave mesh (serial API) to deliver it to connected clients (such as Home Assistant). It’s maintained by the developers of OpenZwave itself so directly at the source. What we want to do is detach the OZW Controller/mesh from Hass and that’s where the OpenZwave Daemon jumps in. Because OZW is the controller and it’s directly attached to Home Assistant, restarting Home Assistant leads to restarting the Z Wave mesh. The Z-wave mesh takes a little time to start as it needs to interview all nodes. Z-Wave is now implemented in hass by leveraging a python wrapper around OpenZwave, this leads to multiple issues, most important that the python wrapper can’t cope up with changes in the (O)ZW specs. ![]()
0 Comments
Leave a Reply. |