SLZB-06M can't leave access point mode

[jusicgn]

Hi folks,

I heard about this wonderful project and wanted to switch with my SLZB-06M to XZG.
Before flashing XZG I was on v2.2.8.dev from smlight.
I always use the device connected via wired ethernet and also powered over ethernet.

For flashing to XZG I used a USB cable of course.
After a few attempts the webflasher finally startet flashing and said successfull in the end.

First I thought it should obtain a IP-address via ethernet and DHCP but it didn't.
Then I found the XZG WiFi access point and connected to it.

Loved the UI but couldn't change to use the wired ethernet connection at all.
Every time I changed the config and triggered the reboot it came up with the access point again.
No connection via wired ethernet possible.
Neither by fixed ip (which is my default) or DHCP.

I the tried to put it in my own WiFi network first but also had no luck in changing to ethernet connection.
Even with the ethernet cable plugged in it always showed the wired ethernet connection "red" in upper right corner.

As I didn't had more time today to struggle with this, I flashed back to v2.2.8.dev from smlight to have my zigbee running again.

Thought, I write you guys here and maybe you an idea for me :)
Maybe I did something wrong or there really is an issue with wired ethernet connection and SLZB-06M.
Would love to give it another try if you guide me the right direction.

Thx
Julian

[xyzroe]

Please provide screenshots and info as described in the issue example.
Then we can try to help you

[jusicgn]

@xyzroe ,
sorry for missing that in my last post.
I already had flashed back to stock fw as I needed my zigbee network to come up again.

Today I managed to give it another shot.

Here are the screenshots and the other information you asked for.

What I found is, that I could establish a connection to my network via WiFi but not via wired ethernet.
In XZG the ethernet symbol in the top right corner is always red.
With the stock fw the ethernet port works like a charm.

So for me it looks like the ethernet port is not fired up correctly even though the LEDs on the port are blinking.
As you can see in the screenshot, it still shows ethernet as disconnected even though it IS connected and configured.
Using DHCP or not also makes no difference.

Best,
Julian

Device information
/
/{
"network-config": {
"wifiEnbl": false,
"wifiSsid": "bluevis",
"wifiPass": "PASS",
"wifiDhcp": true,
"wifiIp": "::",
"wifiMask": "255.255.255.0",
"wifiGate": "::",
"wifiDns1": "1.1.1.1",
"wifiDns2": "8.8.8.8",
"ethEnbl": true,
"ethDhcp": true,
"ethIp": "10.0.18.230",
"ethMask": "255.255.255.0",
"ethGate": "10.0.18.1",
"ethDns1": "10.0.18.2",
"ethDns2": "10.0.18.2"
},
"vpn-config": {
"wgEnable": false,
"wgLocalIP": "::",
"wgLocalSubnet": "255.255.255.0",
"wgLocalPort": 33333,
"wgLocalGateway": "0.0.0.0",
"wgLocalPrivKey": "",
"wgEndAddr": "",
"wgEndPubKey": "",
"wgEndPort": 0,
"wgAllowedIP": "0.0.0.0",
"wgAllowedMask": "0.0.0.0",
"wgMakeDefault": true,
"wgPreSharedKey": "",
"hnEnable": false,
"hnJoinCode": "",
"hnHostName": "XZG-0353",
"hnDashUrl": "default"
},
"mqtt-config": {
"enable": false,
"server": "",
"port": 1883,
"user": "",
"pass": "",
"topic": "XZG-0353",
"updateInt": 60,
"discovery": true,
"reconnectInt": 15
},
"system-config": {
"disableWeb": false,
"webAuth": false,
"webUser": "",
"webPass": "",
"fwEnabled": false,
"fwIp": "0.0.0.0",
"serialSpeed": 230400,
"socketPort": 6638,
"tempOffset": 12,
"disableLedUSB": false,
"disableLedPwr": false,
"refreshLogs": 1,
"hostname": "XZG",
"timeZone": "Europe/Berlin",
"ntpServ1": "pool.ntp.org",
"ntpServ2": "time.google.com",
"nightMode": false,
"startHour": "23:00",
"endHour": "07:00",
"workMode": 1
}
}

[xyzroe]

First screenshot shows that XZG didn't detect board correctly. We need more tests for this board. Could I ask you to be the main tester ? 🥇 I'll made some test build and you need to test them.

[jusicgn]

Sure. Could try them out on the weekend. Need daylight for this as in the evening I need my light switches working ;)

[xyzroe]

Do you have a pinout of SLZB-06M ? As I understand SLZB-06M and SLZB-06 have different pinouts

[jusicgn]

Sorry, I just bought it online and have nothing more than the online sources from smlight.
Have you had a look at https://smlight.tech/product/slzb-06m/ if the information there is helpful for you?
There is also a comparison table between their models and the chips on them.

[xyzroe]

I need pinout

[jusicgn]

So where to get it?

[xyzroe]

Maybe from seller, or manufacturer?

[jusicgn]

I did a little research regarding the different slzb-06* models from smlight.
Hope the additional information helps.
Have a look.

Here https://smartlight.me/smart-home-devices/zigbee-devices/slzb-06m-zigbee-adapter
Is a comparison table.

