Transmit message format: CayenneLPP and customize mqtt topic

Hi, I would like to use CayenneLPP as message format, because it allows to send more than one data at once to reduce battery consumption. How can I achieve that Wazigate is able to pass through the messages to the server (own server)?
And: I would like to customize the MQTT topics. How can I do that?
Thank you!
Christian

For CayenneLPP messages check out the Wazigate Developer version: https://youtu.be/IWs4zOi89ms

The new versions use LoRaWAN+CayenneLPP by default.

You can host the Waziup Cloud on your own and use your server with your gateway. Have a look at the WaziCloud Readme’s on GitHub.

Unfortunately, this is not possible. The MQTT topics for devices/sensors/data match the REST API an can not be changed.

Hi Johann
thank you for responding and your hints. I tried out and have following issues:

  • Following the instructions of https://youtu.be/IWs4zOi89ms I get some errors:

    Installing Docker…
    Failed to stop docker.service: Unit docker.service not loaded.
    Failed to disable unit: Unit file docker.service does not exist.

Executing docker install script, commit: 26ff363bcf3b3f5a00498ac43694bf1c7d9ce16c

  • sh -c apt-get update -qq >/dev/null

  • sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null

  • sh -c curl -fsSL “https://download.docker.com/linux/raspbian/gpg” | apt-key add -qq - >/dev/null
    Warning: apt-key output should not be parsed (stdout is not a terminal)

  • sh -c echo “deb [arch=armhf] https://download.docker.com/linux/raspbian buster stable” > /etc/apt/sources.list.d/docker.list

  • sh -c apt-get update -qq >/dev/null

  • [ -n ]

  • sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    Setting up docker-ce (5:19.03.9~3-0~raspbian-buster) …
    Job for docker.service failed because the control process exited with error code.
    See “systemctl status docker.service” and “journalctl -xe” for details.
    invoke-rc.d: initscript docker, action “start” failed.
    ● docker.service - Docker Application Container Engine
    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Active: activating (auto-restart) (Result: exit-code) since Tue 2020-05-26 11:38:58 BST; 24ms ago
    Docs: https://docs.docker.com
    Process: 14028 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
    Main PID: 14028 (code=exited, status=1/FAILURE)
    dpkg: error processing package docker-ce (–configure):
    installed docker-ce package post-installation script subprocess returned error exit status 1

    Errors were encountered while processing:
    docker-ce
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    Done

Job for hostapd.service failed because the control process exited with error code.
See “systemctl status hostapd.service” and “journalctl -xe” for details.
Created symlink /etc/systemd/system/hostapd.service → /dev/null.
Setting up libpcap0.8:armhf (1.8.1-6) …
Setting up libgpg-error-dev (1.35-1) …
Setting up docker-ce (5:19.03.9~3-0~raspbian-buster) …
Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xe” for details.
invoke-rc.d: initscript docker, action “start” failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-05-26 11:40:15 BST; 24ms ago
Docs: https://docs.docker.com
Process: 15438 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 15438 (code=exited, status=1/FAILURE)
dpkg: error processing package docker-ce (–configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

Setting up docker-ce (5:19.03.9~3-0~raspbian-buster) …
Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xe” for details.
invoke-rc.d: initscript docker, action “start” failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-05-26 11:40:53 BST; 24ms ago
Docs: https://docs.docker.com
Process: 17425 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 17425 (code=exited, status=1/FAILURE)
dpkg: error processing package docker-ce (–configure):
installed docker-ce package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

Setting up docker-ce (5:19.03.9~3-0~raspbian-buster) …
Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xe” for details.
invoke-rc.d: initscript docker, action “start” failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-05-26 11:45:25 BST; 24ms ago
Docs: https://docs.docker.com
Process: 19376 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 19376 (code=exited, status=1/FAILURE)
dpkg: error processing package docker-ce (–configure):
installed docker-ce package post-installation script subprocess returned error exit status 1

Processing triggers for dbus (1.12.16-1) …
Errors were encountered while processing:
docker-ce
E:Sub-process /usr/bin/dpkg returned an error code (1)
Error during install: 'installArchives() failed’cp: cannot stat ‘/usr/local/share/kweb/ktop’: No such file or directory
sudo: kwebhelper_set.py: command not found
./debinstall: 9: ./debinstall: preparekweb: not found
disable_splash=1
splash quiet plymouth.ignore-serial-consoles logo.nologo vt.global_cursor_default=0
cp: cannot create regular file ‘/usr/share/plymouth/themes/pix/splash.png’: No such file or directory
Done

Setting up docker-ce (5:19.03.9~3-0~raspbian-buster) …
Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xe” for details.
invoke-rc.d: initscript docker, action “start” failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-05-26 11:46:02 BST; 53ms ago
Docs: https://docs.docker.com
Process: 20552 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 20552 (code=exited, status=1/FAILURE)
dpkg: error processing package docker-ce (–configure):
installed docker-ce package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
Password:
Enter it again:
Building the docker images…
error during connect: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/networks/create: read unix @->/var/run/docker.sock: read: connection reset by peer
ERROR: .FileNotFoundError: [Errno 2] No such file or directory: ‘./docker-compose-dev.yml’
Connection to 192.168.1.78 closed by remote host.
Connection to 192.168.1.78 closed.

I tried to setup the WaziCloud as described at your given url. When I run docker-compose pull I get the message “command not found”.

Can you give me some explanation and help how I setup Wazigate and wazicloud properly?

Thank you!
Christian

If you need it, I can send you the full terminal log output of Wazigate installation.

Hi Christian,

This is not normal during the installation. Try to run it as root or just use the following to run it in sudo:

curl -fsSL https://raw.githubusercontent.com/Waziup/waziup-gateway/master/setup/get_waziup_dev.sh -o docker.sh && sudo sh docker.sh