Hmm, ok, I had created the device manually before adding the app. So now, I removed that device and the app. Recreated the app and let it rebuild the device from the app.
I remember it was a bit of a pain in the butt for me as well when I first installed it. You're definitely on the right track though. And your d7 is still connected to your network? Make sure it's awake maybe?
Can you enable debug logging in the app, enable child devices on the D7 device page, and then click save and see what the log shows? It should create the child devices in just a few seconds. If you disable child devices and click save it will remove them.
EDIT: Also, just speculation on my part, but I wonder if I could be creating the problem because I have two maps on my D7. Only one is activated and it definitely has zones defined but wonder if this edge case might be the root cause?
Could you show me the app logs also? They may show a little more information. It's been a while since I have looked at the API, but if I remember correctly it is supposed to find the most recent persistent map. So if the map you created without zones is newer than the other one, that could be the problem. You can send me a PM if you want to.
@gassgs I’m pretty sure your theory is right. Just to test, I added zones to my secondary map - a map I set up more recently that I rarely use. As soon as I did, and then went back to the device to activate zones, they showed up.
Unfortunately, they’re not the zones I want. So I’m going to just delete the secondary map, redo it all, and see if that works. Will report back.
EDIT: sure enough, when I deleted the secondary map, everything worked great. Maybe for now, you want to note somewhere zones only work for one map or the like.