Drop down menus

[TSinclair]

As I have migrated to eisy, I've tried to be organized and specific in my device and program naming.  HOWEVER, the issue this has created is now some of the device names are too long to fit into the space of the drop down menu in programs (see screen print).  

By chance is there a way to see the full device name or a work around?

Thanks in advance.

 

 

[DennisC]

Under File you can change the font size, but I think the smallest font is 12, which for me, doesn't help. Possibly, changing computer resolution might put more characters in the space, but then it becomes hard to see.

I learned to adjust the way I name programs to keep the important parts at the beginning of the program name and to put programs in to folders to reduce the name but provide required organization.

A plus to this, using folders allows for programs to be located much quicker.

[trevorst]

I have the same issue we need a method of parsing out the data in the lists so that we can drill down into the folders, not have the concatenation we have now.

[brians]

14 hours ago, TSinclair said:

As I have migrated to eisy, I've tried to be organized and specific in my device and program naming.  HOWEVER, the issue this has created is now some of the device names are too long to fit into the space of the drop down menu in programs (see screen print).  

By chance is there a way to see the full device name or a work around?

Thanks in advance.

 

 

I usually rename my nodes to something shorter and tuck away all the unused ones in a folder named ZWave extra nodes. Before I rename, I make a copy of original name and then place in notes so I can always look at what it was originally.

Can't help but notice this is Zen32 you are showing, and how you are making separate programs for each on/off state keeping track of variable it seems. I can't see all what your programs do so not sure... but I do something similar and use two programs per button, but also keeps ZEN32 Button LED in sync even if load is turned on/off remotely.. see here, not the basic association method but program method.

 

 

[TSinclair]

We are taking a similar approach with the ZEN32 and a separate folder for all of the extra nodes.  What made my ZEN32 scenario a bit challenging is I am using 3 of the 5 buttons to control ~8 lights/lamps in the Family room, effectively high, medium, low or Movie, TV and Bright.  A press on any any of those 3 buttons determines the current state, turns on the appropriate brightness, and turns on the appropriate LED and turns off the LED on the other buttons.  So for example if the current state is medium and the high button is pressed the program turns off the medium button LED and turns on the high button LED and adjusts the lights.   

I should add that this was unworkable with the 994 as it took 3-5 seconds for the lights to respond to a button press and 8-10 seconds for the button LED change to occur.  With eisy the lights are instantaneous and the LED change is in a second or two.

[Geddy]

@TSinclair looks like this finally got implemented into IoX with 5.5.6 release..."wider node selection boxes"

 

 

 

Quote

Features

• Z-Wave Compatibility Mode to support non-conforming Z-Wave devices (right+click Z-Wave | Compatibility Mode)
  • Fixes problems with status updates / user codes for many locks
• Added 'Theme Size' to Admin Console for wider node selection boxes
• X-Ray for Insteon nodes

 

[TSinclair]

I saw that.  Not sure if this was in the pipeline or if it's evidence of UDI monitoring this forum and listening to feedback, but BRAVO either way.

Now, after the 5.5.5 pain, there is no way I'm upgrading to see how this works until I see positive feedback overall!

[TSinclair]

Well I just upgraded to 5.5.6 which went flawless.

File>Themes>Theme Size>3  is PERFECT! 

Thank you UDI!

[sjenkins]

17 hours ago, TSinclair said:
Now, after the 5.5.5 pain, there is no way I'm upgrading to see how this works until I see positive feedback overall!

I think I calculate 9hrs until you succumbed & updated. 
I can relate