In reply to Patrick.

Patrick, 1. Usage of an accelerometer to trigger location updates is a viable scenario. It conserves power in that the device/sensor does not need to unnecessarily wake up and transmit to the gateway when there is no movement. Under which conditions the location updates are suspended in this scenario is implementer's choice; the LoRaWAN specification does not prescribe this. A common implementation might be based on accelerometer value plus timer expiration. 2. For a simple endpoint implementation, yes - but there are of course tradeoffs. If the endpoint only needs to sense and report to the gateway but not natively compute, it will translate into endpoint BOM cost and power conservation benefits. On the other hand you may be transmitting more than you need to (what you referred to as "false positives"), so the main tradeoff is that the wireless medium is not optimally utilized. An alternative implementation might allow the application (through the network server and the gateway) to convey back to the endpoint what its estimated location (or location differential) is. 3. Practically speaking, since LoRaWAN is a low rate technology you might be constrained by the spreading factor (SF). At the lowest bit rate (SF12) a single packet of maximum payload size will be on the air for 1,400 msec, versus only 28 msec for the highest bit rate (SF7); you will probably recognize this is similar to Wi-Fi and other communication systems that support a fairly wide range of physical layer rates. 4. No, LoRaWAN is based on star topology.