mercenaruss / uzg-firmware

Firmware for ZigStar UZG-01
GNU General Public License v3.0
74 stars 11 forks source link

V0.2.6 on CC2652P7 #36

Open NightHawkATL opened 7 months ago

NightHawkATL commented 7 months ago

I have finally updated to the "latest" version and I am still seeing daily disconnects with my Home Assistant setup.

I have tried:

Is there anything that can be done to make this more stable or should I just move to a competitor device? This has only happened in the last month or so and was rock solid before that.

xpenno255 commented 7 months ago

I'm also having issues that sounds similar to this. For me it happens every 2 to 3 days.

I'm using ZHA in Home Assistant OS 2024.04.2 I was previously running Skyconnect via USB but I migrated to UZG-01 in ethernet mode and updated directly to v0.2.6.

At the time the following error appears in home assistant.

`Logger: zigpy.application Source: /usr/local/lib/python3.12/site-packages/zigpy/application.py:675 First occurred: 20:24:14 (1 occurrences) Last logged: 20:24:14

Watchdog failure Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/zigpy_znp/api.py", line 1059, in request response = await response_future ^^^^^^^^^^^^^^^^^^^^^ asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/zigpy/application.py", line 673, in _watchdog_loop await self.watchdog_feed() File "/usr/local/lib/python3.12/site-packages/zigpy/application.py", line 655, in watchdog_feed await self._watchdog_feed() File "/usr/local/lib/python3.12/site-packages/zigpy_znp/zigbee/application.py", line 628, in _watchdog_feed await self._znp.request(c.SYS.Ping.Req()) File "/usr/local/lib/python3.12/site-packages/zigpy_znp/api.py", line 1055, in request async with async_timeout.timeout( File "/usr/local/lib/python3.12/site-packages/async_timeout/init.py", line 141, in aexit self._do_exit(exc_type) File "/usr/local/lib/python3.12/site-packages/async_timeout/init.py", line 228, in _do_exit raise asyncio.TimeoutError TimeoutError`

NightHawkATL commented 7 months ago

@xpenno255 i just recently added the MQTT server connection to add functions to monitor it in HA. I have an automation that watches the state of ZHA and if it goes to unavailable or unresponsive, it sends a message and then triggered the zigbee reboot of the UZG-01. Once it comes back up, it sends another message letting me know it may be working again.

Trying this for a minute to see if it helps.

tavalin commented 7 months ago

Can you share your automation or a link to it please? I'm having similar issue

NightHawkATL commented 7 months ago

Can you share your automation or a link to it please? I'm having similar issue

alias: "Notify: Zigbee Control Down"
description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.texas_instruments_coordinator
    from: null
    to: unavailable
condition:
  - type: is_not_connected
    condition: device
    device_id: aeb436d05cd0bbf44cac48c2043ce89c
    entity_id: de5d3f881a20242a52e9f54da7b74635
    domain: binary_sensor
action:
  - service: notify.mobile_iphone_13
    metadata: {}
    data:
      message: >-
        The Zigbee coordinator has gone unresponsive. The zigbee radio has been
        restarted and should become responsive shortly.
      title: Notice!
  - device_id: aeb436d05cd0bbf44cac48c2043ce89c
    domain: button
    entity_id: 3affbf71bed59a894f70b0c1c110753b
    type: press
mode: single
NightHawkATL commented 7 months ago

Screenshot 2024-04-10 7 01 54 PM Screenshot 2024-04-10 7 00 05 PM Screenshot 2024-04-10 7 01 13 PM

xyzroe commented 7 months ago

https://github.com/mercenaruss/uzg-firmware/issues/7

xyzroe commented 7 months ago

It's some problem with CC2652 firmware. You could find more information https://github.com/Koenkk/Z-Stack-firmware/discussions/496

NightHawkATL commented 7 months ago

It's some problem with CC2652 firmware. You could find more information https://github.com/Koenkk/Z-Stack-firmware/discussions/496

There's no clear fix on that site. It is just a lot of trial and error so far. I have my automation in place until they can come up with a fix.

xpenno255 commented 7 months ago

Screenshot 2024-04-10 7 01 54 PM Screenshot 2024-04-10 7 00 05 PM Screenshot 2024-04-10 7 01 13 PM

This looks great, I'm currently using ethernet mode to connect my UZG-01 so I'm not sure if it appears as entity in home assistant, I can't seem to find it at least....

xyzroe commented 7 months ago

we don't see your images 😞

NightHawkATL commented 7 months ago

I downloaded the files linked at the top labeled 20240315 and extracted them and installed it on my UZG-01 and I show "20230507" but it is stable as of right now. I have not gotten any more disconnect notices from my automation to monitor it since the update and connections do seem to be faster and more reliable.

NightHawkATL commented 7 months ago

Screenshot 2024-04-10 7 01 54 PM Screenshot 2024-04-10 7 00 05 PM Screenshot 2024-04-10 7 01 13 PM

This looks great, I'm currently using ethernet mode to connect my UZG-01 so I'm not sure if it appears as entity in home assistant, I can't seem to find it at least....

You will need to enable the MQTT connection in the latest ESP32 update to get access to the reset commands. But by default, you can use the ZHA integration to track the status as shown in my screenshots. image image

@xyzroe I think he was linking to my screenshots.

TronTronix commented 7 months ago

Ich versuche bei mir ein updat für CC2652P7 einzuspielen (ZigStarGW-MT) bleibt aber immer stehen mit ("local variable cip referenced before assignment") 1

Mit (SmartRF FP2 - USB) hat es auf jeden Fall funktioniert 4

Aber jetzt habe ich irgendwie wohl eine Dateileiche ("fw.hex") im System wie kann ich die loswerden, löschen ?? 2

xyzroe commented 7 months ago

Ich versuche bei mir ein updat für CC2652P7 einzuspielen (ZigStarGW-MT) bleibt aber immer stehen mit ("local variable cip referenced before assignment") 1

Mit (SmartRF FP2 - USB) hat es auf jeden Fall funktioniert 4

Aber jetzt habe ich irgendwie wohl eine Dateileiche ("fw.hex") im System wie kann ich die loswerden, löschen ?? 2

  1. You need to use latest version of Multitool. You were used old one. Need 0.4.0 at least.
  2. This files appears after trying to install Zigbee update via web UI, which is still in development. There isn't way to remove this file except full erase flash and install clean firmware.

P.S. Please be respectful of other community members, and use the language that everyone uses to communicate in this community.

GD-Dal commented 7 months ago

Having the same issues. And if I enable MQTT, it becomes downright unstable. Not able to connect at all I use PoE to power it. But every time I initiate a reboot from the Zigstar device, the NIC just blinks and never comes online anymore, unti i do a shutdown / no shutdown on the switchport

Not particulary happy right now

mercenaruss commented 7 months ago

@GD-Dal this will be solved,this is not a generic problem,cant find the pattern for this problem,never occurs on my test devices. Please send a email to: support@zig-star.com with details about you data switch.