<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Python script to upgrade firmware based on availability in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425358#M4225</link>
    <description>&lt;P&gt;A script would be faster to schedule and easier to explain to users not that versed on the dashboard.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Mar 2026 20:45:23 GMT</pubDate>
    <dc:creator>tjh188</dc:creator>
    <dc:date>2026-03-03T20:45:23Z</dc:date>
    <item>
      <title>Python script to upgrade firmware based on availability</title>
      <link>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425356#M4223</link>
      <description>&lt;P&gt;Has anyone had any luck at writing a script to upgrade Meraki firmware using Python?  If so please share the script without any secret info.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 20:39:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425356#M4223</guid>
      <dc:creator>tjh188</dc:creator>
      <dc:date>2026-03-03T20:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Python script to upgrade firmware based on availability</title>
      <link>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425357#M4224</link>
      <description>&lt;P&gt;Excuse the question, but what's the point of this? Wouldn't it be easier to schedule via the dashboard?&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 20:44:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425357#M4224</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2026-03-03T20:44:08Z</dc:date>
    </item>
    <item>
      <title>Re: Python script to upgrade firmware based on availability</title>
      <link>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425358#M4225</link>
      <description>&lt;P&gt;A script would be faster to schedule and easier to explain to users not that versed on the dashboard.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 20:45:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425358#M4225</guid>
      <dc:creator>tjh188</dc:creator>
      <dc:date>2026-03-03T20:45:23Z</dc:date>
    </item>
    <item>
      <title>Re: Python script to upgrade firmware based on availability</title>
      <link>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425359#M4226</link>
      <description>&lt;P&gt;People with a large number of networks or organizations may want to automate the process.&lt;/P&gt;&lt;P&gt;Check out John’s example here: &lt;A href="https://github.com/meraki/automation-scripts/blob/master/manage_firmware/firmware_upgrade_manager.py" target="_blank" rel="nofollow noopener noreferrer"&gt;https://github.com/meraki/automation-scripts/blob/master/manage_firmware/firmware_upgrade_manager.py&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 20:46:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425359#M4226</guid>
      <dc:creator>obrigg</dc:creator>
      <dc:date>2026-03-03T20:46:02Z</dc:date>
    </item>
    <item>
      <title>Re: Python script to upgrade firmware based on availability</title>
      <link>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425360#M4227</link>
      <description>&lt;P&gt;I have seen that script but all of my networks are in Templates.  I would like to upgrade the templates one by one on a specific date and time.&lt;/P&gt;&lt;P&gt;I don't like the batch effort outlined in that GitHub.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 20:57:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425360#M4227</guid>
      <dc:creator>tjh188</dc:creator>
      <dc:date>2026-03-03T20:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: Python script to upgrade firmware based on availability</title>
      <link>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425361#M4228</link>
      <description>&lt;P&gt;This is probably a good use case for using automation workflows.  Because, well, it is part of your standard workflow.&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/Platform_Management/Workflows" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/Platform_Management/Workflows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.png" style="width: 400px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/264659iF6BE0C6BF4603C5B/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2026 18:07:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/python-script-to-upgrade-firmware-based-on-availability/m-p/5425361#M4228</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2026-03-04T18:07:11Z</dc:date>
    </item>
  </channel>
</rss>

