sjenkins

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

@vspete , this should ping you this time. if you send me, PM me if you like, the results of these url's I may be able to find the issue, and make the plugin more resilient, for others as well. http://{g}/api/shades http://{g}/api/scenes with {G} being replaced with your gateway, 192.168.46.37 from above if still the same.

So, looks like you have one G2 gateway & it is good & it is finding a list of shades & scenes. Your lists don't look quite right. Do you really have 14 rooms in the app, with only 4 shades and 10 scenes? So you either really have 14 rooms and the plugin is not finding all the shades/scenes or the app has a bunch of empty rooms which may be messing up the sifting of the arrays I don't have a G2 so all my troubleshooting has been with a few users; I need to ask some questions. Can you look at what you have in the power view app and report back what's there. Even feel free to delete rooms or scenes you are not using. Let me know what are the numbers of rooms, which have what shades. And the scenes you have. Also if you are using the multi-room scene option (the scene spans rooms). thx

Exactly. The standard valves are really cheap & I have had good luck with either Rainbird or Orbit. Easily replaced as well. The 24ac is standard as well as a coil of the cable to bury. Amazon or even HomeDepot in a pinch.

I have used OpenSprinkler for over a decade now (really the plastic is yellowing). It’s an open source dropin & can handle dc or ac valves. Added two valves for the deck plants and one for filling the pond. Solid PG3 plugin by @Javi btw: they have put out a number of new versions since mine.

You might take a look at some of the Yolink robot valve offerings. They get into tighter spaces than the Titan but still are gear driven for the torque you need. Have been using it for a number of years with real life tests. The yolink leak sensors can be direct linked so even with no mains power / WiFi will respond to a leak event.

Good deal @EWhite , appreciate the update! you mentioned 'a few issues earlier', would you mind marking this as solved and add those issues to the stream for v3.1.11?

Thanks @EWhite for keeping us up to date on the journey. I am sure this was not on your agenda for tonight to work on. Sorry about that.

I have not seen that error before. Searched around on the forum here & found it on the notifications plugin. Looks like a reboot solved it.

When you say “it” shows, do you mean the logs on pg3?

Moved to production all the rewrites. Functionality improvements for switches and temps are really down to quicker updates. Back-office was significant rewrite/simplification of the code and docs updates. Minimal feedback from the betas on anything breaking ; thank you to those who tried the beta out. On this plugin I am slow to move from beta to production as it has been so stable for so long (maybe too stable). I don't want to break anyone's setup. The Garage device now will read/write from variables or Ratgdo read/write & write to vars if you want. It is event driven with polling on the longPoll. I am thinking of going all events with a poll for the Ratgdo to send current status to the events on the longPoll. Warning putting in an IP address makes boot much quicker as the Bonjour timing seems to be random on the EISY. If anyone starts using this please let me know. It is in full use for me for the last number of weeks but there are lots of set-ups out there. Do I give you the info you need from the Ratgdo? There are lots of fields I don't bring over. Let me know. Didn't get any feedback on my question of moving the variable setups for the Temp devices to configuration (JSON in config or YAML file), like the Garage device. I would add another device with this capability for users to try out. Advantage is it would mean config is immediate rather than forcing one to goto the Admin console to set up, as well it cleans up the Admin screen for the device. Let me know your opinions. Feedback, feedback, feedback. VERSION = '3.1.11' """ 3.1.11 DONE poll on longPoll, events sse DONE add motor, door position DONE update docs TODO Bonjour discovery is sometimes slow 3.1.10 DONE rewrite switch, dimmer, temp, tempc, garage DONE docs DONE move db files to subfolder 3.1.9 DONE Garage device read status directly from Ratgdo through ESPHome RESTapi DONE update docs for garage Ratgdo integration FIX switch st uom from 2 True/False to 25 On/Off 3.1.8 DONE Garage device sends commands directly to Ratgdo through ESPHome RESTapi DONE Bonjour discovery of Ratgdo garage device 3.1.7 DONE Small refactors DONE redo environment 3.1.6 FIX better solution to markdown2 issue 3.1.5 FIX repair docs due to markdown2 issue 3.1.4 DONE docs updated for garage 3.1.3 DONE: new device 'garage' door (update to/from variables option) 3.1.2 DONE: ISY name changes based on updates to config / YAML / JSON 3.1.1 DONE: YAML file option for configuration DONE: JSON option for web based configuration DONE: Discover button to update based on config updates 3.1.0 DONE: move version history out of README to own file DONE: update docs 3.0.1 DONE fix get value from variable 3.0.0 DONE add control ability to contact device DONE refactored to modern template previous updates: see versionHistory.md """