Using a Vera Edge as a network-attached zwave device (skipping the vera software)

I also started with a Vera Lite when it was first released. Since then, I’ve been managing my home automation through a Razberry in slave mode with Jeedom and ZWaveMQTT, along with a Jeedom master. However, my Vera has always been there to control some Z-Wave modules and alarm scenes. I really like its integrated concept of “tripped armed” or “tripped and not armed,” which I haven’t found elsewhere. In the end, I’m just asking if this functionality is still up-to-date. I’m planning to dust off my Vera Lite, which is still functional but has been sitting aside for the Vera Plus, and give controlling Z-Wave devices from Home Assistant a try. We’ll see how it goes.

Vera works well with HA. I have my Vera Plus for most of my z-wave stuff although I have a z-wave stick connected to my HA. I have only a few z-wave devices on the stick in HA and move them from the Vera only when I have to or making new installations. No rules or anything else in the Vera, just the z-wave stuff and it has been rock solid. The Vera software and HA integration works side-by-side and you can still used the Vera interface as normal.

Edit: When thinking about it, one hiccup was when the energy measurements from the Fibaro plugs stopped working (1-2 years ago) in from Vera into HA, I then bought some new Zigbee plugs to where I need those measurements (washing machine, dryer etc.). This was before I bought the z-wave stick.

Dear Community,
I have issues with a nukevera associated with ZWAVE JS UI installed in Docker Synology. The process stop after some time, also ssh on the vera disconnect (I gues the vera is rebooting). Any similar experience and suggestions for resolving this ?
Thanks a lot
ZWAVE JS UI log below:

  • 6:46.401 INFO APP: Version: 9.9.1.f6dff21
  • 2024-03-25 10:36:46.524 INFO APP: Application path:/usr/src/app

  • |___ / \ \ / / | |/ ___| | | | | _|
  • / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |  
    
  • / /_____\ / / / ’ \ \ / / _ \ _ | |_ \ | | | | | |
  • / /__ \ /\ / (| |\ V / / | || |_) | | |__| || |
  • /| / / _,| _/ _| _/|/ _/|___|
  • 2024-03-25 10:36:46.599 WARN STORE: scenes.json not found
  • Logging to file:
  • /usr/src/app/store/logs/zwavejs_2024-03-25.log
  • 2024-03-25 10:36:52.052 INFO Z-WAVE-SERVER: ZwaveJS server listening on 0.0.0.0:3000
  • 2024-03-25 10:36:53.494 INFO Z-WAVE-SERVER: DNS Service Discovery enabled
  • 2024-03-25 10:53:23.727 INFO Z-WAVE-SERVER: Client disconnected
  • 2024-03-25 10:53:23.739 INFO Z-WAVE-SERVER: Server closed
  • Logging to file:
  • /usr/src/app/store/logs/zwavejs_2024-03-25.log
  • 2024-03-25 10:54:31.115 INFO Z-WAVE-SERVER: ZwaveJS server listening on 0.0.0.0:3000
  • 2024-03-25 10:54:31.936 INFO Z-WAVE-SERVER: DNS Service Discovery enabled
  • ZWaveError: The controller is not yet ready! (ZW0103)
  • at Driver.get controller [as controller] (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:752:10)
    
  • at Timeout._onTimeout (/usr/src/app/server/lib/ZwaveClient.js:2831:30)
    
  • at listOnTimeout (node:internal/timers:569:17)
    
  • at processTimers (node:internal/timers:512:7)