Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Procedure to return su MI HOME mode for zigbee (SUPPORT) #1449

Open
maury77 opened this issue Sep 7, 2024 · 14 comments
Open

Procedure to return su MI HOME mode for zigbee (SUPPORT) #1449

maury77 opened this issue Sep 7, 2024 · 14 comments
Labels
question Further information is requested

Comments

@maury77
Copy link

maury77 commented Sep 7, 2024

in the system I dont' find the tool tu return da ZHA Mode a MI mode

can you help me?

thanks

@maury77 maury77 changed the title Procedure to return su MI HOME MODE ZIGBEE (SUPPORT) Procedure to return su MI HOME mode for zigbee (SUPPORT) Sep 7, 2024
@AlexxIT AlexxIT added the question Further information is requested label Sep 7, 2024
@AlexxIT
Copy link
Owner

AlexxIT commented Sep 7, 2024

Reset gateway to default settings.

@maury77
Copy link
Author

maury77 commented Sep 7, 2024

I reset device with the frontal button , but the zha mode is on

its's possiblle?

@AlexxIT
Copy link
Owner

AlexxIT commented Sep 7, 2024

Probably because you didn't turn off the ZHA integration

@maury77
Copy link
Author

maury77 commented Sep 7, 2024

I try this sequence

  • remove ZHA integration
  • reset device
  • configuration with xiaomi app

the firmware instaled is your custom firmware

======================================================
FIRMWARE........: 1.5.6_0001 #20231031
IP..............: 192.168.0.121
MAC.............: 5xxxxx
TOKEN...........: xxxxxx
DID.............: xxxxxx
KEY.............: xxxxxx

but the device zigbee don't connect in paring mode

@maury77
Copy link
Author

maury77 commented Sep 7, 2024

in the console I can view this process

10177 admin 587m S /data/openmiio_agent miio mqtt cache central z3 --zigbee.tcp=8888

@AlexxIT
Copy link
Owner

AlexxIT commented Sep 7, 2024

If you change firmware for zigbee chip, you should change it back. Check docs about custom zigbee firmware.

@maury77
Copy link
Author

maury77 commented Sep 8, 2024

mmmm I don't remember the chagne of the firmare..

Can you help me? Where is the procedure to restore ?

thanks

@AlexxIT
Copy link
Owner

AlexxIT commented Sep 8, 2024

@maury77
Copy link
Author

maury77 commented Sep 8, 2024

I try it

with 3 pass

image

image

but the result is ERROR

image

@AlexxIT
Copy link
Owner

AlexxIT commented Sep 8, 2024

We need to see if there are any details about the error in the debug logs

@maury77
Copy link
Author

maury77 commented Sep 8, 2024

DIAGNOSTIC

  "errors": [
      {
        "name": "custom_components.xiaomi_gateway3.core.ezsp",
        "message": [
          "192.168.0.143 [FWUP] Can't update firmware"
        ],
        "level": "ERROR",
        "source": [
          "custom_components/xiaomi_gateway3/core/ezsp.py",
          74
        ],
        "timestamp": 1725784701.1208494,
        "exception": "Traceback (most recent call last):\n  File \"/config/custom_components/xiaomi_gateway3/core/ezsp.py\", line 74, in update_zigbee_firmware\n    ok = await hass.async_add_executor_job(flash_firmware, host, content)\n         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/usr/local/lib/python3.12/concurrent/futures/thread.py\", line 58, in run\n    result = self.fn(*self.args, **self.kwargs)\n             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/config/custom_components/xiaomi_gateway3/core/ezsp.py\", line 125, in flash_firmware\n    sock.connect((host, 8889))\nConnectionRefusedError: [Errno 111] Connection refused",
        "count": 5,
        "first_occurred": 1725718941.9180005
      }
    ],

DEBUG

2024-09-08 10:41:11.330 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'miio/report_ack', 'data': b'{"id":292259052,"result":"ok"}'}
2024-09-08 10:41:11.728 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'ZIGBEE_RESET VALUE=1'}
2024-09-08 10:41:11.758 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'ZIGBEE_RESET VALUE=0'}
2024-09-08 10:41:11.787 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'ZIGBEE_RESET VALUE=1'}

2024-09-08 10:41:15.314 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'ERROR: ezspForceReset 0x21'}
2024-09-08 10:41:15.316 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'openmiio/log', 'data': b'{"level":"info","app":"Lumi_Z3GatewayHost_MQTT","time":1725784875003,"message":"[zigb] run"}'}
2024-09-08 10:41:15.329 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'Reset info: 11 (SOFTWARE)'}
2024-09-08 10:41:15.330 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'gatewayInfo.txt was not found'}
2024-09-08 10:41:15.331 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'gateInfo.Vaild = FF gateInfo.state=00'}
2024-09-08 10:41:15.331 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'Directory "/data/silicon_zigbee_host/" was created successfully'}
2024-09-08 10:41:15.332 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'Begin to Reset NCP'}
2024-09-08 10:41:15.335 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'ZIGBEE_RESET VALUE=1'}
2024-09-08 10:41:15.358 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'ZIGBEE_RESET VALUE=0'}
2024-09-08 10:41:15.388 DEBUG (MainThread) [custom_components.xiaomi_gateway3.mqtt.192.168.0.143] {'topic': 'log/z3', 'data': b'ZIGBEE_RESET VALUE=1'}

other question in old version of custom integration there was the posssibilità ti check ZHA Mode

image

but in my version is not possibile

image

@AlexxIT
Copy link
Owner

AlexxIT commented Sep 8, 2024

Something is definitely not working the way it should. Like this one:

sock.connect((host, 8889)) ConnectionRefusedError: [Errno 111] Connection refused

The old "ZHA mode" setting is no longer necessary.

@maury77
Copy link
Author

maury77 commented Sep 8, 2024

idea to solve? I reflash software 2 o 3 times .. but nothing

@AlexxIT
Copy link
Owner

AlexxIT commented Sep 8, 2024

Your gateway is in unknown state for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants