With the great work of the Allonis team sussing out the myDesigner issues I'm finally making some progress. Things are sorta working, here's where I'm at:
- Got MyServer setup/activated.
- Went through and added all the drivers that exist so far
- I setup rooms
- Configured those drivers (notably for my initial setup, my Rokus and LG TV)
- I think I've got those devices correctly assigned to the right room.
- I setup the SmartRemote wifi, and connected to the server
- Note that I initially screwed this up, but I went into the app settings in the Android settings and deleted the data and re-set it up.
- I've got myDesigner connected to my server, and renamed the smartremote template.
- I picked the right room on the SmartRemote and I see the correct devices* on the remote.
Digging through, it seems like at a really high level, the macros and command are all setup on the server through the web portal, and then myDesigner is used to create pages on the remote for accessing those macros. It looks like for my Rokus, the hard buttons were automatically configured on the Roku scene.
Perhaps my first question is, how to do I configure things so that the server knows my LG TV is the display in the living room, and that it should get turned on? I found the
displayon.livingroom macro which has this:
AV|{{livingroom_avamp_id}}~Power~On!
AV|{{livingroom_display_id}}~Power~On!
I looked in the server variables section and I don't see either of those two variables defined. Do I need to do that manually, or is there a more elegant way to configure that.
Another question I have is, are the best practices for setting up, lets call them sources. For example there's a few channels on the Roku that I'd like to add (eventually I think it would be cool to put them on the index, but for now I'll just stick to the Roku scene). I was going to start defining them manually, but I was wondering if there's a way to define them on the server, and then have the remote query the list of channels from the server (like the index page buttons are found)?
And then a sanity check, I read a bit about scenes vs overlays. It seems like an overlay would be a way of adding common buttons to a number of scenes? For example in my HT, I'll want lens memory selections on several of the other activities (scenes I think in allonis-speak). So I could make an overlay with a pulldown list of lens memories and apply that to all the scenes that that's useful for?
