zwavejs2mqtt

For Z-Wave related questions in Domoticz

Moderator: leecollings

JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

mgugu wrote: Friday 14 October 2022 13:53 The ":" is mandatory because it separates the external controler reference from the internal one.
You probably have a wrong configuration.
You should follow the wiki at https://www.domoticz.com/wiki/ZwaveJS2MQTT in which docker-compose is recommended.
If you absolutely prefer command line, instructions are here: https://zwave-js.github.io/zwave-js-ui/ ... uick-start
Thnx. I will start all over again with the wiki as a guide and not the till now used https://zwave-js.github.io/zwave-js-ui/ ... uick-start.

Let you know the results.
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

I really give up
Been hasling 2 days now and I don't even get docker compose installed propperly.
So installing Mosquitto is difficult as the wiki assumes docker compose is installed.
tried this:

Code: Select all

Install Docker
ZWavejs2MQTT will run as a container, so Docker must be installed first.
Run these command to install Docker:

cd ~
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
sudo usermod -aG docker pi
sudo apt install python3 
sudo apt install python3.pip
sudo pip3 -v install docker-compose
and this gives me the next fault:

Code: Select all

  This package requires Rust >=1.56.0.
error
  Failed building wheel for bcrypt
  Running setup.py clean for bcrypt
  Running command /usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-ho5h88v2/bcrypt/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" clean --all
  running clean
  removing 'build/lib.linux-armv7l-cpython-37' (and everything under it)
  'build/bdist.linux-armv7l' does not exist -- can't clean it
  'build/scripts-3.7' does not exist -- can't clean it
  removing 'build'
  running clean_rust

      =============================DEBUG ASSISTANCE=============================
      If you are seeing a compilation error please try the following steps to
      successfully install bcrypt:
      1) Upgrade to the latest pip and try again. This will fix errors for most
         users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
      2) Ensure you have a recent Rust toolchain installed. bcrypt requires
         rustc >= 1.56.0.

      Python: 3.7.3
      platform: Linux-5.10.103-v7l+-armv7l-with-debian-10.13
      pip: 18.1
      setuptools: 65.5.0
      setuptools_rust: 1.5.2
      rustc: n/a
      =============================DEBUG ASSISTANCE=============================

  error: can't find Rust compiler

  If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.

  To update pip, run:

      pip install --upgrade pip

  and then retry package installation.

  If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.

  This package requires Rust >=1.56.0.
  Failed cleaning build dir for bcrypt
Failed to build bcrypt
docker 6.0.0 has requirement requests>=2.26.0, but you'll have requests 2.21.0 which is incompatible.
Installing collected packages: typing-extensions, zipp, importlib-metadata, attrs, pyrsistent, jsonschema, bcrypt, paramiko, docker, PyYAML, docopt, docker-compose






  changing mode of /usr/local/bin/jsonschema to 755
  Created temporary directory: /tmp/pip-record-ky657xyv
  Running setup.py install for bcrypt ...     Running command /usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-ho5h88v2/bcrypt/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-ky657xyv/install-record.txt --single-version-externally-managed --compile
    running install
    /tmp/pip-build-env-0yobe7f_/lib/python3.7/site-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
      setuptools.SetuptoolsDeprecationWarning,
    running build
    running build_py
    creating build
    creating build/lib.linux-armv7l-cpython-37
    creating build/lib.linux-armv7l-cpython-37/bcrypt
    copying src/bcrypt/__about__.py -> build/lib.linux-armv7l-cpython-37/bcrypt
    copying src/bcrypt/__init__.py -> build/lib.linux-armv7l-cpython-37/bcrypt
    running egg_info
    writing src/bcrypt.egg-info/PKG-INFO
    writing dependency_links to src/bcrypt.egg-info/dependency_links.txt
    writing requirements to src/bcrypt.egg-info/requires.txt
    writing top-level names to src/bcrypt.egg-info/top_level.txt
    reading manifest file 'src/bcrypt.egg-info/SOURCES.txt'
    reading manifest template 'MANIFEST.in'
    warning: no previously-included files found matching 'requirements.txt'
    warning: no previously-included files found matching 'release.py'
    warning: no previously-included files found matching 'mypy.ini'
    warning: no previously-included files matching '*' found under directory '.github'
    warning: no previously-included files matching '*' found under directory '.circleci'
    warning: no previously-included files found matching 'src/_bcrypt/target'
    warning: no previously-included files matching '*' found under directory 'src/_bcrypt/target'
    adding license file 'LICENSE'
    writing manifest file 'src/bcrypt.egg-info/SOURCES.txt'
    copying src/bcrypt/_bcrypt.pyi -> build/lib.linux-armv7l-cpython-37/bcrypt
    copying src/bcrypt/py.typed -> build/lib.linux-armv7l-cpython-37/bcrypt
    running build_ext
    running build_rust

        =============================DEBUG ASSISTANCE=============================
        If you are seeing a compilation error please try the following steps to
        successfully install bcrypt:
        1) Upgrade to the latest pip and try again. This will fix errors for most
           users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
        2) Ensure you have a recent Rust toolchain installed. bcrypt requires
           rustc >= 1.56.0.

        Python: 3.7.3
        platform: Linux-5.10.103-v7l+-armv7l-with-debian-10.13
        pip: 18.1
        setuptools: 65.5.0
        setuptools_rust: 1.5.2
        rustc: n/a
        =============================DEBUG ASSISTANCE=============================

    error: can't find Rust compiler

    If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.

    To update pip, run:

        pip install --upgrade pip

    and then retry package installation.

    If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.

    This package requires Rust >=1.56.0.
