GTench

@sjenkinsDo I need to do a reinstall? I don't see an update button in PG3

@sjenkinsDid an update but still showed 0.1.6 in PG3. Tried a restart but still showed o.1.6. Also got a popup error in PG3 saying "Error fetching from gateway". Another thing was that programs stopped working but AC direct commands still worked. I tried just running the "run then" command but that did not work either. I needed to go into each program, select a line and slick update (did not change anything) then clicked save changes. After that the "run then" command worked hunterdouglas_4-6-2024_105628_AM.zip

@sjenkinsJust did an update but version number is still showing 0.1.6 in PG3. Been using your plugin in programs for the past few days with no problems

@sjenkinsI think you are in pretty good shape and I can't think of any other feature that I would like. I have been using the plugin in programs for the non tilt shades for a few days now and everything is working well. The tilt shades are still running from schedules in the powerview app but I will change that to your plugin in a day or two. I don't foresee any issues doing this but if there are I will report back.

@sjenkinsFor Non Tilt shades: false, Open worked with AC primary at 100 false, Close worked with AC primary at 0 10, SSP worked with AC primary at 10 Created a new scene call Test1 in the powerview app in AC for HunterDouglas clicked Discover and got this error AC screen but Test1 did show up in the AC just not under HunterDouglas in the tree. When I did not originally see it I clicked Discover in PG3; so, not sure which of those caused it to appear. Maybe the log will help Created another scene Test2 and clicked Discover in the AC. This time it showed up under HunterDouglas and there was no popup error message I deleted Test1 using the powerview app and clicked Discover in the AC. Test1 was removed from the AC without any error message in the AC I deleted Test2 using the powerview app and clicked Discover in the AC. Test2 was removed from the AC without any error message in the AC hunterdouglas_4-1-2024_22119_PM.zip

@sjenkinsinstalled latest plugin version, started AC and the Set Shade Position button was now gone from the bottom of the AC non tilt shade screen false,false, Tilt Open works with AC showing 49 false,false Tilt Close works with AC tilt showing 0 false, 25, SSP did not work but AC tilt showing 25 false,55, SSP worked with AC tilt showing 49 false,25, SSP worked with AC tilt showing 25 20,25, SSP worked with AC tilt correctly showing 0 and primary at 20 and shade physically open at 20% false,false, Tilt Open worked, shade closed and AC tilt at 49, AC primary at 0 false,false. Tilt Close works with AC tilt showing 0 false,20, SSP worked this time with actual shade and AC tilt at 25% (not sure why it didn't work before - could be I didn't click the button?) Tilt Close then activated a scene Foyer - Tilt Full and that worked the second time I clicked the button, AC shows 50 (not 49) not really a problem though Tilt Close worked Tilt and position working well for tiltable shades. I will test non tiltable shades next followed by using the discovery button when I add and remove scenes The odd time I need to click the AC button a second time for it to work but this is very infrequent and I don't see it as an issue just FYI hunterdouglas_4-1-2024_110700_AM.zip

@sjenkinsjenkins the ssp button only shows up at the bottom on the non tilt shades AC screen and does not work. The ssp button also shows up in the middle of the AC screen for both tilt and non tilt shades and woks well there for both shade types. I agree that deleting the bottom ssp button makes the most sense. As you said it is redundant. I did try restarting the plug in and also tried the discovery button and restarting IoX but that did not remove the deleted scenes. The only thing that worked for me was a plug in reinstall

@sjenkins false,false, Tilt Open worked with AC tilt showing 49 false,false, Tilt Close worked with AC tilt showing 0 Deleted 2 scenes in powerview app so 2 rooms now have no scenes, restarted plugin nodes and deleted scenes still showing upon restarting AC rebooted IOX but deleted scenes still there reinstalled plugin, restarted AC and deleted scenes were gone and nodes loaded successfully Looks like your fixes worked. Really appreciate all the time and effort you have put into this. Cannot be easy given the lack of good G2 api documentation and the fact you don't have a G2 hub. Your plugin will be quite useful for me. You should consider charging for it. I would be more than willing to pay for it. I will be tied up over Easter with kids and grand kids; so, don't know how much more testing I can do before Monday but the only issue I am aware of right now is the SSP button at the bottom of the non tilt shade in the AC. If you can think of anything else you want me to try, please let me know Gary hunterdouglas_3-29-2024_84857_AM.zip hunterdouglas_3-29-2024_81024_AM.zip

@sjenkins After some testing to try to figure out why my nodes all vanished when I deleted some scenes, it seems that I need to have at least one scene configured in the powerview app in each room for the plugin to load nodes. Once I did that the nodes all loaded into PG3 and the AC

@sjenkinsI just ran across another problem. I deleted a number of scenes using the powerview app to clean things up. I reinstalled/restarted your node server a few times but it does not pick up any nodes now. I attached the log file. Any ideas? thanks hunterdouglas_3-28-2024_113732_AM.zip

