[APP][PRO] Apollo Automation

Thanks for your support! Also, thanks for sharing and the incorrect phishing error. We’ve reached out a few times to get it resolved.

This is an interesting one. I’m currently on a plane and unable to test. Are you on our latest app 2.0 version?

@Doekse are you around to help with this one?

Best,

Justin

I’ll ask our support guy, Brandon, to test, and Abe is great about helping so I hope we can get this figured out soon!

Best,

Justin

The easiest option would be to create a diagnostic report from the Apollo Automation-app on Homey. Our own support can’t offer any support here unfortunately, the developer can see exactly what is going on with that report :wink:

Thanks for the recommendation, Abe!

Best,

Justin

I’ve submitted a diagnostics report, the ID is sent to the Apollo support mailbox. Thanks so far!

Thank you again! Our latest test app should work now. Please install it and let us know.

Still the same problem with the latest version. Also, the sensors don’t show up in the HlkRadar tool app anymore, could this be related?

You’ll most likely have to uninstall the app, restart your Homey, and then reinstall the Apollo app. If that doesn’t work then you’ll need to remove the devices and add them again.

As for the HLK app, please go to the devices URL web server and make sure that the mmWave Bluetooth is toggled on. Then you should be able to see it in the app. I’ll look into adding that toggle into the devices settings.

Can you please confirm that you’re using the test app and which version number do you see?

I have removed the devices, uninstalled the app, restarted homey, reinstalled the app (test app v2. 1.1) and added the devices multiple times.

Weird thing is, now the app says 2.0.0 even though (and I have double checked this) it was 2.1.1 this morning.

LD2450 Bluetooth is enabled in the web config btw, there’s no readings there for presence either and it’s not showing up in the app.

Interesting. Not sure why it would revert back to an older version. Here’s the link to the test app to try again: Apollo Automation | Homey

The Bluetooth antenna on the LD2450 has limited range so you’ll need to be close to the device. BUT if it’s also not showing any presence detection on the web server then we might need to troubleshoot a few other things.

  1. Reflash the device (can fix odd issues and there were recent updates): Factory Re-Flash MTR-1 - Apollo Docs
  2. Reseat the mmWave: MTR-1 Teardown - Apollo Docs

Keep us updated!

The version issue might have had something to do with auto update being enabled before, I have disabled it and the version is still 2.1.1 now.

I have tried flashing the firmware and reseating the mmWave but unfortunately still no result.

Just realized you have a support ticket. I’ll follow-up there. Thanks!

I can Easily connect my MSR-2, and it works great.

But if it’s power was interrupted or connection is lost my MSR-2 not automatically reconnecting to the Homey.

It reconnects to WiFi and visible on the network with the same ip, but homey app always sees it with error until I remove it and add again.

Any suggestions on how to fix it?

Yes, for example, you can restart the app automatically every hour. Enable the Power User experiment in More->Settings->Experiments, and then create a Flow: WHEN Date/Time → Every 1 hour THEN System->Restart App Apollo Automation

It sounds like a sloppy workaround.

it is easier to create an post install patch fixing the bug if it is one. I hoped that it is a configuration issue.

@itsklimov You can also create a Flow like this:

Every 20 seconds → Make HTTP GET request to http://[your-sensor-ip]/ → AND boolean variable is set to yes → Restart app Apollo Automation → Set boolean variable to No. Then, connect the error line of the HTTP request card to the Set boolean variable to Yes. This is assuming the device supports HTTP requests, not sure since I don’t own one.

Thanks for your support!

Could you please try our Apollo test app and let me know if you have the same issue.

Great flow and thanks for helping! BUT our test app should fix this. Keep us updated!