Getting Started

More
2 years 5 months ago #293 by stanger89
Getting Started was created by stanger89
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?

Please Log in to join the conversation.

More
2 years 5 months ago - 2 years 5 months ago #295 by stanger89
Replied by stanger89 on topic Getting Started
Regarding my Roku trouble, not sure if I was doing something wrong earlier, but the Roku Command Test is working now, but I see the problem with the remote, seems like it's not getting the roku ID, in the logs I see:
05/02/2024 22:40:10.40 · DEBUG · Server.doCommand - AV|{{active_roku_{{clientname}}}}~Play from livingroomsr
05/02/2024 22:40:10.40 · DEBUG · Server.doCommand - AV|~Play

When I do it from the web portal's Command Test I get:
05/02/2024 22:43:13.43 · DEBUG · Server.doCommand - AV|9~Play from dashboard-fx-posm
05/02/2024 22:43:13.43 · DEBUG · Roku.doCommand - Cmd=[9~Play] Client=[dashboard-fx-posm]

I don't see an "active_roku" variable in the server variables page, if that means anything.
Last edit: 2 years 5 months ago by stanger89.

Please Log in to join the conversation.

More
2 years 5 months ago #297 by David Li
Replied by David Li on topic Getting Started

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?
You are making good progress!
"how to do I configure things so that the server knows my LG TV is the display in the living room"  In the LG driver, assign it to the room.

"It seems like an overlay would be a way of adding common buttons to a number of scenes?"  An Overlay goes "over" a scene.  It can be slid in and out.  It can appear / disapeer based on a variable value.  Very flexible.

re: Roku channels - just add them to the Roku and myServer should see them.

" 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?"
You can create a custom scene for your projector and put buttons on that scene to trigger actions in the driver.  See the driver command builder for what's available.
See user Graydon who posted doing same for his theater.  Not sure if he posted that on this forum or on AVSForum.

Good work!  Keep it up and keep us posted!



 

Please Log in to join the conversation.

More
2 years 5 months ago #304 by stanger89
Replied by stanger89 on topic Getting Started
Yeah, the Roku channels show up on the server, but not the remote (I verified I can activate the channels from the Command Tester on the server).

I'll go dig around for Graydon's info.

Please Log in to join the conversation.

More
2 years 5 months ago #308 by bowlingbeeg
Replied by bowlingbeeg on topic Getting Started
Someone else asked this in another thread but it could be that the {{active_roku_{{clientname}}}} wasn't created on the server. I found that on my appleTV driver it didn't seem to get set so I added it manually and then things started working.

Please Log in to join the conversation.

More
2 years 5 months ago #311 by stanger89
Replied by stanger89 on topic Getting Started
Yup, I just saw your reply there. I'll give it a shot later. Actually I might just try deleting and reconfiguring my Rokus. I think I had some stuff in a weird state when I set things up initially.

Please Log in to join the conversation.

Time to create page: 0.188 seconds