sjenkins

@GTench, interesting, I have it loading 60 & 600 on installation. I’ll have to look. the 60 is the update cycle for G2. please try that as it’s less likely to overload your gateway.

@GTench, Thank you for the logs, I looked at them & in general they look good with no obvious errors. Can you verify you are using a shortPoll of 60 and longPoll of 600? Any chance of a race in your programs? Have you changed any recently?

Thanks for all the work ; putting my plug in for the last one on the list (I know you know)

the connected / disconnected is a feature of udi by adding: self.poly.addNode(self, conn_status='ST') Allows easy tracking. Not sure when that was added by the UDI boys ; I just added it to this. NOTE: So this means you can use the STATUS of ST to check for connected status. But in addition, this plugin (and many others) use the CONTROL of ST to check for heartbeat. Basically a program which checks in the IF section of a program for ON or OFF of the CONTROL, using the THEN to wait for a period of time, say an hour until setting an error ( I push a message using network to my phone). As the heartbeat goes back and forth the wait is reset and the error message is only set when it stops oscillating. I talk about this in the instructions but the status part is new. The creating widgets for scenes does not make sense to me. So if both are stopped does it work ok? I have not experienced that & not sure how it could effect that. Can you please send me the debug files of both the plugin and the main log of PG3. Might be best to DM them to me. If too big I can give you my email there. thanks.

you assume correct remember to tick the box by "Allow ISY access by plugin" and save.

@macjeff, the keys, "isy" , "user", "password" has been depreciated for quite a while. With this re-write I added error checking which defaults to flagging keys which are not recognised. In the configuration screen under the shortPoll , longPoll entries is a little tick box "Allow ISY access by plugin", make sure to tick that box. when you use that kind of configuration you need to enclose the dictionary in {}, {"type": "garage", "name": "VirtualGarage1", "ratgdo": "False"} will work fine for you, no limits on the number (within reason) hope that helps, & thanks for testing.

@GTench, I was using a new name checking function (which I "stole") from another plugin. Their reasonable choice (which I agreed with) was to cut from the left as that data is not as likely "unique", its the name of the room. You are less likely to end of up with a number of shade/scene names the same. As you do in the production version. I changed it back for now, but I am leaning to keep truncating from the left. Let me know how you think about it. Personally, I have just shortened my names a bit. As far as having more than one plugin running at the same time. The issue may be they are polling from the same gateway. On G3 I normally don't run them at the same time but what I find is the gateway crashes not the ISY. I just checked HTOP with three running and found it was ok ; but that is G3. Can you stop each of the plugins, and run one at a time? Let me know if you see a performance difference with production only, beta only, both. If you only see the performance drop on the beta, please send me debug logs. thx

@GTench, Good to go, as I was concerned about, during my refactoring I replaced 'id' with '_id' for G2 scenes. That's all it takes. Someday I will generate tests with my programs ; never really took hold for me. Would help in places like this, where I don't have the hardware to test. Please install in a fresh slot and give it a go. thanks again. PS: also, made a change to fix the noisy start-up before you put in your config gateway

@GTench, Made a change which should protect G2 from starting the sse client. Please reinstall.

@GTench , looks it didn’t detect g2 properly; It got there & is saying the sse server is not right. Yours doesn’t have one. can you do a restart of the plugin and give me the logs from the beginning until that message starts. I don't need it all just that. I added something to drop out of the sse client if it sees that too. I will look at the detection routine again. thanks for testing. This is the g2 stuff I couldn’t test myself.

@GTench, No I just now did a clean non-production install & all was well I have to ask, you updated the config with your gateway IP, right? assuming so, send me your debug logs please

@GTench, Sorry for the delay, fixed. The bug was in the discover routine which you have to do a clean install to find & have certain shades. I made a change before my last clean install test. My bad. Should be good to delete, re-install and check out. btw: : to all testers, please tell me if you are G3 or G2 when you give feedback. Thanks again to all!!

@GTench, Found a late dumb error in Discovery. Did a quick fix for G3, but give me the night & I will fix it properly.

Yes you can, I actually have production, beta, & development local on mine. I don’t tend to run them at the same time as sometimes the gateway gets grumpy. But nothing will blow up. you also can install the beta on top of the production, and then go back to production without your programs getting messed up. I do this sometimes too in my testing cycle. The poly platform is very flexible this way.

Should be in the non-production store.