A clarification first: the Pixoo64 app currently does not use mDNS discovery. Auto-discovery uses the Divoom same-LAN cloud endpoint first, then falls back to a local subnet scan from Homey. So if mDNS/Bonjour is blocked or unreliable on your network, that should not be the direct cause here.
That said, direct connection still depends on Homey itself being able to reach the Pixoo64 locally. A curl command from your PC only proves that your PC can reach the Pixoo. If Homey is on another VLAN, guest Wi-Fi, isolated SSID, or behind firewall rules, Homey may still be unable to connect even when curl works from another machine.
I found one issue in the pairing detection logic: some newer Pixoo64 API revisions can answer the test command with a minimal { "error_code": 0 } response instead of the full configuration fields the app expected. That could make manual pairing fail even though the API was actually reachable.
I’ve uploaded test version 0.1.7 with improved pairing detection:
accepts both legacy http://IP:80/post and newer http://IP:9000/divoom_api
accepts minimal successful API responses during detection
lets you enter either a plain IP address or a full local API URL
improves the Divoom cloud discovery request format
If pairing still fails after 0.1.7, please check whether Homey can reach the Pixoo64 from the same network segment. Common blockers are VLAN separation, guest network isolation, client/AP isolation, firewall rules between Homey and IoT devices, or Homey being wired/wireless on a different subnet than the Pixoo.
This version works! Now it discovered it immediately like the stable released version, but unlike it it shows the Divoom as online and ready for play time.
Hi DJP, very glad to find the Divoom Pixoo 64 is supported by your app.
Therefor I ordered one from ibood which has it on sale today for €69,95 which seems a reasonable price for the device. Just a tip for others who might be interested as well.
I just ordered a Pixoo 64 II. I hope that it is supported by the app. I have looked for a long time for a simple display for some stats. Naturally there are always the repurposed e-ink price tags, but this seems like a good start.
@DJP Big thanks for the app. It worked on first try with autodetect. Question: I ordered a Pixoo64 II, but I am a bit confused. The II is not really mentioned on the packaging, maaaaaaybe as a 2 in the serial number… However, the app detected Legacy Revision on the API. I assume that has nothing to do with what version I have of the device, or does it?
I think there are multiple revisions of the hardwares, including “brighter” ones, maybe that’s what the shop you ordrered from calls “II”.
What I know is that there are 2 revision of the internal system, and if yours is detected (and working) as “Legacy” then it’s the “original version” (still, maybe with a better display).
I can’t really tell you more about the different versions, packaging, naming etc. Divoom is a chinese company and it’s hard to keep track sometime due to localization issue, region specific naming, etc. Even the “Legacy” vs “Newer” is just how I’ve decided to call it and I had no idea it existed before getting feedbacks about issues. Divoom still hasn’t updated the API document to adress that newer revision.
@DJP Thanks for the reply. Divoom themselves claim that I have gotten the II, but I have been around the block to many times… That’s why I asked you. I think I’ll communicate some more with them before accepting their explanation. Do you have any recommendation as to how I might access hardware revision data, and what the two versions should list in terms of components? That way I could send them some more detailed questions.
Absolutely no idea, I wouldn’t even consider my identification of “legacy” / “newer” as anything more that a differenciation of API versions. Maybe they have 2 production lines with different setup or whatever. who knows.
What did you expect from this “version II” to be different ? have been able to see anything online about differences…
Some kind of hardware difference that would bring some minor noticable change. Like Homey23/26 perhaps. It could just be that all the specs that matter are the same, but the hardware platform is slightly different . (Perhaps more reliable.)
Anyway, now to play with your app and test out how to make my own designs. Again, thanks for the app.
The app is working great and I have no problem building my own layouts. I might have detected a layout bug in the “Display Text” command, but I want to do some more testing before I bother you with it.
However, I do have a feature request (if it is possible through the API). It would be nice to be able to request which channel the Display is in, so that for instance when I have put it in Clock mode, I can check before an update to a variable triggers a channel switch to Custom.
Maybe I am missing another way of doing it and the feature is unnecessary. Please tell me if that is the case. Thank you.
