-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
[Bug] Running the Mac OS - Homebridge Zigbee2MQTT - doesn't really start up when the Mac OS boots up. #844
Comments
I think this is an issue with your setup. |
I'm not sure. how do I check it?
|
That really depends on how you've setup your system. Personally I'm using a Docker compose file, in which you can explicitly set the dependencies between containers. I would think however that the order itself shouldn't be a problem of the (important) messages from Zigbee2MQTT are persistent on the broker. |
Can you provide the plugin configuration? I use this plugin with catalina on intel mac mini 2012 for two years approx, then last month on mac mini m2 with sonoma without the same problem |
Do you mean JSON in Homebridge? { or configuration.yaml permit_join: true |
@DarkGrey88 It's weird, visually it's the same as my config but try to cache_state: true |
Yesterday I started from scratch. And it seems to me that as long as I just added zigbee devices and rebooted my mac at the same time, everything worked fine. The problem appeared after I enabled child bridge for the z2m plugin. And then after rebooting my mac the devices did not appear again until I rebooted the child bridge z2m plugin. |
it works the same even without that line( |
It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions! |
Does your mqtt broker use authorisation? |
@LaurentCole Do you also have Zigbee2MQTT running (e.g. can you access its frontend to see that the dongle works)? |
I have a username and a password |
no I can't access the frontend. How to ? |
the text configuration of the plugin does not show this |
you need to install zigbee2mqtt first https://www.zigbee2mqtt.io |
There's a rough outline of the steps needed to set this up on the plug-in website: https://z2m.dev/install.html More information about the Zigbee2MQTT frontend, can be found on the Zigbee2MQTT website: https://www.zigbee2mqtt.io/guide/configuration/frontend.html |
my dongle is already uptodate |
FYI factory fw is not good |
So I finally manage to install zigbee2mqtt, thx to you for the link Then launched zigbee2mqtt via terminal
[2024-05-21 17:54:06] info: z2m: Logging to console, file (filename: log.log) I can access the frontend but I can't add devices Finally succeeded to add a device. Do you have a link to easily update the coordinator on a mac. Thx again for all your helps |
Hi guys, thx for your help, everything works fine now. But zigbee2mqtt doesn''t start when I restart the mac Do I need to modify this line : :-) |
I'm using Sonoma on M2 Mac Mini, our work dirs and file names may be different. |
Hi, Do you have any idea what is wrong, could you help me a bit more? |
I used another program. |
Hi Bootstrap failed: 5: Input/output error |
Is there an existing issue for this?
Describe the bug
I have installed Homebridge on a Mac OS Monterey. I have Mosquitto and Zigbee2MQTT configured. Mosquitto and Zigbee2MQTT - works at system startup which is visible thanks to MQTT Explorer. I installed the plugin - z2m and prescribed the mqtt address. The plugin rebooted after changing the settings and everything worked! Hooray? No. After the reboot it turned out that it didn't work properly.
The Homebridge log says it's fine.
[3/14/2024, 7:33:24 PM] [homebridge-z2m] Connected to MQTT server
[3/14/2024, 7:33:29 PM] [homebridge-z2m] Zigbee2MQTT is ONLINE
[3/14/2024, 7:33:30 PM] [homebridge-z2m] Using Zigbee2MQTT v1.36.0 (identified via zigbee2mqtt/bridge/info)
but the accessories section was empty.
I restarted the child bridge z2m
and everything worked again.
[3/14/2024, 7:35:16 PM] [homebridge-z2m] Process Ended. Code: 143, Signal: null
[3/14/2024, 7:35:23 PM] [homebridge-z2m] Restarting Process...
[3/14/2024, 7:35:24 PM] [homebridge-z2m] Launched child bridge with PID 1094
[3/14/2024, 7:35:24 PM] Registering platform 'homebridge-z2m.zigbee2mqtt'
[3/14/2024, 7:35:24 PM] [homebridge-z2m] Loaded homebridge-z2m v1.11.0-beta.3 child bridge successfully
[3/14/2024, 7:35:24 PM] Loaded 1 cached accessories from cachedAccessories.0EBEC2A64B1B.
[3/14/2024, 7:35:24 PM] [homebridge-z2m] Connecting to MQTT server at mqtt://10.0.1.28:1883
[3/14/2024, 7:35:24 PM] [homebridge-z2m] Restoring accessory: test_sw (0xa4c138f3271bad89)
[3/14/2024, 7:35:24 PM] Homebridge v1.7.0 (HAP v0.11.1) (homebridge-z2m) is running on port 59590.
[3/14/2024, 7:35:24 PM] [homebridge-z2m] Connected to MQTT server
[3/14/2024, 7:35:24 PM] [homebridge-z2m] Zigbee2MQTT is ONLINE
[3/14/2024, 7:35:24 PM] [homebridge-z2m] Using Zigbee2MQTT v1.36.0 (identified via zigbee2mqtt/bridge/info)
And so it is every time. To make everything work, after each system reboot you need to reboot z2m.
Related devices
No response
Related Devices
No response
Steps To Reproduce
No response
Expected behavior
z2m works correctly at system startup - automatically
Device entry
No response
Status update
No response
Messages from this plugin
No response
This plugin
1.93
Homebridge
1.7
Zigbee2MQTT
1.36
Homebridge Config UI X (if applicable)
No response
The text was updated successfully, but these errors were encountered: