vspete

@sjenkins,
Version 1.12.3 of the plug-in is working fine accross the board (at the level supported by the G2 API).  While a G3 hub might be better, I cannot justify replacing the G2 given my use case. I have tested all of the scenes and they are working fine. I will address some of your comments above from what I have observed. 
1. For the G2, "default room" is only used as the "room descriptor" for scenes involving shades in multiple rooms. In IoX I place the shades and scenes in separate folders and rename them for clarity. All the scenes work as expected. The "Activated" field shows "True" while the shades are in motion and then returns to "False"
2. For me, using defined scenes gets the job done with a minimum of commands. I seldom position the shades manually. If I need to know their current status, I could make decisions using the shade's "Primary" value.
3. As I only use scenes to set the shades and "Activated" works like "Motion" there isn't any issue. All my shades are hardwired for power, so "Battery" always reports "High" Anyone installing and automating these shades today would undoubtedly use a G3 hub, so I wouldn't bother with creating separate G2 & G3 versions.
4. You do suggest shortening the polling rate in the config instructions. I set the Long Poll at 40 seconds as it takes about 35 seconds for my longest shade to go from open to closed.
5. Having the ability to "Set Shade Position" is a nice feature of the plug-in (works great). Don't know what "Set Shade Position: False" is for?
Stephen, thanks again for the great plug-in and your steller support. Let me know if I can be of assistance should you wish to test any additional changes for G2 hub impact.

I did take a look at the logs, but couldn't discern why certain values were not populating.
I decided the best thing to do was do a complete re-install.  I removed the node server completely from PG3x and then reinstalled.  After restarting the node server and restarting IoX, all fields are now populated for both measurements and forecasts. Only "Climate Coverage" is "blank" in IoX for both Aeris Weather and Forecasts. The GV 11 (Weather) and GV11 (Forecasts) node values are "16" which matches to "blank" in the en_us.txt profile lookup table.
It looks like it may be working as expected now. Now that all the fields are populated, I expect they will be updated when changes occur.  Thanks for your assistance getting this resolved.