error
Cleaning up...
  Removing source in /tmp/pip-install-ho5h88v2/bcrypt
Removed build tracker '/tmp/pip-req-tracker-kll8w8k_'
Command "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-ho5h88v2/bcrypt/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-ky657xyv/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-ho5h88v2/bcrypt/
Exception information:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 143, in main
    status = self.run(options, args)
  File "/usr/lib/python3/dist-packages/pip/_internal/commands/install.py", line 386, in run
    use_user_site=options.use_user_site,
  File "/usr/lib/python3/dist-packages/pip/_internal/req/__init__.py", line 49, in install_given_reqs
    **kwargs
  File "/usr/lib/python3/dist-packages/pip/_internal/req/req_install.py", line 791, in install
    spinner=spinner,
  File "/usr/lib/python3/dist-packages/pip/_internal/utils/misc.py", line 723, in call_subprocess
    % (command_desc, proc.returncode, cwd))
pip._internal.exceptions.InstallationError: Command "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-ho5h88v2/bcrypt/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-ky657xyv/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-ho5h88v2/bcrypt/
Does somebody has an step by step how to to get things working because my patience with ozw (and of my wife) is completely over.
Please take me by the hand :oops:
For non programmers the wiki is not user friendly I must say.
It seems that in HA it is more easy to install everything.

Sorry for being so disappointed

Jan
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
ferrosk
Posts: 44
Joined: Saturday 26 August 2017 20:13
Target OS: Linux
Domoticz version: 2023.2
Contact:

Re: zwavejs2mqtt

Post by ferrosk »

Hi,

You can install docker-compose binary from Docker Compose gitthub repository.

For your platform (armv7l):

Code: Select all

sudo curl -L https://github.com/docker/compose/releases/download/v2.11.2/docker-compose-linux-armv7 -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
then try:

Code: Select all

$ docker-compose version
Docker Compose version v2.11.2
Domoticz 2023.2 on Odroid M1 and Armbian
MySensors (RFM69 Serial GW): bunch of DIY sensors/devices
Zwave (Z-Wave.me RaZberry board): Danfoss devices
Zigbee (Sonoff Dongle Plus): IKEA, Tesla devices
TSkar
Posts: 29
Joined: Wednesday 20 June 2018 16:47
Target OS: Linux
Domoticz version: 2.13055
Location: Stavanger, Norway
Contact:

Re: zwavejs2mqtt

Post by TSkar »

Do you strictly need docker?

Install Mosquitto. (Open ports for listener if your not running mosquitto, zigbee-js-ui, domoticz, etc, all on 1 computer.)
Install NodeJS - https://github.com/nodesource/distributions
Install Zwave-js-ui - https://zwave-js.github.io/zwave-js-ui/ ... er-methods (I used get from github option)

To autostart make this in /etc/systemd/system/zwavejsui.service
Replace USERNAME with your actual username.

Code: Select all

  [Unit]
  Description:Zwave to MQTT Gateway
  Documentation=https://zwave-js.github.io/zwave-js-ui
  After=network.target
  
  [Service]
  Type=simple
  WorkingDirectory=/home/USERNAME/zwave-js-ui/
  ExecStart=npm start
  ExecStop=npm stop
  User=USERNAME
  Restart=always
  
  [Install]
  WantedBy=multi-user.target

