zwave
and a BE469 lock right?
Yes that is correct
If you enable the debugging, you can see whatās happening, but ultimately these locks work best in ozw
.
I would be willing to try to switch to open zwave is that something I can just switch over or do I have to re pair everything and start from square 1
You can write your own Lovelace.
Yes, just make sure you copy your network key somewhere you can put it in for later.
okay where can I find my current network key? I can find where im supposed to set the configuratiuon paramater of the openzwave addon but obviously it needs to match
If you didnāt enter it into your configuration.yaml
itāll be in .storage/core.config_entries
you can search in that file for ānetwork_keyā.
sweet thanks for all your help. I found the key stopped my old zwave network started open zwave i see and can control devices in that panel however the beta integration says it cant find a zwave and mqtt setupā¦ I have an external setup mqtt server running on a seperate device that I think is making it not workā¦ If i switch to mosquitto on the device ill break so many other things lol
I run MQTT separate from HA it works fine. It sounds like youāre trying to use the addon? Are you using a supervised HA install (HAOS)?
yes im a supervised install. Its the openzwave beta addon that wont start and is complaining
In order to do what you want, youāll need to remove the addon, install the portainer addon and spin up a non-addon version of ozwdaemon.
You can use the docker compose I compiled in this thread to get it working in portainer easier.
well to test my theory I dumped my mqtt integration rebooted setup the default rebooted and now the two are talkingā¦ If this is the future I may need to stick with this vs the old zwave integrationā¦ I just have a bunch of custom arduino type devices that all communicate with my old mosquitto server I had long before I got into home assistant. so now Iām just going to have to either look into what you are saying or Iāll have to update the firmware on all of my diy devices to connect to the new serverā¦
Alternatively you can bridge your MQTT with the one OZW is using.
Add this to the end of your mosquitto.conf
# External MQTT Broker
connection external-bridge
address address.of.your.ha.server
topic # both
remote_username [redacted]
remote_password [redacted]
so this will just forward messages from old to new so they still get to home assistant? if so you are awesome lol
Yes, itās 2 way communication
The only other downside Iām seeing is Ill have to go find all these devices and rename them exactly as my old ones were or ill mess up so many automations and dashboards oh man what a mess lol better now than in the future I suppose
better now then after you add tons more devices
theres already so many hahaha. one thing thats confusing is the old app says I had 44 devices the new one says it has 31 devicesā¦ I wonder what is missing hopefully ghost nodes lol