Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]on pi4 shows connected but never gets data from zwave module #146

Closed
2 tasks
scyto opened this issue Jan 5, 2021 · 1 comment
Closed
2 tasks

[bug]on pi4 shows connected but never gets data from zwave module #146

scyto opened this issue Jan 5, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@scyto
Copy link
Contributor

scyto commented Jan 5, 2021

Version

Build/Run method

  • [ X] Docker
  • PKG
  • Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.2.3

Describe the bug
I moved my SD card and z-wave module from pi3 to a pi4 and while the light and main log indicate it is connected to /dev/ttyAMA0 the z-wave log insists the port is open.

I don't know why

To Reproduce

  1. Install pi3 latest raspbian with docker and get zwavejs2mqtt working just fine
  2. move SD card and z-wave module to pi 4
  3. check serial port is still the same path (it is /dev/ttyAMA0 on both.
  4. check log with ``` docker container logs zwavejs2mqtt``
    Seems ok
 ______                       _     ___                  _   _   
|___  /                      (_)   |__ \                | | | |  
   / /_      ____ ___   _____ _ ___   ) |_ __ ___   __ _| |_| |_ 
  / /\ \ /\ / / _` \ \ / / _ \ / __| / /| '_ ` _ \ / _` | __| __|
 / /__\ V  V / (_| |\ V /  __/ \__ \/ /_| | | | | | (_| | |_| |_ 
/_____|\_/\_/ \__,_| \_/ \___| |___/____|_| |_| |_|\__, |\__|\__|
                            _/ |                      | |        
                           |__/                       |_|        

2021-01-05 02:31:04.567 WARN STORE: scenes.json not found
/bin/sh: git: not found
2021-01-05 02:31:06.199 INFO APP: Version: 1.0.0-alpha.2
2021-01-05 02:31:06.200 INFO APP: Application path:/usr/src/app
2021-01-05 02:31:06.462 INFO MQTT: Connecting to mqt://192.168.1.30:1883
2021-01-05 02:31:06.567 INFO ZWAVE: Connecting to /dev/ttyAMA0
2021-01-05 02:31:06.638 INFO APP: Listening on port 8091
2021-01-05 02:31:06.731 INFO MQTT: MQTT client connected
2021-01-05 02:31:07.357 INFO SOCKET: New connection dUK4DkkI7cstpvvCAAAB
2021-01-05 02:31:08.074 INFO SOCKET: New connection TQ7FWi1bDsVs-3ZyAAAD
2021-01-05 02:32:40.559 INFO SOCKET: Event INITED emitted to dUK4DkkI7cstpvvCAAAB
2021-01-05 02:32:43.630 INFO APP: GET / 304 36.492 ms - -
2021-01-05 02:32:43.643 INFO SOCKET: User disconnected dUK4DkkI7cstpvvCAAAB
2021-01-05 02:32:43.655 INFO APP: GET /static/css/app.2f987c695a0127cf0841.css 304 8.144 ms - -
2021-01-05 02:32:43.658 INFO APP: GET /static/js/app.543685e52331359ebfc6.js 304 6.491 ms - -
2021-01-05 02:32:43.798 INFO APP: GET /static/logo.png 304 1.525 ms - -
2021-01-05 02:32:43.883 INFO APP: GET /static/fonts/MaterialIcons-Regular.fa3334f.woff2 304 1.520 ms - -
2021-01-05 02:32:43.949 INFO SOCKET: New connection vB0bF14dZ4BlqWCZAAAF
2021-01-05 02:32:43.967 INFO SOCKET: Event INITED emitted to vB0bF14dZ4BlqWCZAAAF
2021-01-05 02:32:44.010 INFO APP: GET /static/favicons/favicon-32x32.png 200 5.955 ms - 1831

check z-wave log

02:31:01.546 DRIVER   serial port errored: Port is not open

Expected behavior
I expected this to work - i don't know why it doesn't?

Additional context
i know that i should really re-install now i have it in the pi (and i can do that if needed) but shouldn't a move like this just work? Or am i being an idiot?

@scyto scyto added the bug Something isn't working label Jan 5, 2021
@scyto
Copy link
Contributor Author

scyto commented Jan 5, 2021

Well i solved it - seems on a pi4 Bluetooth takes over the AMA0, i have no clue where the serial ports on the GPIO route to when it is like this?

Adding the following to /boot/config.txt fixed the issue

# Disable Bluetooth
dtoverlay=disable-bt

@scyto scyto closed this as completed Jan 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants