Hi everyone,
I’m having an issue integrating the new Sonoff MINI-ZB2GS with Homey: it pairs, but I can’t get both channels/endpoints to work independently. Only shows one channel.
Is there any solution for this device?
tks
Hi everyone,
I’m having an issue integrating the new Sonoff MINI-ZB2GS with Homey: it pairs, but I can’t get both channels/endpoints to work independently. Only shows one channel.
Is there any solution for this device?
tks
The Sonoff app doesn’t support the device. You should request support here:
Hi! If you’d like, I’ve created a fork of the original project where I’ve added some devices, including the MINI-ZB2GS. I’ve already sent a pull request to the developer, but I see the response times are quite slow (if there ever are any…).
This is the link to the repository, but you’ll have to install it manually:
It’s a fork of the Sonoff official app (the first one)
Both have few devices/ features available when we look at all those on the market and no new releases by sonoff
Could you help how to install it manually, sorry but im a user with low IT knowledge and first time.
Will appreciate a lot.
Regards.
Installing from code takes a bit of practice, but let’s try:
Node.js is a program required to run the Homey development tools.
Open your browser and go to https://nodejs.org/
Click the green button
Download and run the installer
Open a Terminal:
Win + R, type powershell, and press EnterType the following command and press Enter:
node --version
If you see a version number like v20.x.x (must be v18 or higher), Node.js is correctly installed.
Homey CLI is the official tool for installing and managing Homey apps from the terminal.
With the terminal still open, type the following command and press Enter:
npm install --global --no-optional homey
Installation may take a few minutes. Wait until the command prompt returns.
homey --version
If you see a version number, Homey CLI is correctly installed.
First, navigate to the folder where you want to download the project:
cd C:\Homey\Sonoff
Then clone the repository:
git clone https://github.com/s-dimaio/Homey.Sonoff.Zigbee.git
From within the project folder, run:
npm install
This command will automatically download all the libraries required by the app. Wait for it to complete.
Before installing the app on Homey, you need to log in with your Athom account:
homey login
A browser window will open automatically, asking you to log in with your Athom credentials. Follow the on-screen instructions.
Make sure your Homey is connected to the same Wi-Fi network as your computer
Then run:
homey app install
The Homey Sonoff Zigbee app is now running on your Homey device. Open the Homey app on your smartphone to start adding your Sonoff Zigbee devices.
Hello s_dimaio,
Hello,
First of all, thank you for your work on this project.
I successfully installed the app using Homey CLI (including a clean installation with homey app install --clean). The app installs without any errors, and I can see all drivers being added in the terminal during installation (e.g., SNZB series, ZBMINI, etc.).
However, after installation:
The app either does not appear correctly in the Homey Apps list
More importantly, the devices/drivers do not appear in the “Add device” section in the Homey app
I am unable to add ZB2GS using the app sonoff zigbee or by zigbee technogies
I have already tried:
Reinstalling the app multiple times
Using --clean install
Restarting Homey
Reinstalling dependencies (npm install)
Closing and reopening the Homey mobile app
But the issue persists.
I had use chatgpt to help me to fix some problems that i had during the instalation becose my sistem is Mac ios
Thanks in advance for your time!
regards
Instead of installing try homey app run --remote
This will run the app and shows a realtime error log, maybe this reveals useful info.
(--remote means “on the selected Homey”)
.
What does this mean, Renato, does it appear or doesn’t it?
This means the related app is not installed or doesn’t run.
As suggested by Peter try running
homey app run --r
and send me a PM with your terminal log so I can take a look.
If you had the original app installed, the issue is probably the version number: I see now that the original app has recently reached version 1.8.3, while my fork is stuck at 1.8.0.