Andrew Lindsay

Forum Replies Created

Viewing 9 posts - 121 through 129 (of 129 total)
  • Author
    Posts
  • in reply to: LoRa Range problems #8834
    Andrew Lindsay
    Participant

    Thanks Brandon, the Conduit is running 1.0.28 as updated by deviceHQ if that helps.

    I also changed the mDot spreading factor using dot->setTxDataRate( mDot::SF_9 ); but this doesn’t seem to have changed as Node-RED still reports a spreading factor of 7 in the debug window.

    Slimming the payload down is the next job as this is too large at present due to sending gps lat/lon values.

    Regards

    Andrew

    in reply to: Serial Port #8831
    Andrew Lindsay
    Participant

    Finally tried this, watched the logs and saw the USB device was detected and which port it was allocated too. Next thing, using the Serial In node in Node-RED allowed me to capture received data.

    Thanks

    Andrew

    in reply to: Registering device on DeviceHQ #8757
    Andrew Lindsay
    Participant

    Hi David,

    Ethernet is connected as this is how I’m connecting to it and Node-Red on the conduit. I’ve updated the config to change Ethernet from LAN to WAN and now the static option includes gateway and dns server IP addresses. I did also try DHCP but this failed to get the DNS server and gateway IP addresses too.

    I checked DeviceHQ and its checked in!

    The conduit is currently running firmware 1.0.25-Beta, so selecting the scheduled firmware update would take it to 1.0.28 on next checkin.

    Thanks for your help on this. Much appreciated. Now to get the mDots doing something useful.

    Andrew

    in reply to: Registering device on DeviceHQ #8754
    Andrew Lindsay
    Participant

    Hi David,

    SSL is enabled in remote server option. I also see the current status is now:

    Current Status failed to open connection with mdm

    Server name is ds-beta.devicehq.com, the app store and dependency URLs are both https://beta.devicehq.com

    The only option not set is the Sync with Dial on Demand as I’ve not yet installed a SIM.

    Thanks

    Andrew

    in reply to: Registering device on DeviceHQ #8749
    Andrew Lindsay
    Participant

    Hi,

    Next point, I’m not seeing the conduit as having checked in but from the logs I am seeing this, so wondering if it’s failing to phone home:

    Jul 27 19:58:53 mtcdt daemon.info annexcd: [INFO] courier.cc:Open:1394: opening connection with ds-beta.devicehq.com:5798
    Jul 27 19:58:53 mtcdt daemon.err annexcd: [ERR] courier.cc:Open:1408: gethostbyname_r: 2
    Jul 27 19:58:53 mtcdt daemon.err annexcd: [ERR] courier.cc:RunnableCore:1211: Open failed

    I’ve not changed any of the URLs in the config, I added the account key that was received in the sign up email for the beta site so it should, in theory be checking in.

    Is there anything else I should be looking at?

    Thanks

    Andrew

    in reply to: Registering device on DeviceHQ #8714
    Andrew Lindsay
    Participant

    Aha! that was it. Now registered on the beta site so need to see if the Conduit checks in.

    thanks for your help

    Andrew

    in reply to: Registering device on DeviceHQ #8709
    Andrew Lindsay
    Participant

    Hi David,

    https://www.devicehq.com/ which is the only one I could find, seems its not linked on your website.

    Thanks

    Andrew

    in reply to: Registering device on DeviceHQ #8706
    Andrew Lindsay
    Participant

    Hi,

    I emailed the uuid but have not heard anything back. I’ve tried to register the device thinking it might have been done but still not found.

    thanks

    Andrew

    in reply to: Registering device on DeviceHQ #8703
    Andrew Lindsay
    Participant

    Thanks Jeff, email sent.

    Andrew

Viewing 9 posts - 121 through 129 (of 129 total)