# BC127 - Melody 7.3 POWER command error

**URL:** <https://forum.sierrawireless.com/t/bc127-melody-7-3-power-command-error/26753>\
**Category:** WiFi and Bluetooth Modules\
**Tags:** debug\
**Created:** [April 6, 2022, 4:59pm UTC](https://forum.sierrawireless.com/t/bc127-melody-7-3-power-command-error/26753 "2022-04-06T16:59:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bl1](https://avatars.discourse-cdn.com/v4/letter/b/3be4f8/32.png) [@bl1](https://forum.sierrawireless.com/u/bl1)\
**Post date:** [April 6, 2022, 4:59pm UTC](https://forum.sierrawireless.com/t/bc127-melody-7-3-power-command-error/26753/1 "2022-04-06T16:59:03Z")

</div>

Hi,

We have succesfully used the “POWER ON” / “POWER OFF” command in Melody version 5 and 6.  
The datasheet for Melody 7.3 also contains the command, but when I try to write or read the command I get error 0x0011 and 0x001A respectively.

Could someone point me to where to start looking for a solution?

Best regards and thanks in advance!

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [April 7, 2022, 2:07am UTC](https://forum.sierrawireless.com/t/bc127-melody-7-3-power-command-error/26753/2 "2022-04-07T02:07:07Z")

</div>

I don’t see problem.

```auto
version
Sierra Wireless Copyright 2018
Melody Audio V7.3
Build: 1544637564
        Bluetooth addresses: 20FABB075D2B 7BD5DBD3ACF7
        Profiles: A2DP AVRCP HFP BLE SPP PBAP MAP TWS
        Codecs: SBC
OK
POWER ON
ERROR 0x0011
POWER OFF
OK
POWER ON
OK

```

---

<div class="post-metadata">

**Author:** ![bl1](https://avatars.discourse-cdn.com/v4/letter/b/3be4f8/32.png) [@bl1](https://forum.sierrawireless.com/u/bl1)\
**Post date:** [April 7, 2022, 7:35am UTC](https://forum.sierrawireless.com/t/bc127-melody-7-3-power-command-error/26753/3 "2022-04-07T07:35:01Z")

</div>

Hi jyijyi,

Thanks for your quick reply.  
It looks like you get the same error, and meanwhile I think the error is only sent when the module is already in the state I’m trying to put it in.