sjenkins

Finally have Shade nodes which only use the parameters they have capabilities for. If a new shade-type comes along it should default to all parameters. Feel free to give feedback! VERSION = '0.1.6' """ 0.1.6 DONE parameters based on shade capabilities 0.1.5 DONE format for program setShadePosition DONE set Shade Position change using False to define which parameters to change DONE more debug on G2 so it acts as expected 0.1.4 DONE add node_queue & as result need pause updates while in discovery DONE FIRST TRY G2 tilt feature 0.1.3 DONE node discover rewrite to allow add/remove DONE add event 'homedoc-updated' currently no actions DONE limit room label size to 15 as room - shade/scene < 30 for ISY DONE clean up LOGGING.debug messages DONE G2 bug fixes 0.1.2 DONE change icons to nicer ones DONE docs with screenshots & description for udi spotlight DONE add troubleshooting document DONE add some support for G2 gateways (no gateway push, only polling) 0.1.1 DONE tap into gateway events, which allows longPoll update to move from 30s to 60s DONE active scene indications from events DONE shade motion indicator from events DONE shade position update from start, stop, online events DONE remove parameters based on shade capability (primary, secondary, tilt) DONE update readme & config instructions to highlight G3 scope 0.1.0 DONE handle multiple gateways automatically, picking primary & switching if required DONE updated configuration instructions as well as link to the forums past versions: 0.0.9 DONE fix uom for positions(100) & ids(107) DONE more notices clean-up DONE shade naming to include room as scenes DONE remove status based on shade capability (primary, secondary, tilt) 0.0.8: DONE handling of notices individually DONE polling 5s short-poll 30s long-poll DONE status for programs (positions etc) 0.0.7: DONE faster status updates when command is given DONE bug fix DONE re-order of parameters displayed 0.0.6: DONE move shade by specific amounts DONE bug fix scenes not activating 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

@GTench Sorry I may not have been clear. You DO need to reinstall the plugin. When I say Admin restart is does NOT mean an EISY reboot. That is almost never required. I just meant that the Admin (blue screen) needs to be closed and reopened. With the reinstall of the plug-in the program should show the parameters. -- I made a change there. The false, false, false Tilt open I will take another look at as it works with mine.

@GTench Fixed the program formatting issue. it includes a profile change so admin restart. also, check my above comment ; wanted to verify all other tests especially the Tilt Open as I did not see that in mine.

Really good to hear we are getting closer! Thanks for doing such extensive testing. Am I right just the below didn't work as expected? Just wanted to verify the above. Tried on my G3 and it worked, so want to narrow the issue. On the showing up the code program issue ; verified same response with mine ; yup, I know what I have to do there. btw: as you suggested primary gets priority over tilt for G2 -- for fun I would like to see what would happen if I sent primary to the G2 posKind1: 1 & tilt to posKind2: 3 and see what happens. Would only be useful if there is no secondary. I might make a button just for you to try it out.

@GTench I put out a new version to consolidate all our changes plus I think I have cracked a better way to define set shade position. You can have more than one uom in an editor file so a False means don't bother which a number means you want a change. Check it out. Make sure to either hit the update profile button or restart your admin console after the update. As stated in the notes I think I know how to better refine the shade node based on capabilities without having 20 different node types. Basic structure programming but I got put off by how the ISY talks to the nodes. The experts helped me here. Lets start a new thread if you don't mind - this one is beyond it usefulness & I don't like the title I'm going to close it solved but please start a new one with feedback either in the announcement of 0.1.5 or a new one. Thanks again!

Put out a new version which has a new set of profile files as well as G2 debug. Make sure you restart your Admin console after install. The main 'feature' is in set Shade Position you can set False or 0-100, this allows the user to define what is moving. Next I will likely work on cleaning up the shade node so that is matches the features of a shade closer. So that tilt or secondary only show up for shades that need it. After talking to the node experts I think I now know how to accomplish this without having a node type for every type of shade x G2/G3. Enjoy and please send feedback. VERSION = '0.1.5' """ 0.1.5 DONE set Shade Position change using False to define which parameters to change DONE more debug on G2 so it acts as expected 0.1.4 DONE add node_queue & as result need pause updates while in discovery DONE FIRST TRY G2 tilt feature 0.1.3 DONE node discover rewrite to allow add/remove DONE add event 'homedoc-updated' currently no actions DONE limit room label size to 15 as room - shade/scene < 30 for ISY DONE clean up LOGGING.debug messages DONE G2 bug fixes 0.1.2 DONE change icons to nicer ones DONE docs with screenshots & description for udi spotlight DONE add troubleshooting document DONE add some support for G2 gateways (no gateway push, only polling) 0.1.1 DONE tap into gateway events, which allows longPoll update to move from 30s to 60s DONE active scene indications from events DONE shade motion indicator from events DONE shade position update from start, stop, online events DONE remove parameters based on shade capability (primary, secondary, tilt) DONE update readme & config instructions to highlight G3 scope 0.1.0 DONE handle multiple gateways automatically, picking primary & switching if required DONE updated configuration instructions as well as link to the forums past versions: 0.0.9 DONE fix uom for positions(100) & ids(107) DONE more notices clean-up DONE shade naming to include room as scenes DONE remove status based on shade capability (primary, secondary, tilt) 0.0.8: DONE handling of notices individually DONE polling 5s short-poll 30s long-poll DONE status for programs (positions etc) 0.0.7: DONE faster status updates when command is given DONE bug fix DONE re-order of parameters displayed 0.0.6: DONE move shade by specific amounts DONE bug fix scenes not activating 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

