Hej!
Är det mycket konfigurationer behöver göras om man har redan en Linux-maskin eller en standard Rasbian OS? förutom att flytta scripts som finns under /etc/iot-open och iotopen-verify. Som jag förstår att tanken från det hela att omvandla en Raspberry Pi till en gateway som styrs från IoTOpen plattfrom.

unvacs
Det splelar ingen roll för detta om det finns en Z-wave dongle eller inte.

    2 months later

    We got the following error message when we executed iotopen-verify
    https://ibb.co/BBtwFBS
    The edge client joined successfully. The warning does not affect the joining.

      Devices which became included to gateway does not appear in Lynx Portal.
      Both service zwaved and mosquitto run without problem.
      Man can see the communication in MQTT Realtime windows without problem.
      You can t.ex. check the following installation:
      Organization nr: 2494
      Installtion id: 445

        unvacs
        The reason for the locale warnings (the are just warnings) is that the corresponding locales is not installed on the gateway. The following installs them.
        sudo apt-get install locales
        And then configure them ti includes the ones that are missing
        sudo dpkg-reconfigure locales
        In the long list mark the ones that are missing e.g. sv_SE.UTF-8. When you log in via ssh you get the same language as the machine you are loging in from. If it doesn't exist the warning is shown.

          unvacs

          Including devices again should also add them in the portal.
          There was an issue with the back-end manager.

            What is back-end manager? and what is caused the problem?

            The back-end manager is the component handling the Z-wave functions in this case. There are another one for e.g. LoRa.
            We had a glitch in it when you tried. The only thing that did not work was inclusion and exclusion so it was not noticeable for most users.

            And what is "a glitch"? Is it a missing connectivity to hosting server or något software relaterad issue?

            It looks to be some software related issue with the component on the back-end. One of our developers is looking into the bug, I am sure the software might get some update in the future.

              I have marked that when ping traffic is blocked by the firewall, The gateway could not be able to connect to the Lyxn IoT Open server. Are there other traffics that should be allowed in the firewall?

              Jesper And does this back-end in this case called zwave-manager?

                The gateway needs to be able to connect to the backend on ports 443 and 8883. It also of course needs to be able to lookup hostnames via DNS.