sjenkins

@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.

@GTench I think I have it straight on open = 100 for G2, and the buttons should do what you want. Give it a try to verify. Tilt is going to take a bit more research. could you put a shade to 50% tilt for me using the PowerView app. then do below in a browser, copy it & let me know which shade it is. http://192.168.2.239/api/shades thanks.

So I may need some direction here what makes sense for you in this. Positions in G3 work like this, 100 is 100% closed. The actual numbers are 0-1 with 0.5 50% open and 1 being closed. G2 are 0-65535 with 0 being closed and 65535 being open. As you know I am using 1-100 with 100 being closed ; like G3 for the input of shade position. to 'fix' the G2 I modified the translation routines which do the move from float to int and back for G3 to handle the 6555. the latest change just reversed the 'polarity' of the G2. All that to ask, "How would you like it to work?" On the subject of tilt. Can you try 50% in the secondary parameter for a shade which takes tilt? Also let me know which ones in your set (I have your data), those are. I can do something with that. Currently nothing will happen in tilt for the G2 as it doesn't exist in the positions array. My thesis is they use the secondary for it.

Did you try an Eisy reboot? Cycle the power sometimes works. If you still get that behaviour after that try installing a different free plugin.

Try a reboot & if it’s still there delete again. Looks like a timeout error.

@GTench very good news! 1. Can you tell me which shades it is? Even better move those shades to 50% tilt open and send me the result from the browser, then close them in the direction you like (up/down) and send me it again. With that I will have open (50%) and close, and will understand how G2 does it without a tilt variable. http://192.168.2.239/api/shades 2. I was wondering when I first read the G2 api if this would be the case ; just wasn't sure. Has to do with the difference in how they defined zero which is open in G3 but closed in G2 I believe. Not a big deal to change now that it's verified. EDIT: pushed a fix for this 3. When you get rid of those scenes in the PowerView app. Do me a favour and goto the controller in the AC or go to the plugin at the polyglot V3 and hit the re-discover (AC) or discover (poly) button. This should remove the non-exist scenes (or shades). Then move a remaining scene or shade. Id like to know that the scene is removed and everything else still works. That was the feature add I worked on for version 0.1.3. Need someone to verify it works besides my own system.

@GTench , ok updated same 0.1.3 version just a bugfix

@GTench took a quick peek ; will have to fix when I get home from work. The good news: all is happening without internal errors. Its now down to getting the api right. I think I see the typos, I have been staring at this too long. When they went to G3 they did a bunch of very small clean-up changes changing singular/plural and get/put and position stuff. All good to clean it up ; so doing G2 after G3 is really messing with me, lol. The scene activation is actually showing a good 200 response but is as you say not working: interface:_handleInput: PROCESS command message {'address': 'scene40299', 'cmd': 'ACTIVATE', 'query': {}} from Polyglot 2024-02-29 14:50:00,463 Command udi_interface DEBUG Controller:get: Get from 'http://192.168.2.239/api/scenes?sceneid=40299' returned 200, response body '{"sceneIds":[12315,2048,41824,62186,34488,11179,50898....... the url should have "scenes?sceneId" not "scenes?sceneid" while the shade: Controller:put: Put from 'http://192.168.2.239/api/shade/21564' returned 404, response body '{"message":"Not Found","error":{}}' the url should be counterintuitively "shades" not "shade"

@GTench ok found some time. Scenes: changed to PUT Shades: I fixed a stupid labelling error in the JSON Let's go Oilers!

@GTench , had a busy/late day yesterday so I didn't get to a new version but did spend 10min on your logs. For the scenes I do have a next step. In the G2 api document I have they are saying that scenes are activated with a GET, which is different than G3 where all motion is with a PUT. I will change that and let you know ; likely not until tonight. Not currently sure why the other motion is not firing. Likely something else subtle in the differences. Thanks for joining me in my debug cycle ; might have been faster for you to mail me your G2 for a couple of days. lol. take care

