# Updating an emonPi to emonPi\_CM

**URL:** <https://community.openenergymonitor.org/t/updating-an-emonpi-to-emonpi-cm/23446>\
**Category:** emonPi\
**Created:** [16 April 2023 11:10 UTC](https://community.openenergymonitor.org/t/updating-an-emonpi-to-emonpi-cm/23446 "2023-04-16T11:10:43Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![TrystanLea](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/trystanlea/32/31_2.png) [@TrystanLea](https://community.openenergymonitor.org/u/TrystanLea)\
**Post date:** [21 April 2023 14:40 UTC](https://community.openenergymonitor.org/t/updating-an-emonpi-to-emonpi-cm/23446/21 "2023-04-21T14:40:02Z")

</div>

> [@rupert](#):
>
> I just tried updating the scripts, and then tried the firmware update listed as 1.1.4, but still got 1.1.3

I’ve fixed an issue with the firmware update tool, it will now use the remote copy of firmware\_available.json which defines the firmware download URL’s without requiring the local copy of the list to be updated. Though this does require an update to EmonScripts for it to work with the new code.

Can update your EmonScripts repository @rupert via Admin \> Components \> EmonScripts \> Update?

and then after that try updating the emonPi firmware again?

---

_[View the full topic](https://community.openenergymonitor.org/t/updating-an-emonpi-to-emonpi-cm/23446)._