I’m posting news in Telegram News Channel: Telegram: Contact @zigstar
Thank you, you help a lot.
Can you tell me when and where I will be able to order the Olizig PoE coordinator with the box?
Great job, thanks for your help.
@mercenaruss
I see that the Olizig PoE coordinator can be ordered again.
Unfortunately, I can’t 3D print a box, but it would be very important to me. You promised that there would be a solution to this soon. I would like to ask if I can now order an Olizig PoE coordinator together with a box?
Thanks for your help.
Good day. My lan coordinator has been working well for a year.
Yesterday I decided to upgrade the firmware to latest zstack (Dec 2022).
Used your upgrade tool and completed successfully.
Now the network is just very slow. Some devices freeze, others lag considerably.
Any guidance suggestions are much appreciated. What is the recommended baud rate? It’s currently 115200
Edit: a day later (feb 14) I decided to revert to the previously working zstack (Dec 2021) and it all went back to normal. Cant tell what the issue is, but my Lan coordiantor did not like the latest zstack
1 Like
What’s the procedure to flash the firmware without losing the ZigBee network? Using ZHA here.
Sorry not using zha, im on z2mqtt.
However, a plain firmware upgrade on same coordinator should retain the network as is.
I’d suggest looking at zha documenatation. I’ve also seen a hacs network tool for zha.
Yeah,i still didnt test on my setup last firmware.
But many users complained about it.
Will find time and test.
Just stop ZHA,upgrade firmware,start ZHA.
This is all.
I upgraded the firmware using cc2538-bsl.py from the GitHub - JelmerT/cc2538-bsl: Python cross-platform script to upload firmware via the serial boot loader onto the CC13xx, CC2538 and CC26xx SoC. and when I did so, it erased my firmware flash data. Home Assistant, thankfully for me, restored my ZigBee network.
I repeat the question. How do I flash (on Linux, obviously) without losing the coordinator’s data?
I’m struggling to get this working with docker-compose.
For the docker-compose.yaml:
zigbee2mqtt:
container_name: zigbee2mqtt
restart: unless-stopped
image: koenkk/zigbee2mqtt
volumes:
- /opt/zigbee2mqtt/data:/app/data
- /opt/zigbee2mqtt/udev:/run/udev:ro
network_mode: host
environment:
- TZ=$TZ
For the z2m configuration.yaml:
homeassistant: true
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: mqtt://192.168.100.10:1883
user: mqtt-username
password: mqtt-password
serial:
port: 'tcp://192.168.100.11:6638'
advanced:
homeassistant_legacy_entity_attributes: false
legacy_api: false
device_options:
legacy: false
frontend:
port: 8099
host: 192.168.100.235
devices:
- devices.yaml
groups:
- groups.yaml
When I run docker-comose up -d and I check the logs for the z2m container in Portainer:
Zigbee2MQTT:info 2023-03-13 09:08:08: Starting Zigbee2MQTT version 1.30.2 (commit #cdf62ea)
Zigbee2MQTT:info 2023-03-13 09:08:08: Starting zigbee-herdsman (0.14.96)
Zigbee2MQTT:error 2023-03-13 09:08:28: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-03-13 09:08:28: Failed to start zigbee
Zigbee2MQTT:error 2023-03-13 09:08:28: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-03-13 09:08:28: Exiting...
Zigbee2MQTT:error 2023-03-13 09:08:28: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:58:27)
at Controller.start (/app/lib/controller.ts:101:27)
at start (/app/index.js:107:5)
You need to backup NVRAM just in case, but you dont loose any data during flashing.
First of all check your device is reachabe by web interface and that zigbee firmware is flashed.
If you need support just drop an email to [email protected] or chat me in telegram Telegram: Contact @zig_starting
New Web Installer now is up and running.
Will help you to install all ZigStar Firmwares directly from your browser without downloading any software.
For ESPHOME firmware we prepared correct firmware for web flashing.
- STANDART ZIGSTAR FIRMWARE
- Zigbee - ESPHome Firmware with ZigBee on board
- BT-Proxy - ESPHome Firmware with BT-Proxy functionality on board
- Mixed - ESPHome Firmware with ZigBee and BT-Proxy on board. May cause interference,use at your own risk.
Currently all documentation is possible to edit directly from your browser, feel free to edit and submit pull request on Github.
2 Likes
I don’t get it. Does this mean I can install ESPHome on one of your devices, and this will also give me a ZigBee router running in it? I didn’t see anything of the sort in the YAML files.
Okay,
each LAN Capable device is based on ESP32,so you have a choice to install our own developed FW or the ESPHome FW, that is used for connection between LAN and Zigbee what is present on device.
What firmware you will install on Zigbee is depending on your needs but devices was mostly designed for Coordinator mode in mind.
1 Like
not sure if is the right spot to post. but i am tryiong to install a zigstar lan gatey i purchased from tindie. It does not work. i also try a fresh install of home assistant. The gateway is link by ethernet.
This is the log:
Logger: aiohttp.server
Source: components/zha/radio_manager.py:224
First occurred: 13:48:10 (1 occurrences)
Last logged: 13:48:10
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 1058, in request_callback_rsp
return await callback_rsp
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 253, in start_network
commissioning_rsp = await self.request_callback_rsp(
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 1055, in request_callback_rsp
async with async_timeout.timeout(timeout):
File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 129, in __aexit__
self._do_exit(exc_type)
File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 212, in _do_exit
raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 180, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper
result = await method(view, request, data, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 267, in async_configure
result = await self._async_handle_step(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 370, in async_step_form_initial_network
return await self.async_step_form_new_network(user_input)
File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 376, in async_step_form_new_network
await self._radio_mgr.async_form_network()
File "/usr/src/homeassistant/homeassistant/components/zha/radio_manager.py", line 224, in async_form_network
await app.form_network()
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 333, in form_network
await self.form_network(fast=True)
File "/usr/local/lib/python3.10/contextlib.py", line 217, in __aexit__
await self.gen.athrow(typ, value, traceback)
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 875, in capture_responses
yield queue
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 291, in start_network
raise zigpy.exceptions.FormationFailure(
zigpy.exceptions.FormationFailure: Network formation refused: there is too much RF interference. Make sure your coordinator is on a USB 2.0 extension cable and away from any sources of interference, like USB 3.0 ports, SSDs, 2.4GHz routers, motherboards, etc.
any ideas?
1 Like
This is the correct spot.
Remove antenna and try again.
After will form the network attach antenna back.
it did the tricks thanks
@mercenaruss My zigstar lan is no longer working after sending it a Restart Zigbee command using the multitool. The lights go on but I can’t connect to it using z2m or the web interface or ZHA anymore.
I tried both the multi tool and the python library to flash the latest CC1352P2_CC2652P_launchpad_coordinator_20230507 firmware, but both methods are giving me the same error:
ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'
I am trying to boot it into BSL mode thinking that might be the problem, but pressing the BSL button while booting makes no difference.