A few refinements. I re-wrote the discover routine so that it was smarter & didn't duplicate nodes for shades/scenes and also knew to delete ones it couldn't find. If you get too verbose with your naming it is easy to use up the 30 characters ISY allows you, so I limited the room text to 15 chars, giving the balance to the shade/scene name. Could make this a parameter or even more cool make the shades/scenes nodes children of the rooms. In the background I have reduced some of the debug logging which I more needed during development. Finally I have been having fun with a willing victim to develop G2 capabilities without breaking G3, thank you @GTenchfor your patience. We now have nodes, and soon I am hoping movement for the G2 users. Feedback is welcome! VERSION = '0.1.3' """ 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 FIXME G2 bug fixes add to future version: TODO bugfix & test 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 I put up a new version as there have been some developments for both G3/2 I think I found the bug in the update routine. I also cleaned up the Logger.debug a bit to clear out the noise. thanks again

Well we are up and running! You are right the names are truncated by the AC side of things. What I could do is limit the room text to something smaller so you are more likely to get more of your shade/scene name. A more complicated version would have the shades / scenes nested under rooms. I have never done that so I would suggest we start with A and put B on the todo list. You also could be a bit less verbose in your naming 🤪 Once I get done my meetings I can take a good look at the logs and figure out why you have pretty pictures but nothing moves when you tell it to. Once again, thanks for going on the G2 journey with me. btw: : in parallel I have been working on some other improvements to the discover routine. Basically, from others I am incorporating best practices from other plugins. Because of that the next debug cycle may have a version change unrelated to this debug cycle.

@GTench Thanks for sticking with me & for the logs, they are invaluable. G3 & G2 have different ways of communicating their JSON data. G3 uses a different label for room id, versus shade id, versus scene id while G2 uses 'id' for all of them. I thought I got all the spots where I was referencing them. I didn't. if you are ready for another try I just testing G3 and didn't break anything. You will want to delete and reinstall the plugin to keep it clean.

Not putting out a new version as PowerView G3 is unaffected. Going to work on the PowerView G2 to get it functional with the users who need it ; and unlike me have the G2 boxes. Always open to Bugs or Feature requests.

@GTench so first, your logs were extremely helpful for a few reasons. It allowed me to see what the G2 gives back for data REALLY in the wild as opposed to the api document (not written by HD). There were some differences. The issue which crapped out my program is G2 only sends the position parameters the shade needs. The G3 sends back all of them whether required by the shade or not. You know what they say about assumptions. So this meant more than you would like that to mean for the program. Should make it more solid. I tested G3 and nothing seems broken by my changes. I may eventually need to write a test program. I did not put out a new version, just a bug fix. I would suggest you delete and re-install the plugin. I expect two-steps forward and one-back ; send me the logs ; thanks again for your help.

@GTench thanks so much for giving this a try. I’m on my phone at my daughter’s hockey game right now so I’ll have to get into depth later. But a Quick Look is good news!! it found your controller and verified it was G2 ; it just didn’t dissect the data into shades and scenes like it does on G3. It is likely just a JSON mismatch ; if you don’t mind being my guinnea pig & a bit patient I am sure we can get there. Hard to debug at home without the hardware since I never do anything right the first time. 😜 With your feedback it will be good. btw: startup notice just means it launched and is setting up. That goes away at the first longPoll

Either in the YoLink app in the automation you can add the delays and/or you could write your ISY program to do the same.

new version 0.1.2 incorporates PowerView G2, I don't have one so there may need to be some refinement.

So the big item here is the documentation improvements both before and after @Michel Kohanim was so kind to spotlight my plugin. This is one of those few online communities I have come to enjoy because 'nice people' reside here. Not many of those on the internet these days. Additionally I prettied up the icons. Finally, due to "popular" demand (you know who you are @GTench I broke one of my starting precepts and added functionality for PowerView G2. Events are the main thing you lose here, only updates by polling. Additionally, tilt if it is a feature of your shades, comes through the Primary variable ; let me know if so. All I can say is I have not broken PowerView G3 functionality ; I give it a 1 in 10 chance that it works due to the fact I am writing code based on a non-oem api document, so I need good feedback & Logs. I also found out that PowerView G3 users need to make sure to set up their account and home in the PowerView app. Likely done during dealer installation. While this is a local api it needs that step to enable the gateways by adding a HomeDoc id to the gateway. I added a troubleshooting document accessible from the config file and the readme file on my GitHub to help to identify this. Thanks for those watching, it's been a bit of fun on my side. Stephen VERSION = '0.1.2' """ 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) add to future version: TODO bugfix & test 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 """

Hi Josh (and perhaps others Good news your pic was perfect & will help me with future users. I had made an assumption that normal set-up was completed in your hunter douglas app. for others, I had Josh goto a browser and enter: http://ipaddress/home for each gateway I will likely add this to the instructions as a 'test if you're ready' step - As shown above, this is truly a V3 gateway hub but it is not your primary. - this is also a V3 gateway hub, and is very likely your primary - Ithe HomeDoc is not something that the user needs to 'have' or edit but is on the gateway if it has been connected with a Hunter Douglas account, and a Home created. ... from the HD Docs: " Note: If the Home does not have a HomeDoc, all /home APIs return statusCode 503/SERVICE_UNAVAILABLE until the Home is correctly configured and a HomeDoc is successfully retrieved from the Cloud" - HomeDoc is created when you run the PowerView App & create an account and then a "Home", this should have been done for you by your installer. Mine was not very tech savvy so I did it for him. - you need to download the HD PowerView app on your phone - If you have never run the app before there is a Setup Wizard which will run out of the box and allow you to create an account and then a home - If you have run the app before and do not have a home created you can go into the More area in the bottom right, which will come up with a screen you can pick Set-up Wizard from. - I would do a restart on the plugin after you complete the HD app process - If you want to check yourself after you complete the app HomeDoc process then enter the http://{ip of the gateway}/home again into your browser, you should receive a JSON text with a whole bunch of data - This is part of the 'normal' set-up when you get the blinds but I can see where some installers didn't complete it. You can still see the blinds on their app if you don't create this link, you just cannot do much with the api - Also I am going to add some diagnostics to the plugin and the above help to my documentation

Feel exactly the same way. I have played around with so many z-wave items and left really unsatisfied. The Insteon are really good at switches. These yolink are great at low speed temp/humidity, leak sensors, and valves. Now I'd like to see them get the local api they have been promising for a while on their web.

@Michel Kohanim could you flush this out a bit? Does this mean it will copy your current system back to the Mme 50G and then after reboot allow you to run the new script with its features. No guarantees in life I know but is this a path for those of us that went in the deep end with the first version to resize our new drive? Sorry, the text seems to be saying this but obviously I would like to be sure. Much appreciated.

Hi Josh, Appreciate you sending the logs, could you verify for me what you put in the configuration? Perhaps a screenshot. Second, maybe a pic of the hub to verify version (not the bottom with your serial numbers) thx.

Love the ability to add a custom icons from url for default & love the ability to configure advanced status' Could we add the ability to add custom icons not just as the default icon but also in the advanced status area? Not as important but as a convenience it would be great to pull icons from local files in addition to url's Thanks @Javi & udi team for all you do!