Zwave-JS and ws://localhost:3000

papasierra · March 28, 2021, 10:50am

Having successfully installed Zwavejs2mqtt at the last iteration of my continuous upgrading of Home Assistant (ie every time I mess up and can’t work out how to correct my error I simply format the disc and reinstall Raspberry OS and HA), this time round I thought I would install Zwave-JS.
I have been able to set it up as an Add-on. The add-on log shows that Zwav-JS is installed and connected to the UZB device.
However when I try to install the integration I can’t get it installed.
I have tried installing the integration with the option “Use the Zwave-JS Supervisor add-on” ticked. I get no further than image number 2.
I have tried with this option unticked, and get to a second pop up (image number 3). But cannot get any further (image number 4). For some reason the default URL is not accepted.
I have Grafana in docker and I know this uses port 3000. But I have stopped and deleted the Grafana container and I still can’t get Zwave-JS to work.
I have tried setting the port to be 3001 in the Add-on config and the integration config but no go.
Is this something to do with running HA Supervised on Raspberry OS? I have tried setting the integration URL to the IP address of the Pi that HA is running on, but no good.
Just in case this is relevant, I have changed the ownership of the /usr/share/hassio directory to my username so that I can edit configuration.yaml etc.

All help greatly appreciated.

21-03-28 08:24:07 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
21-03-28 08:24:07 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
21-03-28 08:24:08 INFO (MainThread) [supervisor.store] Loading add-ons from store: 66 all - 0 new - 0 remove
21-03-28 08:24:08 INFO (MainThread) [supervisor.store] Loading add-ons from store: 66 all - 0 new - 0 remove
21-03-28 09:03:59 INFO (MainThread) [supervisor.addons] Creating Home Assistant add-on data folder /data/addons/data/core_zwave_js
21-03-28 09:03:59 INFO (SyncWorker_2) [supervisor.docker.interface] Downloading docker image homeassistant/aarch64-addon-zwave_js with tag 0.1.14.
21-03-28 09:04:28 INFO (MainThread) [supervisor.addons] Add-on 'core_zwave_js' successfully installed
21-03-28 09:06:33 WARNING (MainThread) [supervisor.addons.options] Option 'options' does not exist in the schema for Z-Wave JS (core_zwave_js)
21-03-28 09:23:01 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-03-28 09:23:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-03-28 09:23:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-03-28 09:23:01 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-03-28 09:23:01 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-03-28 09:23:01 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-03-28 09:23:01 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-03-28 09:24:05 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-03-28 09:28:56 WARNING (MainThread) [supervisor.addons.options] Option 'options' does not exist in the schema for Z-Wave JS (core_zwave_js)
21-03-28 09:30:59 WARNING (MainThread) [supervisor.addons.options] Option 'options' does not exist in the schema for Z-Wave JS (core_zwave_js)
21-03-28 09:31:21 INFO (SyncWorker_1) [supervisor.docker.interface] Restarting homeassistant/raspberrypi4-64-homeassistant
21-03-28 09:35:02 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-03-28 09:35:15 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-03-28 09:35:56 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-03-28 09:51:17 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-zwave_js with version 0.1.14
21-03-28 09:51:19 INFO (MainThread) [supervisor.discovery] Sending discovery to Home Assistant zwave_js from core_zwave_js
21-03-28 09:51:19 INFO (MainThread) [supervisor.discovery] Discovery c08629f7d4404072b82310bc19c39f72 message send
21-03-28 09:57:33 INFO (MainThread) [supervisor.host.info] Updating local host information
21-03-28 09:57:34 INFO (MainThread) [supervisor.host.services] Updating service information
21-03-28 09:57:34 INFO (MainThread) [supervisor.host.network] Updating local network information
21-03-28 09:57:36 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-03-28 09:57:36 INFO (MainThread) [supervisor.host] Host information reload completed
21-03-28 10:01:24 INFO (SyncWorker_1) [supervisor.docker.interface] Restarting homeassistant/raspberrypi4-64-homeassistant
21-03-28 10:01:36 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-03-28 10:02:33 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-03-28 10:16:22 INFO (MainThread) [supervisor.snapshots] Found 2 snapshot files

paszczak · March 28, 2021, 11:10am

Hi there,
you need to select container host name: look at supervisor page then zwave2mqtt page and copy the hostname

Do no tick Use the Z-Wave JS supervisor add-on

papasierra · March 28, 2021, 12:09pm

Thank you for your quick reply. This is what I have in the Supervisor Add-on:

I used core-zwave-js instead of local host so I had core-zwave-js:3000

No luck - it still failed to connect.

I had a look in Portainer, and the zwave_js container name is “addon_core_zwave_js”. Interestingly when I plugged this in - ws://addon_core_zwave_js:3000, the pop up took about 5 seconds before rejecting it rather than immediately showing the “Failed to connect” message.

Regarding the option “Use the Z-Wave JS Supervisor add-on”, it is odd that I don’t tick that box, as I have the Supervisor add-on installed. I have tried with it on and off but still no luck.

Incidentally @paszczak I see you mentioned zwave2mqtt - I am not using that with my current iteration. Although I may have to use if I can’t get Zwave-JS working.

For the record, here is the Supervisor add-on log for Zwave-JS:

<--- Last few GCs --->
[245:0x7fb29ca290]   850393 ms: Scavenge 1889.3 (1895.0) -> 1887.7 (1895.0) MB, 4.4 / 0.0 ms  (average mu = 0.335, current mu = 0.319) task 
[245:0x7fb29ca290]   850438 ms: Scavenge 1889.3 (1899.0) -> 1887.8 (1899.3) MB, 5.9 / 0.0 ms  (average mu = 0.335, current mu = 0.319) task 
[245:0x7fb29ca290]   850524 ms: Scavenge 1891.0 (1899.3) -> 1888.0 (1899.3) MB, 5.3 / 0.1 ms  (average mu = 0.335, current mu = 0.319) task 
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
[13:13:47] INFO: Successfully send discovery information to Home Assistant.
2021-03-28T12:13:49.427Z DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
                                  ╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
                                    ███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
                                   ███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
                                  ███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
                                  ╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
2021-03-28T12:13:49.437Z DRIVER   version 7.0.0
2021-03-28T12:13:49.439Z DRIVER

Does the Fatal Error mean something isn’t installing?

papasierra · March 29, 2021, 9:31pm

Problem solved. Instead of selecting /dev/ttyAMA0 in the Add-on configuration options for the device, I selected the other option in the drop down list which looks like an identifier with lots of letters and numbers. Saved that, back to Configuration/Add Integration, select Zwave-JS and accept the “Use the Z-Wave JS Supervisor add-on”, and it installed within seconds.

Chris_Vandivere · October 9, 2021, 1:46am

Huge help - saved me, thank you.