sjenkins

rewrite of the sse events routines for cleanliness and robustness. I will move to production if no noise in next few days

@bmercier , Just wanted to let you know that there is still a difference in behaviour between the local AC and the remote AC / Eisy-UI. Using my hunterDouglas plugin as an example as I know the plumbing: reportDrivers() does not update the detail fields in the remote AC / Eisy-UI works fine in the local AC ISY programs get the data just fine, so this is a display issue. Examples below: local AC: remote AC: remote Eisy-UI: Note: The field that did update are ones which have changed since the Eisy-UI was running. The remote AC are blank as I had to restart it to switch from local to remote. When I press query it runs the reportDrivers() function. This updates the local(if needed), but not the other two remote versions. Again the programs run fine.

Both 1.12.5 & 1.12.6 moved to production, thanks to @glarsen for the last minute change is the reversal of Open / Close for G3. I did not touch G2 and need some G2 users to validate the Open / Close function for them as I do not have any. The rest of the changes made in 1.12.5 were mostly not user facing. Libraries and documentation changes. G3 changes: I did add an event for battery low but that would have been triggered by the polling info too. The motion stop event seems to not always come across the sse, so I added a timeout clearing at the next polling event. The biggest effort was a rewrite of the sse event engine ; threads necessitate this being non-standard but the way I had written it was absolutely awful to look at. Significant simplification & clean-up. I am hoping some of the mystery crashes will go away with this. I have changed my polling to every 120s to lessen the traffic. Did not change the default though ; you may want to play with it. YMMV. Let me know what you see! VERSION = '1.12.6' """ 1.12.6 DONE reverse open / close behaviour for G3 shades 1.12.5 DONE re-write SSE for G3 DONE fix motion if motion-stop missed DONE battery low event added for G3 DONE force updates to server (helps with new eisy-ui) DONE doc clean-up DONE string clean-up DONE improve logging DONE bumped requests and urllib3 versions

@glarsen so you are right! I can say that I have open and close reversed for G3 ; open should be 100, close 0 position. TODO: can someone who has G2 can check if Open / Close works as expected? When I developed it, the G2-API has open as 0 and close as 100 ; the opposite of G3. I only have G3 blinds. Not sure how I messed this up or how you are the first to notice as these lines were committed in Jan-2024 ! @glarsen you win the observant user award ! The rest of us should hang our heads

Thanks for the heads up. Haven’t changed anything recently & I mostly use Activate. Maybe I missed something in my test procedure. You are the first person to notice if so. I’ll check it out and get back to you.

I forget to mention my devices working on the local-hub: leak sensors power failure temp indoor temp/humidity with display outdoor temp garage control & sensor water valve control

Got it. My only request then is to have retention of the expand/contract from session to session, otherwise this is a royal PITA. Oh and my ONLY other request is to allow us to move and expand/contract with our cursors like the AC. This using the mouse to move one down is killing my Emacs-fu

Thought I'd start a topic under eisy-ui for beta minor observations, @bmercier please take in the spirit of constructive feedback, as well know that each of these items will have a different priority to you versus me. Maybe others who are helping test can add their observations here. - noticing if I leave the eisy-ui web page up overnight it stops updating ; even if I do a refresh of the page it does not update with no real indication of "heartbeat"; takes a logout/login. Was wondering what the timeout period was? Is there a way to do a heartbeat? - have been noticing differences between the status on the column view versus the detail view. A refresh does not always fix it. Again have needed to logout/login. - the folder retention of expand/contract has been mentioned but also you cannot search for a folder name and then select it to have it open its contents - really, really, would like to be able to use my cursor controls to move up and down the list ; contract/expand folders. As a keyboard user the use of the mouse to move one up or down is maddening (personal rant) - during search as I start typing I am still getting an 'unexpected application crash' regularly. refresh of page often resets but sometimes requires a logout/login cycle.

Been running the Beta local exclusively for a week & have my programs set that way. Seems to be running quite well, with no glitches. Let me know if there is anything specific to stress test.

VERSION = '1.12.5' """ 1.12.5 DONE re-write SSE for G3 DONE fix motion if motion-stop missed DONE battery low event added for G3 DONE force updates to server (helps with new eisy-ui) DONE doc clean-up DONE string clean-up DONE improve logging DONE bumped requests and urllib3 versions Mostly a clean-up version & debug. Some reliability for G3 events. Putting in beta for try-out and comment ; will move to production in a few days if no issues. You can find it in the beta / non-production store.

So I will close this out with this is not a plugin issue, it was a gateway connectivity issue. I ended up adding another gateway device so I had one in each room. Solved the issue. Seems the gateways do not recover well unfortunately.

this folder issue was brought up a while ago in the alpha. the response was that the fix comes with the next major isy update (perhaps the one @bmercier refers to above coming next week).

did you try substituting eisy.local for your local ip adress? that works more consistently for me