ok. balancing the constraints is the issue here. I have really tried to avoid the need a separate shade node type for each capability of shade. So it means the tilt selection will allow you to choose up to 100 even when on a 90 degree shade will only accept up to 49 (>49 will be changed to 49) when the SSP is pressed I am not aware of how to change this range select on the fly when I know the capability. fyi, tilt close is 0 and tilt open is 49, 100 is tilt close the other way on a 180 blind. the primary at 100 when the shade is closed is a mistake on my part. The number is hard wired when there is only tilt data available ; it should be zero. FIXED the primary not working I will have to fix by either making it have priority when its number is different than current value or having a button for each of primary, secondary, tilt. Will take another run at the former before falling back to the three button solution finally, It looks like the update "from the gods" has worked. No crashes last night. Will likely get another version out tonight then I might be spotty for a week due to kids spring break. thanks again for the help here ; I do hope that I am not wearing your patience too thin.

updated to take a crack at the tilt issue. also they put out an update on the interface. requires update of isy and a re-install of all your plugins from the menu.

Well that's not good. Yes shade opening should take priority. At one point I was going to set up a sequence for it. I will take a look what I broke and get back here. Likely something silly. Btw: : the gods got back to me. They are pushing an update to the interface library, so the good news is it's not my fault, the bad news is the fix will come later this week. Means the plugin crashes after about 5-10hrs of running.

@GTench ok dialed open back to 49 and limited inputs to 49 for 90 degree blinds (there are two types). give'er another run. See if tilt-open, & tilt-close work & the angle inputs work. What I was also curious of if the blind was half down or so and you entered a tilt angle ; what happens? Does the G2 ignore, lock-up, go down then tilt, or fall off the wall?

