sjenkins

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

I use a lot of Eufy as well. Haven’t really looked into an api if it exists & the possibilities. Are you thinking of triggering off of motion or human detected?

This question intrigued me. With some quick searches it looks like Sentrol has some wired devices which will handle a room for $15. They of course are meant to hook to an alarm planel, but your contact input should be fine as well. below is not a link just the device I followed to purchase and also found a pdf of its manual. Could be a fun project SENTROL SHATTERBOX 5705-N ACOUSTIC GLASSBREAK SENSOR

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.

@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