@bmercier first, thank you for taking the time to explain the plumbing a bit. Not only helpful but very interesting. Second, you are right I was not forcing when sending my updates, I had left the defaults. Changed that and all of a sudden I am updating just fine in the local dev mode to the eisy-ui. Not sure if there is any penalty for this beyond a bit more traffic and time; but I cannot observe any side-effects. self.setDriver('GV6', self.shadedata["batteryStatus"],report=True, force=True) (the report=True is already default) I will go with this method for now. Thanks again. I will move to the new forum, but thought I should close this out here.

Installed 0.5.8 All looks good. Couldn't tell from the version notes what I need to specifically test. My issue with the local plugin is very odd. A few fields are updating on some of the nodes, but only a few and not real-time. I get this is much lower priority, let me know if it gets to the top ten list.

Hi Emile, since @TriLife is travelling I will jump in, You are close, you data is just not where the node is looking for it. Attaching a link to the relevant node and a screenshot of the part of the program which is relevant (I wrote this device a long time ago to get the temp for a fish tank and the lake) https://github.com/sejgit/udi-mqtt-pg3x/blob/main/nodes/MQds.py If you look at the topics its getting the data, its under the sensor id topic and under that you need the Temperature variable. So basically just add another layer. I know this seems odd for this device but many of the other devices have Humidity, heartbeat, etc. Temp is fine as the device choice. Many of the devices added were not Sonoff as that was my original use case when I added them to the original plugin, @TriLife has brought the focus back to Sonoff as that is his use case. If you want to learn more about the different devices like raw and Analog, take a look in the python scripts of the devices in the plugin from the github link above. You mention you are programming in python so shouldn't be much of a stretch to figure out what they are doing. Hope this helps

@bmercier you are correct (of course)! But you gotta share how you came to that conclusion.

Its my HunterDouglas plugin. The shade updates are not showing up in the local version of my plugin. It sits in my home directory under a folder with admin/admin privileges, while I see the cert/key files have admin/polyglot ownership. I am seeing a couple of the nodes which have had 'action' go true in your status column (which is nothing to do with the details of the nodes status, that is all blank). AC looks the same unless I log in local. Yes it is strange.

@bmercier , sorry I wasn't clear. When I log in the AC on port 80/443 with portal credentials the developer local nodes do not update & stay mostly blank ; same on the browser eisy-ui. Log in the AC with port 8443 with local credentials and they update. This is just for nodes on locally hosted plugins I am developing, no issue if I run it beta.

@bmercier Not sure if its a known condition but the status for nodes from my local plugins, which I use for development do not show up in the eisy-ui or the AC when I log in with my portal login. They are mostly blank. When I use the 8443 port and log in with my local login the status in the AC updates. Bit of a fringe case I know but I banged my head for an hour before I tried to log in with the local AC.

That made me laugh! (and I will use the Alexa equivalent with my family)

Two Three questions/observations: Unlike other node servers where the controller shows off-line when stopped I see that YoLinkSetup stayed "On-line" when the nodeserver is stopped. Is there any other indications? the speakerhub shows up as a device on both the nodeservers. Local hub does not show as a device in the AC but does in the configuration (it gets added automatically). Any plans there? will the speakerhub respond in local mode with the internet gone? Obviously I will test this, it cannot be added to the local network in the local-hub but it is on the local network.

So far testing of the beta plugin is good. Added my devices to local hub and starting to use its plugin as main. What I’ve done to skirt the slow update thing is stop the production (remote only) plugin. I’m putting in my ISY programs so they can use inputs from either plugin based on which one is running. this should allow me to survive as @Panda88 works his plan towards production and maybe one plugin to rule them all. I use YoLink for Leak sensors, temp/humidity, garage, and water valve. They are great for those things. So far I’m a happy chappy , I’ll let you know as I see issues, but so far so good. Going to pull the internet next & see if the point of this whole endeavour holds true.

@Javi unfortunately the new version, 1.2.12, is still crashing when I edit any favourite and try to change the display status. Rebooted my phone and thought it was going to fix it as the picker came up but then crashed when I picked. Next time crashed as soon as I chose display status. Both with old and new favourites.

I added one temp/humidity sensor to the local hub. Looks like that’s all you do is add it in those settings. Back in the app’s device screen there was now a symbol in that devices’s square like an Ethernet symbol. When I checked the node on the plugin there is a field for type of connection but that was blank for this and all the nodes which were added. @Panda88 is this a future feature? My next steps in testing was to: 1. simulate internet down and see what works. 2. Move more devices over 3. Move my programs over & disable the old ones. 4. not with plugin but was going to play with the local automations. Might still use those for the leak sensor to house water valve. question, is there any value to the old hub now except that it has a speaker (understanding we are still in beta on this plugin, so post beta)? are there any “duelling banjos” problems with two that you have seen?