sjenkins

@zGuy981 good to hear. If you wouldn’t mind post your log here. I’d like to take a peek & may optimise.

@zGuy981 , thanks for finding this & the explanation. I did find the issue. Give the Beta a try & let me know, if all is well I will push to production if all is good , when I get back home next week.

@zGuy981 I’m travelling through mid week but will take a look at debug a bit today. I may have a few questions as on first read of description I am not quite following everything, but I’m in my phone.

Some debug for my G2 friends in the last two versions. Had to do with polling & with a left/right shade which has a very unique JSON coming from the gateway. Other than that, it's been quiet out there so I assume everyone is happy. I personally have this plugin in constant use with 14 shades and about 20 scenes. My programs are written to during the day move them around using scenes. Scheduling of those move is done in my programs & updated from UD Mobile. When I manually move a shade I usually use the HunterDouglas Powerview app, or in room remote. This plugin has my use case covered, so I do not have any feature map in the works. I am open to good ideas from the user base, but if none come along then I am in really in debug mode when/if they come along. Let me know. VERSION = '1.12.4' """ 1.12.4 DEBUG Gen-2 make a default capability if none exists in JSON 1.12.3 DONE G2 Scene event fix 1.12.2 DONE add shade-offline event handling to error log; currently not passed to ISY DONE add updating of scene activation status on longPoll as backup to event 1.12.1 DONE environment updates DONE small refactors 1.12.0 DONE change versioning to align with workflow DONE update docs: README, versionHistory, logging for previous version see versionHistory.md """

Great to hear! I’ll push it to production.

@zGuy981 Ready for you to give it a try ; its in the beta area same version, just reinstall 1.12.4 Appreciate your patience. I missed a second occurrence in the shade update routine. let me know.....

No worries; I’ll check tonight after hockey. Sometimes need to peel the onion a bit. I likely missed it in another spot. Thanks for the debug.

No worries ; thank you for finding the bug. I am treating this as a bug, I was depending on the variable being there and had no default if it wasn't ; my bad. So on the beta store is v1.12.4, I have checked it out locally but I have Gen-3, so would be great if you could check out and run especially this shade and make sure all is as it should be.

ok, found the issue. Your second shade in the list, 35640, can I verify that is the left/right shade? It has a completely different json structure than the others (see below if you care). The GEN-2 system did this the odd time & is a lot of what they cleaned up in Gen-3. It has no "capabilities" reference & interestingly had a "motor" reference. The capability number is what you use to tell what kind of shade you have (there are many). I just need to set a "default" shade if one doesn't exist. Likely should have that and a log I was doing that anyway, but the error does flag something wrong ; you might not have anyone let you know otherwise. I will get my coffee made and go at this. I'll let you know when I need you to test, likely in the beta first. For those who might care beyond me below is the JSONs I am talking about: Below is a "normal" shade (your other threee): Below is your "Special" one (going to assume default type):

@zGuy981, Thanks for including the all of the debug files ; I will take a look at it this afternoon, heading out for my daughter's hockey now. I see where to look & may have a question or two. Just to be clear it looks like you have four shades. They seem all the same type can you verify what type they are? (tilt, roll, from bottom, from top, both) Do you really have 18 rooms and 37 scenes defined in the app for these four shades? Not saying this is the cause but if they are not all in use then some cleanup in the app may help. Finally, are any of your scenes multi room scenes?

@vspete , Thanks for the detailed response! To answer your position False question, it is a quirk of position setting. I could have used a blank, just means you are not currently setting the position. On the topic of upgrading to G3; from what I know G2 shades are tied to a G2 gateway. Pretty sure on this but the first time I asked that question I got a different answer. I will for sure reach out if a G2 feature request comes up. Also, feel free to mark this stream “solved”. Enjoy the plugin!

@vspete , so glad it’s working for you! Also going to complement you on your quick observations, I think you picked out all the G2/3 differences. G3 gave some real improvements through an sse or event server. Sending real time events. In G3 I update through events, polling, and of course send commands. G2 remove the events. 1. Default room is the name in the array from the controller. These are not a thing in G3 and none of my other G2 users used them (or mentions them. I could substitute something else for it? Did you try them? Reason I ask is in G2 multi-room scenes were activated with a separate command. Again you are the first on using them. Let me know. 2. G2 gives me no feedback when the scene is no longer active. G3 does. Let’s say you move the shade manually, eventually all scenes would be random. So in G2 you can command activation & I leave it on for a time for feedback ease of use. Previous G2 users actually did all their movement using ISY programs. 3. Motion is a G3 event feature. Sorry it’s a zombie in G2. Design decision to use the same node for both versions. I added G2 later when I got requests. Looking back the program would have been cleaner with separate nodes. 4. Again this is how G3 shows in the app. 0 to approx 65500 is the G2 way in the opposite direction. This seemed easier. You are absolutely right to shorten the poll rate; I think I even mention that in the config instructions for G2. 5. Yay! As you can see this node server is prejudiced to G3. I originally wrote it for me and shared even with text that it was NOT for G2 ; then I got a couple requests from people willing to work with me as I had no G2. Feel free to give feedback or feature requests; as long as you’re willing to debug with me. I’ve never written a program right the first time even after 45 years of programming. Either way I hope this plugin provides some good use to you!

@vspete, from the logs it looks like nodes were created and the shades were updating. The scenes were for sure erroring. Sometimes you need to restart the admin panel & in pg3 you may have to go back to the Dashboard and back into the node to see the nodes created. Either way I added some error proofing to the G2 code & if you are willing to stick with me and install again from the beta & do a restart & send me the logs. It would me much appreciated.

@vspete , Found an error in the scene node which only applies to G2 when it is looking for events, for background the arrays have a few different labels between G2/3. This line only fires when it needs to rename the node so I am only so confident that this bug is squashed. I also think you are my first user of multi-room scenes but that will not be a problem until you try to activate one of them (one bug at a time). If you would be so kind to go to the Non-production store and install from there. We can iterate on the beta before pushing to production. Would appreciate the logs as well. Thanks so much!

@vspete , if you could send me the verbatim from those links it would be great. I’m thinking the error is from my parsing of the json array in the plugin. Since I don’t have the G2 I’m wondering if they are just different enough in your case from my other G2 tester. Maybe because of your journey with the HomeKit. Just a text file with a few spaces between them is fine. Appreciate your patience.