SLZB-06 Firmware Update 20240710 Error - SOLVED

Hi All

Im running HA on dedicated DELL mini PC and im using the SLZB-06 coordinator for Z2M, all good, no issue apart from for some reason the date and time are wrong but not a issue really, Anyway, ive just gone to the control panel for the coordinator and when i go to the Firmware Update section and try to update from 20240315 to the 20240710 i get this error, any ideas on whats causing this?

have you updated the ESP side firmware 1st ?, latest zigbee firmware requires ESP firmware version v2.2.0 or higher.

Hi, how do i check/do that, im still a noob sorry, i dont have any ESPHome stuff?

Its all good now, was just my gateway was wrong

you do it in the web page of the device

update the CORE (ESP), then you can update the Zigbee firmware.

Having the same problem, what do you mean by “the wrong gateway”?

Thank you!

Hey! I’m having the same issue as the original user. I was able to update previously, but I’m stuck on core firmware version: v2.6.8.dev25 and Zigbee revision: 20241127. Zigbee is the most up to date version, but the core is a few updates behind, and I can’t seem to get it to update. I tried seeing what “wrong gateway” meant too but the gateway settings I have on my device match what I have on my router settings so not sure what to do next lol. I tried manually flashing it via web browser method but I couldn’t get it to connect to my PC for whatever reason.

This is what chatgpt told me to do for my gateway checks/amends that worked for me.

To check or modify the settings of your SLZB-06 coordinator, you can use its web interface. Here’s how:

  1. Access the Web Interface:
  • Connect the SLZB-06 to your local network.
  • On a device connected to the same network, open a web browser.
  • Enter the device’s IP address into the browser’s address bar. If you’re unsure of the IP address, the SLZB-06 supports mDNS, allowing you to access it via http://slzb-06.local (ensure your router supports mDNS).

SMLight
2. Navigate the Interface:

  • Once the interface loads, you’ll see several sections:
    • Dashboard: Displays the current status of the device.
    • Mode: Allows you to set the device’s operation mode (e.g., Zigbee-to-Ethernet, Zigbee-to-USB).
    • Network: Configure Ethernet and Wi-Fi settings, including DHCP and IP configurations.
    • Zigbee2MQTT and ZHA: Set up access via the serial interface and perform Zigbee channel scans (available on SLZB-06M series).
    • Security: Manage security parameters, such as login credentials and web interface access.
    • Firmware Update: Check for and apply firmware updates.
    • General Settings: Adjust system settings, including LED behavior and system logs.
  1. Modify Settings:
  • To change the device’s operation mode:
    • Go to the Mode section.
    • Select your desired mode from the available options.
    • Save your changes; the device may reboot to apply the new settings.
  • To update network settings:
    • Navigate to the Network section.
    • Adjust settings like IP address, subnet mask, gateway, and DNS as needed.
    • Save your changes to apply them.

For a visual walkthrough and more detailed guidance, consider watching the following video:

This video provides an in-depth look at configuring and managing the SLZB-06 coordinator.

If you encounter issues or need further assistance, refer to the official SLZB-06 manual or reach out to SMLIGHT support.

If this doesnt work if you go to the you SLZB dashboard you can ask them in there for any help and they are really good.

Good Luck

Hi Carl, you already changed the topic title to indicate that your problem has been solved. :+1:
Please take the time to mark the post with the solution as the answer, you do that by selecting the three dots under the post:

image

Then select the check box:

image
By doing so this can be useful to other users as well (this thread comes up as solution when staring a related thread).

1 Like

Just in case someone ends up here using a google search. The solution is to disable DHCP and manually enter the IP/Default Gateway on your SLZB network page. Thats what fixed it for me.