sjenkins

Minor debug and name change to HunterDouglas per naming standard. Means it will show up on the store list in proper alphabetical order, instead of near the bottom with the old hunterdouglas name.

Installed and the new features are working, thanks Benoit!

Upgrade & reboot worked as expected. Attempted a name change on my plugin & no joy. Stayed the old name in the store and back-fed the old name to the developer list, but my changelog did update. @bmercier I will also put in a ticket.

I’ve gotten so frustrated with the mqtt version I abandoned it & put home assistant on a pi. I have no use for HA otherwise. I am now backfeeding to the ISY the variables I want. Pain in the a** but it is working. certainly not the recommended solution. My next step was to figure out how the HA protocol works. Sounds like a time sink. I would really rather they just fix the mqtt version. Seems like he knows how as this esphome version is bulletproof.

@GTench Not currently as it makes that choice at the start. Would require some rewrite, and a tester (hint hint). No reason it can’t be done, I just don’t know how the gateways operate together or are talked to separately. Might make more sense just to run two instances of the plugin. There isn’t any other cross talk between blinds. You could make your own scenes in the ISY. I’d be interested how their app handles it.

So, to the meat of it: The plugin should change based on what you modify in the PowerView app names in addition to adding/deleting shades or scenes. I added this after cleaning up mine a bit & realising I wanted it. We are getting 10 more shades in the next month or so. Most of them will have secondary axis as most are double rollers. One also has the header move up/down. Should be able to test some new types.

So 10min after I made my change it changed the name back on mine too. Go figure. This is why I wanted to change the name of mine from hunterdouglas to HunterDouglas the lower case gets sorted to the end I will ask the Discord development guys on how best to change it. btw: : Sorry if by doing this I messed up your programs (this was more frustrating than any issue so far, arrrrg)

Can you refresh your store?

ok , so did something kind of severe... I have been wanting to change the name to HunterDouglas since about the beginning to match the naming convention and make the plugin easier to find. so I deleted the old one (still shows in list but no install option) Shows in the store further up the list as HunterDouglas and version 0.1.8 Works on mine but if this doesn't work I don't know any more nuclear option.

ok I went to 0.1.8 and it seems to be sticking ; so weird

wow ; went to mine & it showed 0.1.7 did a refresh of the store and it reverted to 0.1.6 let me do a new push to my GitHub and see if it sticks... if not I'll have to put a ticket in.

either delete and reinstall or if you goto the plugins production store you can manually update there.

I had some really odd stuff happen. Had to resave my developer upload to get the 0.1.7 to stick three times. Just redid it this morning so you may want to try again. The resaving of programs I have heard of before but only with other plugins.

@GTench updated properly now ; had this happen once before, the production updated on mine then reverted back in my developer screen. thanks for the heads up.

Added feature to automatically update node names when they are updated in the PowerView App. Will update within the next long poll and/or during restart. VERSION = '0.1.7' """ 0.1.7 DONE rename nodes if changed in PowerView app past versions: 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 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 Great testing job! I have seen both of these before. Both in my plugin and others. You can hit second mouse button and group to bring it under the tree. I will go through the logs to see if the error shows anything either I can change or feed back to UD. I also want to go through and see about the double button item. That could be irritating but more importantly matters if it happens in a program. There is no feedback other than a http 200 that the command went to the gateway. I'm interested as you start using the plugin in programs how it fairs. So... what do you think? Anything major still on the todo list / wish list or are we in pretty good shape?

I have same setup & have had the issue “sometimes” but not all the time. wondering if my plm got grumpy if the power came back with noise or voltage drop.

@GTench I pushed a fix for the setShadePosition buttons. All looks good. Seems to be a quirk of how the nodedef profile works. Had to remove the flag for optional so that the shades which only had one parameter would function as expected. I am assuming that it was deciding that it was ok to put below if no parameters are "needed". The discover function seems to work ok (at least on G3) if button is pushed after a change and without a plugin reset. I need to do some more testing. While playing around deleting and installing the plugin with my testing ; the odd time it didn't find all nodes & needed pressing a second time. The last thing on my todo list is exclusive to G3 & has to do with cleaning up the events routine. G3 pushes events when the shades move or a scene is activated. I want to make sure that routine is bullet-proof. Please do your normal battle testing on the plugin ; you will likely find something else. The list is getting shorter!

@GTench Thanks that gives me something to go on for the ssp button. I will check the discover function. Looks like deleting nodes is not working for G2. I tested successfully for my G3, but that was a while ago. Perhaps I broke it. It only fires the discover routine when the parameters change and when the discover button is hit on the AC Controller node or the polyglot plugin screen. So its intended function is not to fire on normal start-up or reboot. I was afraid that if a gateway was not found that it would delete a bunch of nodes, so made it pretty manual and purposeful.

@GTench Please enjoy Easter with kids and grand kids ; we are heading back to the north on Sunday. Ignore this until you have time. if you delete a scene or shade it is supposed to stay there until you hit discovery or if you reboot the plugin ; it should remove them. I'll run through it again. So glad the tilt is working now ; was another oversight of mine. Can you clarify your statement above: does the SSP button not show up below on the tilt shade. I am trying to figure out why those buttons sometimes show below and sometimes don't. lol. I do know how to make that bottom button work but I don't know why it works different and I'd love to just remove it. Seems like a duplication. On the G2, you are the reason I was able to develop it ; your testing rigger made it happen. btw: it also mad my G3 better along the way. I know I could charge for it & I might, not really the reason I wrote it. Mostly because I wanted it and as well for the challenge. I do know that you are not going to be paying for it.

Just reading about a joint board between Silicon labs & Arduino. Arduino-nano-matter-board i will for sure be getting one to play with. This is a board for us to play with. Its main purpose though is to end up in other devices.

@GTench ok per previous I pushed a bug-fix which should resolve both the tilt-open/close issue and the discovery failure issue. You should not need to make a scene in every room to work, that was just a side effect of the issue. As far as the bottom SetShadePosition button. Why did that all of a sudden start showing up?!?! I am comparing to my RGBW node in the MQTT server and it's the same. Maybe a side effect of how I am doing inheritance with the node structures? More research required here. And ya it doesn't work the same as the one above as it doesn't pass the parameters onto the node. Why?!?

@GTench So went straight to your scene issue which turns out is not a scene issue. Looking at the data the last shade being discovered had no data for positions in the dictionary. positions = {} so my discovery routine failed and never got to the scenes. later when you added scenes that shade started to behave and hence your thesis it had to do with scenes. Let me look at making discovery more resilient. Also the tilt open seems to still be and issue. could you use the PowerView app and tilt your shades completely open. Can you tell me the number that is? should be in the range of 32000 - 32200 I believe. Forget this. Found the issue. has to do with prioritising the primary to the tilt. btw: : you are doing a great job of putting this plugin through its paces! Your logs are SOOOO helpful.

@GTench ok, found the issue. I've tested my G3 and all looks good. Delete & reinstall the plugin. No need to reboot EISY, just close and open IoX Launcher. Thanks again!

@GTench I will take a look; might be a day. Odd as I tested out with my G3. Wouldn’t have thought these changes would have broke just G2. So to be clear the status screens are working but the controls are not, correct?