From my understanding the "only" difference between their slzb-06* models is the (zigbee) radio chip used.
All other specs seem to be identical.

Main specs

• ESP32 Main Control Chip (my slzb-06m shows ESP32-D0WD-V3 as core with the stock firmware)
• CP2102 USB/UART Controller
• LAN8720 Ethernet SoC

different radio chips:

• slzb-06m (which I have) has EFR32MG21
• slzb-06 has CC2652P
• SLZB-06p7 has CC2652P7
• SLZB-06p10 has CC2674P10

[xyzroe]

Man, it's OK, but we need PINOUT

[xyzroe]

your link contains a lot of marketing, but no useful technical information. with the exception of TI links, but we don’t need it now, thank you. please provide the gateway pinout and I will add support for it.

[xyzroe]

Like this one https://github.com/mercenaruss/zigstar_gateways/blob/00ddb35e4cfd36ea69d3b93201f4a99546fab4e2/files/ESP-HOME/zigstar-uzg-01/uzg01-mixed.yaml#L31C1-L37C20
https://github.com/mercenaruss/zigstar_gateways/blob/00ddb35e4cfd36ea69d3b93201f4a99546fab4e2/files/ESP-HOME/zigstar-uzg-01/uzg01-mixed.yaml#L128C1-L144C19
https://github.com/mercenaruss/zigstar_gateways/blob/00ddb35e4cfd36ea69d3b93201f4a99546fab4e2/files/ESP-HOME/zigstar-uzg-01/uzg01-mixed.yaml#L173C1-L187C20
https://github.com/mercenaruss/zigstar_gateways/blob/00ddb35e4cfd36ea69d3b93201f4a99546fab4e2/files/ESP-HOME/zigstar-uzg-01/uzg01-mixed.yaml#L205C1-L209C20

[xyzroe]

Example for UZG-01

ethernet:
  type: LAN8720
  mdc_pin: 23
  mdio_pin: 18
  clk_mode: GPIO17_OUT
  phy_addr: 0
  power_pin: 05

ZB_RST pin: 16
ZB_BSL pin: 32
ZB_RX pin: 36
ZB_TX pin: 04

BTN pin: 35
LED_1 pin: 12
LED_2 pin: 14

[jusicgn]

Sorry if the previous information wasn't helpful.
As I'm not a developer myself I'm not familiar with things like pinouts and stuff.

Did a little research again and found this
https://github.com/cbriddell/slzb-06-esphome/blob/main/slzb-06-esphome-zigbee.yaml
For me it looks like there might be so of the information needed, at least for the ethernet part...?

[xyzroe]

We already support slzb-06. But you have slzb-06m. And I think pinout is different

[xyzroe]

And also for now only TI based devices supported

[maksii]

Just in case, I have SLZB-06m as my backup device and can help with testing and some tech things.
@xyzroe beside of pinout is there anything else that you need/or may help you?

[maksii]

It looks like they forked this repository and their latest release, which is based on your 20240603, with minor differences, some disabled functionality, renamed endpoints, and a bit of CSS just works as is.

api route changed to api2 and the action that should download configHW file returns logs =)

[xyzroe]

It looks like they forked this repository and their latest release, which is based on your 20240603, with minor differences, some disabled functionality, renamed endpoints, and a bit of CSS just works as is.

api route changed to api2 and the action that should download configHW file returns logs =)

Can you provide a link to what you're talking about?

[xyzroe]

Just in case, I have SLZB-06m as my backup device and can help with testing and some tech things.
@xyzroe beside of pinout is there anything else that you need/or may help you?

First we need to add support of ERF boards

[maksii]

It looks like they forked this repository and their latest release, which is based on your 20240603, with minor differences, some disabled functionality, renamed endpoints, and a bit of CSS just works as is.
api route changed to api2 and the action that should download configHW file returns logs =)

Can you provide a link to what you're talking about?

These are my observations based on the HTML layout, endpoint names, and the overall structure of the web UI + translations don't match newer releases.
Here is the latest bin of the firmware they distribute
Endpopint to check updates returns, that their 2.3.6 has revision 20240603. As per their "changelog," it has the few same entries as releases in this repository.
"Their" API looks the same, like here, just the route has changed. eg /api2?action=0&page=5 and some "important" endpoints disabled or renamed(eg, /api2?action=5&filename=configHw.json will return logs, while /api2?action=4 disabled)

So, either this repository and their work use the same underlying code, and it's just a coincidence, or they're based on this one and have sprouted anything that might help.
Again, just my observations, I'm not trying to accuse anyone, but to me, as a person visiting this repository for the first time, I get the feeling that someone is borrowing code from someone else. And if that's the case, I really hope that maybe their developer can help with a pull request here to provide support to their hardware(I see their names here in the contributors)

[xyzroe]

Full history of all related projects you could find here https://youtu.be/24C8liZYGWY

[xyzroe]

In short, smlight distributes bin files of a closed-source firmware that is based on a project licensed under the GNU General Public License v3.0, which violates the terms of the license. Up to version 0.9.9 the license was respected, but after that it was not. But no one cares 👎

The sequence was something like this
ZiGate - ZigStarGW-FW - slzb-06-firmware - uzg-01-firmware - XZG Firmware