[App][Pro] Hailo Libero 3.0 – Local integration for Homey Pro

Hi everyone,

I’ve developed a Homey Pro app for the Hailo Libero 3.0.

The app communicates locally with the Libero over the LAN, so normal operation does not rely on the cloud.

Current features include:

  • Open the Libero from Homey
  • Adjust LED brightness
  • Adjust pullout force
  • Adjust detection range
  • Restart the device
  • Sensor values for brightness, force and detection range
  • Flow cards for triggers, conditions and actions
  • Local network communication

The app has now been submitted for Homey App Store certification.

You can already install the test version here:

If you own a Hailo Libero 3.0, I’d be very interested in your feedback and testing.

Feel free to report any issues, suggest additional Flow cards, or share ideas for future improvements.

Thanks!

Hi @Antoine_Chaulieu,

First of all, thank you for creating this integration. However, I’m running into an issue: the integration can’t find my Hailo Libero 3.0 on the network, even though it’s connected. Would it be possible to add an option to specify a fixed IP address? That way I could work around the discovery issue.

Let me know if you need any additional information.

Hi @7Hills

Thank you very much for your feedback!

The current version of the app uses Homey’s automatic MAC-based discovery. At the moment, it recognizes the MAC hardware prefix used by my own Hailo Libero 3.0 (8C:AA:B5).

It is possible that some Libero 3.0 hardware revisions use a different network module/MAC prefix, which could explain why your device is not being detected. It could also simply be that Homey cannot see the device through automatic network discovery on your network.

I’m already planning an update that will keep automatic discovery as the default method, but will also add a manual IP address option as a fallback when the Libero cannot be found automatically.

Could you please tell me the first three groups of your Libero’s MAC address? For example: AA:BB:CC
You don’t need to send me the complete MAC address.

This will help me determine whether your Libero uses a different MAC prefix and potentially improve automatic discovery for other users as well.

Thanks again for reporting the issue!

Thanks for getting back to me so quickly!

My Hailo’s MAC address starts with C8:C9:A3, so it does use a different prefix than the one you expected (8C:AA:B5). That explains why automatic discovery isn’t working.

For reference, here’s my device info:

  • Device: Libero30_2007BD
  • SW Version: 3.0.4

One more thing (not critical, but worth mentioning): the integration requires entering a password during setup. However, as far as I know, you can’t change the default password on the Libero, so asking for it might be unnecessary?

Hi! Just a quick update: I’ve prepared a new test version of the Hailo Libero app that should address the issue you reported.

The new version includes:

  • support for your MAC prefix C8:C9:A3
  • improved automatic discovery
  • a manual IP address fallback if automatic discovery does not find the Libero
  • no password field during setup anymore, since the default Libero password is fixed

The new version is now available for testing. If you have a moment, could you please install the test version and let me know whether your Libero is detected automatically this time?

If automatic discovery still doesn’t find it, you should now be able to enter the Libero’s IP address manually and connect directly.

Thanks again for your help and for reporting the issue — your feedback was really useful for improving the app.

Hi Antoine,

You’ve made my day with the test version. My Hailo is now perfectly connected and working great! The automatic discovery is working now, which is excellent. I’m especially happy that I can lower the detection range when my robot vacuum starts cleaning, so it stops triggering the bin to open. Really annoying problem solved!

One thing I noticed: I can adjust the range below the default 35mm without issues, which is great. But I can’t increase it above the default 100mm. Do you know if that’s a software limitation which you can bypass, or is 100mm the maximum the sensor can actually detect?

Thanks!