Code: Select all

sudo systemctl daemon-reload
sudo systemctl start zwave2mqtt
sudo systemctl status zwave2mqtt
If zwave2mqtt is running ok

Code: Select all

sudo systemctl enable zwave2mqtt
I'm shure there are better ways to do this, but it works.
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

Hi guys,

I came a lot further with your help.
- docker-compose is installed
- mosquitto is installed and working
- zwave2mqtt is giving an error.

Code: Select all

pi@Pi4-Nieuw:~/zwavejs2mqtt $ sudo docker-compose up -d
[+] Running 8/8
 ⠿ zwave-js-ui Pulled                                                     49.8s
   ⠿ c6556b3b6858 Pull complete                                            1.3s
   ⠿ 2274198401fd Pull complete                                           15.6s
   ⠿ 72dfb3b1ff2d Pull complete                                           16.3s
   ⠿ 7afe63fea635 Pull complete                                           16.5s
   ⠿ 7989bb2f72a0 Pull complete                                           17.3s
   ⠿ eed636a44740 Pull complete                                           46.7s
   ⠿ 4f4fb700ef54 Pull complete                                           46.9s
[+] Running 2/3
 ⠿ Network zwavejs2mqtt_zwave  Created                                     0.2s
 ⠿ Volume "zwave-config"       Created                                     0.0s
 ⠿ Container zwave-js-ui       Starting                                    1.7s
Error response from daemon: error gathering device information while adding custom device "/dev/serial/by-id/usb-0658_200-if00": no such file or directory
Error response from daemon: error gathering device information while adding custom device "/dev/serial/by-id/usb-0658_200-if00": no such file or directory

The stick is working (Aeotec gen5) and in docker-compose.yml heb ik:

Code: Select all

version: '3.7'
services:
  zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:latest
    restart: always
    tty: true
    stop_signal: SIGINT
    environment:
      - SESSION_SECRET=mysupersecretkey
      - ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db
      # Uncomment if you want logs time and dates to match your timezone instead of UTC
      # Available at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
      #- TZ=America/New_York
    networks:
      - zwave
    devices:
      # Do not use /dev/ttyUSBX serial devices, as those mappings can change over time.
      # Instead, use the /dev/serial/by-id/X serial device for your Z-Wave stick.
      - '/dev/serial/by-id/usb-0658_200-if00:/dev/zwave'
    volumes:
      - zwave-config:/usr/src/app/store
    ports:
      - '8091:8091' # port for web interface
      - '3000:3000' # port for Z-Wave JS websocket server
networks:
  zwave:
volumes:
  zwave-config:
    name: zwave-config
So need a little bit of more help.

thnx in advance

Jan
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
roblom
Posts: 402
Joined: Wednesday 26 February 2014 15:28
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: the Netherlands
Contact:

Re: zwavejs2mqtt

Post by roblom »

Is the path to your stick correct?
Try browsing to it with a file explorer.
Last edited by roblom on Saturday 15 October 2022 10:41, edited 1 time in total.
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

roblom wrote: Saturday 15 October 2022 10:41 Is it possible that you removed the mapping of your stick in the line, what I have is:

- '/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave'

So I think you are missing the :/dev/zwave part.
no I have exactly the same in the yml file.
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
ksacca
Posts: 80
Joined: Thursday 31 May 2018 21:49
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: zwavejs2mqtt

Post by ksacca »

JuanUil wrote: Saturday 15 October 2022 10:42 no I have exactly the same in the yml file.
I noticed you talked about a pi4. The Aeotec Gen5 stick has a hardware issue when connecting to a pi4, so it will not work when connected directly to the pi. You have to use an old usb 2.0 hub to get it working. The aeotec gen5+ stick (updated version) does work with the pi4 though, so check which one you have exactly.
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

Hi ksacca,

I know that problem. The stick is connected through a hub.
Changed to another usb port with no succes either.
In domoticz it is recognized.
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
ksacca
Posts: 80
Joined: Thursday 31 May 2018 21:49
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: zwavejs2mqtt

Post by ksacca »

OK, sorry. I went back a page but didn't notice this. What I did notice is you use:

Code: Select all

'/dev/serial/by-id/usb-0658_200-if00:/dev/zwave'
But you seem to miss a 0 ('/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave') Can you try using:

Code: Select all

'/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave'
In the previous page I see you mentioned the correct path to the device, but in the last configuration and error log I see it's missing. Migth be a long shot, but you never know.
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