Thanks so much ; very helpful testing rigour. ok, makes sense. I will limit tilt according to your tests for 90 degree shades Tilt Open is not working as it sends a 50 to the tilt parameter Interesting though that the AC shows a 50 ; might be a rounding up as the numbers are really 0 - 65535 / 2 or 32767.5. I am currently rounding up & will change that to truncate and we will retest with both 49 and 50. The controller must lock-up or get confused for a bit when the > 49 is sent. Can you test what happens when you send a tilt when the shade is not at the bottom? I don't limit this right now. This blank field for tilt is because I didn't get a number from the controller, I could assume one of zero based on the capabilities of the shade or just wait until one comes through. Also possible to have a tilt and no Primary if it is at bottom. I'll take a look. Good observation. Comes from G2 using the same parameter for both values. also, I am talking to the plug-in "gods" about an issue I am having somewhere after running for 5 hours or so ; basically it crashes and the logs don't point to anything actionable in my plugin. Requires a reset of the plugin; more to come. So if you see the plugin unresponsive after a day ; do a reset. Not a good situation, its my number one priority to get fixed obviously but its a very long debug loop. I think I have now officially spent more time on G2 than G3 development. lol, what do they say about well laid plans? ***** ok @GTench made the updates. don't forget to delete and reinstall. please test 49 first then 50 ; I am hoping 50 will work as I changed the round-up to truncate. if you enter anything larger than 50 on a 90degree blind it will change to 50. the black tilt should be a zero for tilt capable blinds tilt open will work if 50 does & will not if it doesn't (I will back off to 49 then) Thanks again for the testing help!!

@GTench Delete and reinstall the plugin & then try the tilt open & close, I had G2 unable to use those. Also, by your text you set the tilt at a number then hit tilt open or close ; you should enter the number then hit set shade position, just like if you change the primary / secondary. Either way , please try that again now. I made a change in it too. thanks for the help.

no worries. Heading to florida next week. As you test the tilt stuff, keep an eye on it after a few days. I had a couple times where it seemed to go unresponsive after running for a while & needed a restart. Let me know if you see that. I am tracking it down now.

On a quick scan there’s nothing that jumps out at me. Can you copy in some of your devlist which work / don’t work and a log file?

I’m still on the fence; feels like it’s only worth $5.25… @Michel Kohanim I gotta ask how you backed into that number?

@bmercier sorry for my ignorance; but what does it mean to “Disable the global MQTT queue”. I can imagine what it might mean but can you expand on what this change improves upon? Thanks again for all you do!

To fill out this question as well. If you "do nothing" the defaults will result in the internal generic mqtt server on the EISY/Polisy. Some people still have mqtt running on an external device ; hence the settings are there to be used. I will add a pull request to continuously improve the docs in the plugin.

@GTench give tilt a try. I did it basic first. Let me know what happens when Tilt command is given when up or when Open command is given when Tilt is not zero. The Hunter Douglas gateway may take care of it or may just not move. Let me know.

