how does this work?

If you are making edits to the global hard buttons defined as the project properties then you have to make sure you click off the field in the grid before saving the project. This is an annoyance and a by product of how that grid object registers an edit. If this is not the issue and there are no errors being reported in the Designer events dialog then I'll have to remote in to investigate.

"What is the best way to get back in sync?  Should I create the new macros manually, using the instructions in this thread to pass in the variables?"

The version of the server I released today should resolve the mis-matched volume, display and power macro issues.

I'm having an issue which I think may be related to this... Whenever I select my TV or my Android TV box (both in the same room so same TV) myServer is toggling the TV power, instead of sending a power on... I dont know if myServer thinks the TV is off and is trying to turn it on (I assume this is whats happening)... In practice if I click on Samsung TV, the tv goes on... if I then go back to the menu and click the Android TV, the TV goes off...  (If the TV is on and then I click the menu and click TV, it will turn off...)

I looked in the Macros but havent found anything of interest... was looking for a Power~Toggle, or Power~Off and I've found neither... 

Editing to add: The TV power status is correctly reflected in the Driver, so myServer shouldnt be "lost" about the power state

Edit2:

Commenting this line "solves" the issue... It doesnt turn on my TV anymore, but at least it doesnt turn it off when I'm switching sources/screens on smartremote.
// Always Turn the display on if defined!
// If|isGT##{{{{activeroom_{{clientname}}}}_display_id}}##0##AV|{{{{activeroom_{{clientname}}}}_display_id}}~power~on!
//!

Would this command send  a Power~Toggle instead of a Power~On in any case?

RoyN wrote:

I'm having an issue which I think may be related to this... Whenever I select my TV or my Android TV box (both in the same room so same TV) myServer is toggling the TV power, instead of sending a power on... I dont know if myServer thinks the TV is off and is trying to turn it on (I assume this is whats happening)... In practice if I click on Samsung TV, the tv goes on... if I then go back to the menu and click the Android TV, the TV goes off...  (If the TV is on and then I click the menu and click TV, it will turn off...)

I looked in the Macros but havent found anything of interest... was looking for a Power~Toggle, or Power~Off and I've found neither... 

Editing to add: The TV power status is correctly reflected in the Driver, so myServer shouldnt be "lost" about the power state

Edit2:

Commenting this line "solves" the issue... It doesnt turn on my TV anymore, but at least it doesnt turn it off when I'm switching sources/screens on smartremote.
// Always Turn the display on if defined!
// If|isGT##{{{{activeroom_{{clientname}}}}_display_id}}##0##AV|{{{{activeroom_{{clientname}}}}_display_id}}~power~on!
//!

Would this command send  a Power~Toggle instead of a Power~On in any case?

What kind of TV do you have?  It might be the case where your TV doesn't support discrete power commands.  I have IP-controlled Sony TVs with discrete power commands and they work very well.

If your TV only supports power toggle, either the driver will need to be updated to track the state of the TV power and act accordingly, or you might need to create a state variable to reflect the current state of the TV power and exclusively use macros to turn in on or off.  There may also be a series of commands unique to your TV that can function as discrete commands; Remote Central might be a place to find these sequences.  These aren't ideal solutions, since it's always possible to get out of sync, but it might be the best you can do.

Kyle

Apologies as I should have really made this clear... its a Samsung TV from 1-2 yrs ago, it does support discrete power inputs, and using the Tizen Driver test functionality I can turn it off / on (without toggling) and it does show when it is ON or OFF on the driver... I think the communication part is ok... maybe there is some issue between the new way and the Tizen driver? I wonder if anyone with a Samsung TV tried it out?

You should turn on debugging and see what commands myServer is sending. That might point you in the right direction.