SUPER!!!! That did the trick!
Thnx a lot!
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

:oops: But now when I go to http://192.168.2.21:8091/ the gui won't open.
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
ksacca
Posts: 80
Joined: Thursday 31 May 2018 21:49
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: zwavejs2mqtt

Post by ksacca »

If you ssh to your raspberry and execute

Code: Select all

docker container ls
Do you see your container and can you see the mapped ports correctly?

Example:

Code: Select all

0.0.0.0:3000->3000/tcp, :::3000->3000/tcp, 0.0.0.0:8091->8091/tcp, :::8091->8091/tcp
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

I get this:

Code: Select all

pi@Pi4-Nieuw:~/zwavejs2mqtt $ sudo docker container ls
CONTAINER ID   IMAGE                        COMMAND                  CREATED          STATUS                            PORTS                                   NAMES
62ab007f98a4   zwavejs/zwave-js-ui:latest   "docker-entrypoint.s…"   33 minutes ago   Restarting (133) 20 seconds ago                                           zwave-js-ui
87d0fbf29905   dtv3-8082                    "docker-php-entrypoi…"   10 months ago    Up 23 minutes                     0.0.0.0:8082->80/tcp, :::8082->80/tcp   dtv3-8082
so no ports
Dashticz on port 8082 is working oké
looks like it is constantly restarting
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
mgugu
Posts: 218
Joined: Friday 04 November 2016 12:33
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: France
Contact:

Re: zwavejs2mqtt

Post by mgugu »

run "docker logs zwave-js-ui" to see the logs.
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

Code: Select all

pi@Pi4-Nieuw:~/zwavejs2mqtt $ sudo docker logs zwave-js-ui


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbee334ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbec9c4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe84c4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbef634ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbee3d4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeb5c4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbee9d4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea054ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9ff4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe99d4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbebeb4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbedb14ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea774ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8fa4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe87a4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbecb34ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbec974ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8f14ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeb724ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeee34ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8ef4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8324ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea184ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9784ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9c64ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea204ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbed064ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbee9b4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeae04ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbecf94ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbefec4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbed6b4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbec6b4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea1d4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8774ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8bb4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbefc14ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeb024ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea234ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9514ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe83c4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbec714ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe97b4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeba84ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbef1e4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbec764ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe81a4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9344ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbebd64ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8e74ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbec1a4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9b54ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbef694ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9f74ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbef274ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbee8d4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9f14ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe85b4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbee074ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea904ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8294ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8034ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbedb94ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea1f4ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeed94ac


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeb764ac
pi@Pi4-Nieuw:~/zwavejs2mqtt $
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
mgugu
Posts: 218
Joined: Friday 04 November 2016 12:33
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: France
Contact:

Re: zwavejs2mqtt

Post by mgugu »

You can check the ports in use with "sudo netstat -tulpna".
You can try my yml file:

Code: Select all

version: '3.7'
services:
  zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:latest
    restart: always
    tty: true
    stop_signal: SIGINT
    environment:
      - SESSION_SECRET=mysupersecretkey
      - TZ=Europe/Paris
    networks:
      - zwave
    devices:
      - /dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0
    volumes:
      - ./store:/usr/src/app/store
    ports:
      - '8091:8091' # port for web interface
      - '3100:3000' # port for zwave-js websocket server
networks:
  zwave:
    external:
      name: zwavejs2mqtt
Volumes are in local folder, changed websocket port because already used, changed internalcontroler reference to /dev/ttyACM0 for some reason that I do not remember :roll:
ksacca
Posts: 80
Joined: Thursday 31 May 2018 21:49
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: zwavejs2mqtt

Post by ksacca »

Could you check out https://github.com/zwave-js/zwave-js-ui/issues/2725 and https://zwave-js.github.io/zwave-js-ui/ ... h-with-820

I see you did a new install, but did you use buster or bullseye. There's currently an issue when running buster apparently.

You can check it with

Code: Select all

grep "PRETTY_NAME" /etc/os-release
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

I use buster
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
JuanUil
Posts: 497
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.11083
Location: Asten NB Nederland
Contact:

Re: zwavejs2mqtt

Post by JuanUil »

Upgraded to bullseye working fine now.
Thnx for all your help guys!!
Your mind is like a parachute,
It only works when it is opened!

RPI4 several Fibaro, KaKu, Neocoolcam switches, Z-Wave, Zigbee2Mqtt, Ikea bulbs and remote, Zigbee temp nodes
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest