• Categories
    • Recent
    • Tags
    • Popular
    • Register
    • Login
    1. Home
    2. rayven
    3. Topics
    R
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 12
    • Groups 0

    Topics

    • R

      JavaScript evaluation question.

      Watching Ignoring Scheduled Pinned Locked Moved General Discussion
      3
      0 Votes
      3 Posts
      76 Views
      R
      @jkandasa I appreciate it.
    • R

      Trouble migrating from executable to docker image.

      Watching Ignoring Scheduled Pinned Locked Moved General Discussion
      4
      0 Votes
      4 Posts
      199 Views
      jkandasaJ
      Are the mycontroller.yaml setting the same for the binary and the docker container? Yes, same file/schema used on binary as well as for container. @rayven you have to point to your influx db location, docker container always runs on it's own network space, if you specified http://localhost:8086, it tries inside container. Put your host ip address on it. also enable the metric database. installation with docker container: https://mycontroller.org/docs/installation/quick-installation/docker-container/ install influx database: https://mycontroller.org/docs/getting-started/install-influxdb/ backend configurations: https://mycontroller.org/docs/installation/advanced-installation/backend-configuration/
    • R

      Is their an option to enable ack for messages the gateway originates?

      Watching Ignoring Scheduled Pinned Locked Moved General Discussion
      13
      0 Votes
      13 Posts
      6k Views
      R
      it may be a more universal solution for the node/switch to use the request(uint8_t childSensorId, uint8_t variableType) function and resend the command to the node/relayActuator after a timeout. This is what @jkandasa mentioned in his post earlier. Still if the node/switch receives the request() it does not know what sensor sent it. If this was contained in the message variable we could implement a fairly robust solution to this.