I couldn’t figure out how to do outboard webhooks on their site. There was a cryptic message to call sales, so I did. I also saw a video that showed someone with an outboand tab I was missing.

I talked to Domanic in sales just now, and he confirmed, unless I am a serious commercial customer looking to pay $1000 mo., outbound webhooks are disabled.

The best decsion might be to get the Nordic DK with the iBasis SIM for their cloud solution. I will talk to them first. Maybe I can get an iBasis SIM for the feather.

In general Hologram provides the connectivity only. You should spin your own server or use a service like Golioth to help generate webhook events to your servers.

    Do you know of tutorials or resources for spinning your own server? Is Goliath relatively inexpensive?

      If you’re comfortable with HTTP you could create your own HTTP endpoints. You can check out the HTTPS sample for more info on how to use it.

      I’m not sure about the costs for Golioth but I know it’s reasonable. Sorry I don’t have much more info on that.

        Not sure, what you are exactly searching for. I’m one developer of the Eclipse Open Source projects Californium (CoAP/DTLS 1.2 CID server in java) and tinydtls (DTLS 1.2, device C-library, client-side CID). In order to have a “e2e” integrated setup, I started a couple of demo projects:

        Zephyr - coaps-client using tinydtls
        Californium, cf-cloud-demo-server
        Californium, cf-s3-proxy-server

        This device client is in the meantime pretty reliable. In rare cases the watchdog will reset it, but usually it runs for a couple of weeks without such restarts. The power and data consumption is pretty low, a Thingy:91 is able to exchange a message (e.g. 500-800 bytes) every hour for more the 6 months. (OK, that depends a lot on the radio situation where you want to run it. The short: it takes about 60mC to exchange a message, but easily 2000mC to search for a network.)
        A nRF9160 feather runs from 3xAA 2000mAh LSD batteries up to 2 years.
        The Californium demo server comes in two variants, the simple one with java callbacks for those who want to implement their own server logic, e.g. feed the data into messaging systems. And the CoAP-S3-proxy, which comes with a own simple SinglePageApplication javascript. The proxy “straight forwards” the messages to a S3 service, which is used to persist the data. it is able to inject the “timestamp” and enables to keep time-series. The javascript SPA uses a integrated http-login-server to fetch the temporary S3 signing keys. And then it fetchs all data from S3.

        See Virtual IoT & Edge Days - Day 2., DTLS-CID Meets Zephyr, at 2:45

        CoAP and DTLS 1.2, DTLS 1.2 CID are all IETF standards, so it’s possible to exchange components supporting the same standards. e.g. you may enable DTLS 1.2 CID support on the nRF9160 modem, or use Golioth as CoAP/DTLS 1.2 CID server alternative to Californium. IoTerop offers also a CoAP/DTLS 1.2 CID server endpoint.
        What’s not standardized on the CoAP level is the API the server offers. If you’re looking also for standards there LwM2M may be a choice. There you may find a couple of server, e.g. IoTerop, AVSystem, or Friendly Technologies. Or as open source, Eclipse/Leshan.

          14 days later
          Terms and Conditions | Privacy Policy