Some clean-up which do not add a whole lot for the PowerView G3 users. Node_queue is mostly for preventing overflows when there are significant numbers of nodes being started at once. This will make the Start-up notice take longer ; be patient. Finally, for the PowerView G2 users I have added Tilt functionality. Please give me feedback as I do not know how those G2 shades react when tilted and say an Open Shade command is given. Or if a Tilt command is given when the shade is not at the bottom. Feedback & ideas for improvement is welcome. VERSION = '0.1.4' """ 0.1.4 DONE add node_queue & as result need pause updates while in discovery FIRSTTRY G2 tilt feature 0.1.3 DONE node discover rewrite to allow add/remove DONE add event 'homedoc-updated' currently no actions DONE limit room label size to 15 as room - shade/scene < 30 for ISY DONE clean up LOGGING.debug messages DONE G2 bug fixes 0.1.2 DONE change icons to nicer ones DONE docs with screenshots & description for udi spotlight DONE add troubleshooting document DONE add some support for G2 gateways (no gateway push, only polling) 0.1.1 DONE tap into gateway events, which allows longPoll update to move from 30s to 60s DONE active scene indications from events DONE shade motion indicator from events DONE shade position update from start, stop, online events DONE remove parameters based on shade capability (primary, secondary, tilt) DONE update readme & config instructions to highlight G3 scope 0.1.0 DONE handle multiple gateways automatically, picking primary & switching if required DONE updated configuration instructions as well as link to the forums past versions: 0.0.9 DONE fix uom for positions(100) & ids(107) DONE more notices clean-up DONE shade naming to include room as scenes DONE remove status based on shade capability (primary, secondary, tilt) 0.0.8: DONE handling of notices individually DONE polling 5s short-poll 30s long-poll DONE status for programs (positions etc) 0.0.7: DONE faster status updates when command is given DONE bug fix DONE re-order of parameters displayed 0.0.6: DONE move shade by specific amounts DONE bug fix scenes not activating 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

Your options are good. I use lots of 6 pads & tend to use the mains light as just that a light for what it’s attached to which leaves me flexibility for the other four lights as scene controllers and indicators, with the ability to turn on/off/dim as I please. The only exception are scenes which I treat like they are hard wired; two or three lights which always come on/off together.

here is the movement of your Foyer, after sorting your log data. I am assuming that it starts open with posKind1 using #1, then when its closed it goes to using #3 and the rest of them are you moving the tilt around. {'posKind1': 1, 'position1': 0}, {'posKind1': 3, 'position1': 30} {'posKind1': 3, 'position1': 50} {'posKind1': 3, 'position1': 30} {'posKind1': 3, 'position1': 50} {'posKind1': 3, 'position1': 0}, {'posKind1': 3, 'position1': 0},

was this your scene? (scroll to the right) 2 matches for "need to delete node" in buffer: debug.log<hunterdouglas_3-4-2024_21920_PM> 560493:2024-03-04 14:12:34,316 Thread-716878 udi_interface INFO Controller:discover: need to delete node scene40299 562064:2024-03-04 14:14:35,797 Command udi_interface INFO Controller:discover: need to delete node scene40299 unfortunately in my testing I commented out: for node in nodes_get: if node not in nodes_new: LOGGER.info(f"need to delete node {node}") # self.poly.delNode(node) glass-half-full the logic works.

@GTench really glad the G2 additions are working for you. My btw vent about G2/G3 was in no means suggesting you should update your shades for G3 ; these are very pricey blinds & my wife wants more! So appreciate you working with me on this & hope you will stay with me a bit even if we are starting to get to the end of your use case. Having someone who is willing to work with me is like gold since I only have the G3 shades. My assumptions of the constraints & unknowns are as follows (this is as much for me as I write), I will write the next version based on adding tilt capability to G2; edit them as you like: 1. G2 uses PosKind1: 3 to indicate tilt. 2. The shade first has to be at bottom to use tilt 3. The shade has to be at zero tilt to move up 4. The shade has to be told #2 & #3 ; they do not happen on their own (unknown but indicated by your experiences ; can you put a scene which goes to bottom then a tilt?) 5. I will need to move the data to/from the tilt slot based on #1 6. Somehow need to either automate based on #4 (move down then tilt or tilt and move up ) or get a message to user if the shade is being asked to do something it cannot. Otherwise open will not work & tilt will not work as understood. Let me know if any of these assumptions are wrong or you have other preferences. As first mover / tester you get first dibs!

@GTench Also, I saw your back and forth on the plugin delete. Here is how I do updates on plugins. 1. delete from the polyglot interface 2. install again from the poly store, then add back in the configuration. You often do not even need to reload the Admin console. Just if the nodes get messed up or you see the Link Management, Tools, and Help menu greyed out a bit. Just means it is not talking to ISY at that point. I almost never reboot the EISY box. Very rare. As mentioned I do this many many times a day. In fact when I am using a local plugin from the developers menu I only need to stop/start the plugin (you won't be doing those for now). Hope that helps

@GTench So here is the decoder ring: { "id": 21564, "type": 23, "batteryStatus": 3, "batteryStrength": 167, "roomId": 35121, "name": "Rm95ZXI=", "positions": { "posKind1": 3, "position1": 20538 }, The poKind1 field has a three in it. When it is primary it will have a one in it. Like you say, makes sense for this kind of shade you can only use the tilt when it is fully extended closed. And you cannot open the shade until you move the tilt back to its limits (I think you said zero). Other kinds of shades you can tilt at any state. You have given me enough to go to the next step. I can populate the tilt field when the poKind1 is three. btw: : G3 is much simpler to use.