Yes. Also, it’s not “bad” to underpower LED strips, you’ll just notice it when you try to turn them to full brightness. I have LED matrices with 64 LED’s that should require a 4A power supply (64 * 60mA), but I run those from a 2A supply and it works just fine (even at full brightness I never notices any issues).
I guess results variate a bit. I have a 2m LED strip with 60 LED’s per meter powered by an 8A adapter and the LEDs at the end of the strip are less bright. For me it’s not a big deal but you should be aware of this as well.
You can typically power long(er) LED strings from both sides (from the same power supply), or from the middle of the strip, or even the positive from one side and the negative from the other side. There are inherent losses in the circuit traces of the strips that cause voltage/power drops.
First of all I want to say thankyou for keeping this app up to date and supported.
I have not moved up to test 5.X couse it will break two other apps I am currently using. But really good to know that my ledstrips are compatible now.
A question:
I have a rgbw-strip. In the MagicHome phone app I can dim the brightness of the rgb and the white LEDs independently.
That does not seem possible in your app, or am I just missing something?
It’s probably not supported (yet). I don’t have a rgbw strip to test with atm so can’t really look into it. Could you post a screenshot of the Magic Home app and would you be willing to test once you can install the 3.x version of the app?
The magichome app (iOS) has this interface
Colormatrix (colorweel/numeric)
5 slots for saving favorite settings
2 sliders for brightness (no numeric value avilable)
-Sure I can do some beta-testing for you, but I will stay on homeyFW v4 a little longer. (Not willing to go beta on the entire thing just yet. Way to many issues atm)
Let me know when you do. I’m not going to maintain the SDK2 versions anymore. We will look into it once you are in firmware 5.x.
Hi, I’m running the latest version of Homey experimental V5 and the test version of Magic Home, but the app can’t find my lights 
the lights are connected and working with the emote control and the Magic Home app (non-Homey).
Diag report 626a2179-8177-4277-91dd-0bc10741d3c5
There is nothing in the log. Are the lights on the same LAN?
Yes same Lan. I’ve also factory reset them and still not visible. I know occasionally WiFi controlled devices become unresponsive in Homey, but no matter what I do I can get these back online with Homey.
Could you try and restart Homey, try and pair your Magic Home a couple of times and if it doesnt work send me a crash report shortly after. If the log is still empty it indicates the devices are not found by Homey. There is not much I can do about it I’m afraid. Perhaps a router blocking UDP traffic which is used to discover the devices?
I have been trying for weeks but the controller was no logner available in 5V anywhere.
So I ordered the one in the link below with the 2 outputs for the led strip.
i also got the SP501E.
For both when I connecto them to homey I can only turn them on and off.
I can not control any colors or make patterns.
I am still on the latest official release 4.2.0
Hi I’m also heaving Magic home bulbs, can you make this app compatible with these wifi led bulbs of magic home. The bulb is not expensive, pairing it as controller does not work. Also not as Xiaomi philips lights with IP and token?
The Magic Home bulbs should work. What does not work for you?
The Xiaomi Philips bulb are a completely different device and not supported by this app. You need the Xiaomi Home app for that.
I don’t know which app to use to connect the Magic home bulbs with Homey?
The Magic home Wifi Led controller does not make the connection?
If you control the app using the magic home app on your smartphone it should also work with this app.
Saying it doesn’t work or does not make the connection does not really help. What have you tried and what is the result? Is the lamp not discovered or does it give an error during pairing, if so what error?
If there is an error, try rebooting the app, re-pair and send a crash report from the app settings.
I connected the bulps with the Magic home app. So now I can control the bulps via this Magic Home app. But to add the bulps to my Homey device, Homey does not show the bulps in the connection screen. Therefore I added Magic Home WiFi led controller, but when I start this, after a view second appears “no new equipment found”. Then I tried ESPurna, where I added the IP address of the bulp 192.168.1.9@80 and the DID 00000000000000000000a043b02fd572 but without success
.
If Homey and the light are on the same LAN then it’s probably not supported by my app is it’s not discovered. I don’t know why not but perhaps something changed in the firmware of the latest version of these bulbs. It’s hard to tell without a bulb to test with. I’m afraid you are out of luck.
v3.0.3 - 2021-02-22
- Updated to SDK3 (requires Homey version 5.x).
- Added support for SPI Addressable Controller including an action card to set one of the 300 pre-configured effects.
The duplicate entry seems to have something to do with local and cloud connection, when i setup the device without local connection, it will only show the AK001-ZJ2145, when i then connect it to the local network it will show both (one named AK001 and the other one called ‘other’ .So far it seems to be working fine, except for the “white” color selector. (on/off, dim and colors seem to work fine (currently using the “other”, but works on both).
When selecting the “white” color selector in homey i get an error: Missing capability Listener: Light mode. (No matter if I select the AK or the “other”) @Phuturist is this a (known) bug?)
UPDATE! The duplicates are caused by something else (has nothing to do with local vs cloud). Every time you remove and add the device in homey it adds an “other”, so if you do it 3 times you will have 1x AK and 2x “Other”. Solution. remove the device that you already have in homey, restart the Homey MagicHome app, then add the device, you will see only 1, AKL… @Phuturist is it a bug or is there somethingin Magichome thats causing this behaviour? (And if you need someone to test updates, feel free to let me know what you want tested)