@sjenkinsI did some more testing. The only issue I noticed with the tilt shades was that the Tilt Open button does not seem to work. SSP is working well. Open and Close work well For the non tilt shades, the only issues that I noticed was that the SSP button at the screen bottom does not seem to work. The button in the middle of the screen works well. I noticed some strange results just after I started testing the shades but the issues were not repeatable; so, maybe I clicked the wrong button or did something too quickly. For Foyer Tilt shade: false,fasle Tilt Open did not work false,19, SSP, worked and AC updated false,19, Tilt Open did not work but instead closed the shade, AC updated tilt to 0 false,19, Tilt Close did nothing as it should - just testing to see if Tilt Open and Close actions were reversed false,52, SSP, worked and AC tilt updated to 49 false,52, Tilt Close, worked and AC tilt updated to 0 10,52, SSP, worked with AC primary set to 10 and tilt left at 0 10,52, Open worked with AC primary set at 100 10,52, Close worked with AC primary set at 0 tried SSP with a shade that only has Bottom up - Media Room Center was at 10 initially, SSP to 5 worked with AC primary at 5 SSP to 10 caused the shade to fully open with AC showing 100 SSP to 20 caused shade to close partially with AC set at 83 but physically the shade appears to be at 20 SSP to 30 worked with AC primary at 30 SSP to 5 worked with AC primary at 5 SSP to 10 worked with AC primary at 10 - just testing again to see if shade would fully open again but it did not SSP to 15 using SSP at bottom of AC screen did not change anything SSP to 15 using SSP in the middle of AC screen worked with AC updated to 15 Open worked with AC updating to 100 Close worked with AC updating to 0 SSP to 10 using button at the screen bottom did nothing, AC remained at zero SSP with middle button to 10 worked with AC primary updated to 10 hunterdouglas_3-28-2024_105836_AM.zip

@sjenkinsThanks for this. Looking good. Just did a few quick tests and they all worked. Will do more comprehensive testing tomorrow

@sjenkinsWhen I scan the log file I see a reoccurring message that says a function/object... takes 2 positional arguments but 3 were given. Maybe because of the change to accommodate shade functionality. Don't know if this will help

@sjenkinsyes, status looks ok but controls don't work.

@sjenkinsLooks like something broke with this update. Nothing seems to work: SSP or open/close. I see some error lines in the attached log hunterdouglas_3-26-2024_92933_AM.zip

@sjenkinsLike the new AC interface. Nicely done. I just tried false,false tilt open but it did not work. I have attached the log file. hunterdouglas_3-26-2024_82903_AM.zip

OK thanks. Did that and program looks fine now

@sjenkins I rebooted eisy but did not reinstall your plugin then immediately tried false,false,false tilt open but it did not do anything but things seem to work well using SSP I also took a look at the program but it looks the same as before

@sjenkins I should add that the program does run correctly even though the line of code does not itself show the open level. And great idea to add the Boolean to the position

@sjenkins Great update. Working very well! Here are my tests in the sequence that they were performed. Again SSP = Set Shade Position button. Only thing that I have noticed is when I use the shade in a program and set it to either a variable of a number position, it does not show up in the code (see below) false,false,20 SSP works false,false,false SSP left tilt at 20 false,false,0 SSP returned tilt to 0 and updated AC false,false,15 SSP set tilt at 15 and update AC false,false,0 SSP returned tilt to 0 and updated AC 30,false,false SSP worked and AC updated to 30 30,false,25 SSP had no change from previous position 50,false,25 SSP opened blind to 50% and no tilt as it should be 0,false,25 SSP closed blinds and tilt remained at 0 as it should be false,false,false Tilt Open did not work false,false,false SSP followed by Tilt Open worked with AC set to 49 false,false,false Tilt Close worked false,false,60 SSP worked and AC showed 49 false,false,60 Tilt Close worked with AC updating to 0 false,false,false OPEN opened the shade to 100 and AC updated false,false,false CLOSE closed the shade and AC showed 0 hunterdouglas_3-24-2024_115623_AM.zip

@sjenkins On second thought, I think my suggestion is getting too convoluted. How about if there are both tilt and primary entries and SSP is clicked just issue the primary value. If the shades are tilted, it will just fail. If they are not tilted it will work. Leave it up to user/me to make sure the tiltable shades are in the correct position/tilt before clicking SSP. I can also look after this in any program. It seems kind of messy to have this logic put into your plugin. At any rate I will leave it up to you...just my suggestion

@sjenkinsNo, Not at all. I am enjoying this. Just glad you are willing to keep at it. I have 8 shades and look foreword to making use of your plugin leaving tilt at 1 to 100 is fine by me. I noticed that I cannot set primary value with SSP for both shades that have tilt capability and shades that don't. In other words only tilt is working now with the latest version. How about this... if both tilt and primary have a non zero value and SSP is clicked, can you issue a close tilt followed by the primary value (primary has priority) for G2 only. The tiltable shades will not open if they are in a tilt position. If only tilt is requested can you issue a close shade command prior to the tilt command to make sure the shade is closed. If the shades are open and a tilt is requested, they must be first closed before the tilt will work. This seems to be what the cell phone app does So to summarize, for G2 shades with tilt, can you issue a close shade command prior to issuing a tilt command; and can you issue a close tilt command before issuing a SSP primary shade open/close command and don't worry about the time... kids take priority

@sjenkinsGetting there. Tilt now working but still cannot raise or lower primary shade. Here are my test results: Upon initialization the AC shows primary as 100 even though shade is closed. Tilt selection still goes up to 100 instead of 49. SSP for primary to 30 did not work; primary stayed at 100 in AC. SSP for tilt to 20 worked. Tilt closed worked. Tilt open worked with AC showing 49. Tilt closed worked again with AC showing 0. Tried SSP with primary at 22 and tilt at 0 but did not work; shade stayed closed with AC showing primary at 100. SSP with primary at 22 and tilt at 20; Shade tilted to 20, AC showed tilt at 20, AC still shows primary at 100 hunterdouglas_3-21-2024_92439_AM.zip

@sjenkinsAh yes... the joys of programming. On the plus side your plugin still works ok on the shades that do not have tilt capability...just tested that. Nice to know the "gods" got a fix for you

@sjenkinsThe other condition that might need some control logic is if a tilt and primary both have non zero entries and SSP is clicked. Should shade opening take priority?