Unable to Access ZWAVE JS UI through port 8091

For Z-Wave related questions in Domoticz

Moderator: leecollings

Post Reply
DaveWils
Posts: 7
Joined: Friday 13 April 2018 0:14
Target OS: Windows
Domoticz version:
Contact:

Unable to Access ZWAVE JS UI through port 8091

Post by DaveWils »

Followed the wiki
https://www.domoticz.com/wiki/Zwave-JS-UI

Code: Select all

docker-compose.yaml
version: "3.7"
services:
  zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:latest
    restart: unless-stopped
    tty: true
    stop_signal: SIGINT
    environment:
      - SESSION_SECRET=mySecretSession
      - TZ=Europe/Brussels
    devices:
      - '/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave'
    volumes:
      - ./store:/usr/src/app/store
    ports:
      - "8091:8091" # port for web interface
      - "3000:3000" # port for Z-Wave JS websocket server
The server/service is correctly started

But cannot access it from my laptop http://192.168.178.22:8091

Also tried on the Raspberry PI
wget http://localhost:8091
--2024-03-02 12:07:02-- http://localhost:8091/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8091... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8091... failed: Connection refused.

Are there any ports that need to be opened?
Edit Waltervl: code brackets
mgugu
Posts: 208
Joined: Friday 04 November 2016 12:33
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: France
Contact:

Re: Unable to Access ZWAVE JS UI through port 8091

Post by mgugu »

There is no netwoks settings in your yml file. Check https://github.com/zwave-js/zwave-js-ui ... ompose.yml
DaveWils
Posts: 7
Joined: Friday 13 April 2018 0:14
Target OS: Windows
Domoticz version:
Contact:

Re: Unable to Access ZWAVE JS UI through port 8091

Post by DaveWils »

Thank you for your help, now I used the following docker-compose.yaml. This means that the one that's in the WIKI is just wrong then?

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_0200-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
Got a bit better result, how can i see what's actually wrong in this zwavejs-ui module, because it just says started, there's no log file except if you enable it through the UI which i cannot access?

root@Dave-Domo:/opt/zwavejs-ui# docker compose down
[+] Running 2/2
✔ Container zwave-js-ui Removed 0.0s
✔ Network zwavejs-ui_zwave Removed 0.4s
root@Dave-Domo:/opt/zwavejs-ui# docker compose up -d
[+] Running 0/1
[+] Running 1/2ejs-ui_zwave Creating 0.3s
⠏ Network zwavejs-ui_zwave Created 4.0s
✔ Container zwave-js-ui Started 3.7s
root@Dave-Domo:/opt/zwavejs-ui# wget http://localhost:8091
--2024-03-03 09:40:37-- //localhost:8091/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8091... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

--2024-03-03 09:40:39-- (try: 2) //localhost:8091/
Connecting to localhost (localhost)|::1|:8091... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8091... failed: Connection refused.
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8091... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8091... failed: Connection refused.

Also from the (external) browser, I'm getting a connection refused now, which is better than before...
http://192.168.178.22:8091
This site can’t be reached192.168.178.22 refused to connect.

Edit Waltervl, code brackets
DaveWils
Posts: 7
Joined: Friday 13 April 2018 0:14
Target OS: Windows
Domoticz version:
Contact:

Re: Unable to Access ZWAVE JS UI (through port 8091)

Post by DaveWils »

Anybody? Anything?
BartSr
Posts: 347
Joined: Sunday 03 July 2016 16:16
Target OS: Raspberry Pi / ODroid
Domoticz version: V2024.3
Location: Netherlands
Contact:

Re: Unable to Access ZWAVE JS UI through port 8091

Post by BartSr »

pls post compse file in code window to be able to check the indents.
Raspberry pi 3b
Arduino
KAKU
RfxCom
Zwave
OTGW
Chinese sensors temp (Dallas),movement
Tasmota
Esp8266 espeasy
MQTT
User avatar
waltervl
Posts: 5148
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: Unable to Access ZWAVE JS UI through port 8091

Post by waltervl »

Please check the Zwave-JS-UI repository, issues and discussion. Else ask it there as they develop Zwave-JS-UI. It seems nobody here had your issue. https://github.com/zwave-js/zwave-js-ui

And if you run Buster OS you need to read this https://zwave-js.github.io/zwave-js-ui/ ... /app_crash
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
DaveWils
Posts: 7
Joined: Friday 13 April 2018 0:14
Target OS: Windows
Domoticz version:
Contact:

Re: Unable to Access ZWAVE JS UI through port 8091

Post by DaveWils »

Can you at least help me with my questions:
1) Should it work with the docker-compose.yaml int the WIKI https://www.domoticz.com/wiki/Zwave-JS-UI
Thank you for your help, now I used the following docker-compose.yaml. This means that the one that's in the WIKI is just wrong then?
2) Where can i see the error in order to post/look for my problem on https://github.com/zwave-js/zwave-js-ui
How can i see what's actually wrong in this zwavejs-ui module, because it just says started, there's no log file except if you enable it through the UI which i cannot access? Where are the errors with this docker stuff?
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest