# Octave edge - debugging aid - using the WP edge device command line

**URL:** <https://forum.sierrawireless.com/t/octave-edge-debugging-aid-using-the-wp-edge-device-command-line/22277>\
**Category:** Octave\
**Created:** [December 1, 2020, 4:43pm UTC](https://forum.sierrawireless.com/t/octave-edge-debugging-aid-using-the-wp-edge-device-command-line/22277 "2020-12-01T16:43:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnofleek](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/johnofleek/32/4726_2.png) [@johnofleek](https://forum.sierrawireless.com/u/johnofleek)\
**Post date:** [December 1, 2020, 4:43pm UTC](https://forum.sierrawireless.com/t/octave-edge-debugging-aid-using-the-wp-edge-device-command-line/22277/1 "2020-12-01T16:43:11Z")

</div>

I have put together a simple Python script which runs in the WP based Octave Edge shell to aid development and debugging JavaScript edge actions.

It works by taking the Legato log and filtering / rearranging so that just edge action debug is output.

I’ve found this useful when working with multiple interacting edge actions.  
It also works when the Edge device is not in developer mode.

Link [https://github.com/johnofleek/Octave/tree/main/edgeDebug](https://github.com/johnofleek/Octave/tree/main/edgeDebug)

Any feedback most welcome