[Paul Chilton]

Ok thanks, I’ll give that a go and see if it helps.

[Paul Chilton]

Hi, no I haven’t at the moment. I did look into those settings but couldn’t figure out what to set as the hostname. Is this just any old web server that it can ping or does it need to be running a specific service?

Thanks

[Paul Chilton]

I’m actually seeing different behaviour, for a device that hasn’t joined before that conduit seems to be selecting what it thinks is the closest match to that device and sending the packets out to it instead! Not sure if this is an option that can be turned off or not but is highly annoying…

[Paul Chilton]

Did you figure out if this is possible and how to allow devices to roam between conduits?

[Paul Chilton]

Hi, did you ever find or create an Eagle library for the mdot?

[Paul Chilton]

So, I’ve setup a function block being fed from the Lora packet received block:`msg.topic = “lora/” + msg.eui + “/clear”
return msg;`

and then pass this to an MQTT send block (broker 127.0.0.1:1883). Also branched off is the Lora TX block.

This seems to now be working, thanks!

• This reply was modified 8 years, 6 months ago by Paul Chilton.

[Paul Chilton]

Ah, I see, send a message out to MQTT! I’ll give that a try…

[Paul Chilton]

Thanks for the reply, how do I call the MQTT clear from an AEP NodeRED application?

[Paul Chilton]

Hi,

Was this ever solved, I’m having what I think to be the same issues using mdot and AEP conduit. (http://www.multitech.net/developer/forums/topic/mdot-and-aep-reply-lag-or-offset/#post-14788)

Thanks,

Paul

• This reply was modified 8 years, 6 months ago by Paul Chilton.

[Paul Chilton]

Appears to be maybe a duplicate of http://www.multitech.net/developer/forums/topic/lora-network-server-tx-queue-can-it-be-flushed/ that was never answered in full.

[Author]

Posts