RFulton

hi, I'm far from an expert (my this is my first plugin), but here is my understanding: It should install basically the same way as a normal PG3x node server; there isn’t supposed to be a separate special flow just because it’s in the non-production store. after clicking install, when you go back to dashboard you should see this ScreenLogicCTL(N) show up in a new slot, then you can configure it, restart it, etc. If clicking Install does absolutely nothing, that’s usually a PG3x/web UI issue rather than something specific to this plugin. I’d try, in order: hard refresh the PG3x page and try again sign out/in to PG3x try a different browser or an incognito/private window

thanks for the update and helping test this thing! i dont have a spa, so its a bit tricky for me to test this out. from your pentair app screenshot may 30th, it looks like you have automated pool valve controlled via thermostat logic inside the pentair easytouch system, as well as a different spa automated pool valve controlled via thermostat logic inside the pentair easytouch system. i fixed that duplicate thermostat from your last screenshot, and i updated the code to try to opttionally allow you to add a secondary spa thermostat, please delete everything and setup the variables again, note the changes 1) no more support of _solar_thermostat, now they are named *_pool_thermostat variables, and also a new variable for trying to detect the secondary spa thermostat using this opt in: OPT_show_spa_thermostat=true if the spa thermostat doesn't work, please send log file when it misbehaves.

FYI.. to anyone pulling latest updates... i recommend going through the following sequence to get updates to cleanly show up: 0) close the IOX gui on desktop 1) in polyglot dashboard delete the plugin 2) go to "plugins store" -> non-production store 3) click/install the sceenlogicctl plugin, i always pick a new slot # in the pulldown menu due to occasional IOX caching issues 4) a fresh install will reset the default configuration back to wrong ip and wrong pentair number. fix those to correct settings, then RESTART 4) then open IOX gui on desktop and you should see all new stuff

latest code updates based on your feedback today: tightened the plugin’s production behavior and UI. removed the automatic F1:11:11 lab-mode trigger, renamed the user-facing Solar Thermostat node to Pool Thermostat, simplified feature nodes to plain switch controls, cleaned up a lot of missing Admin Console labels, and constrained the solar thermostat to an Off/Heat model with a 45..95°F setpoint range. also made startup/error states less misleading by changing the shared default pool/thermostat values to zeros instead of believable fake temperatures, and documented that all-zero values usually mean the ScreenLogic host or Pentair system identifier is wrong.

also, please check that your configuration is using your real ScreenLogic system name/host values, not the placeholder Pentair: F1-11-11, and that no experimental thermostat options are enabled in the plugin Configuration; if you reinstall after that on the latest build, it should come back with the normal pool/solar nodes instead of the lab nodes.

thanks for feedback. I fixed the "I'm not getting updates into the plugin when changes are made outside the plugin", if you pull the latest version you will see that the status of devices will update each shortpoll interval. also device status can be checked within IF statement programs now. i only have solar heating in my pool, so i will look into spa setpoint but i dont have anything to test against, let me know if you see something in the log file that you can send me, so i can try to use as a way to interrogate the node server with, but w/o a spa it might be hard for me to get it working.

hi, heads up... I ran into two issues with the Kasa PG3x node server while adding a manually configured Kasa device across subnets/VLANs. My eisy is on 192.168.77.x and the Kasa device is on 192.168.1.x. Routing/firewall access was working, but manual device discovery exposed two plugin-side issues. i was able to local patch, but not sure if these are robust solutions. Device tested: HS103 plug Issue 1: Manual device discovery failed with: Controller.discover_single() got an unexpected keyword argument 'address' In nodes/Controller.py, addmanual_devices() calls: self.discover_single(address=mdev['address']) but discover_single() is defined as: async def discover_single(self, host=None) Changing the call to host= fixed manual discovery. bingo! Issue 2: After discovery worked, the same manual device was repeatedly added as the same node address. The log repeatedly showed: Adding manual device 192.168.1.28 Got a DeviceType.Plug: <DeviceType.Plug at 192.168.1.28 - OfficeFront (HS103)> interface:addNode: Adding node OfficeFront(1027f5226cb2) Adding a duplicate guard in add_device_node() to return the existing node from self.nodes_by_mac or self.poly.getNode(cfg['address']) stopped the repeated addNode loop. After those two local patches, the device was discovered and controlled successfully from IoX. I filed separate GitHub issues for the two bugs: https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/25 https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/24

hi, ScreenLogicCTL is now available in the PG3x Non-Production store for wider beta testing. This plugin is for eisy systems using a local Pentair ScreenLogic controller. It currently supports: - live ScreenLogic connectivity - dynamic feature/circuit discovery - solar thermostat support - safe queued command pacing - mode-based configuration Mode values: 0 = simulated/fake mode 1 = live read-only mode with polling 2 = live read/write mode without polling 3 = live read/write mode with polling I am especially looking for testers with different Pentair/ScreenLogic equipment layouts, including: - solar vs heater setups If you test it, the most useful feedback is: 1. a screenshot of your ScreenLogic Config app circuit/equipment setup 2. the custom parameters you used (with any sensitive info removed) 3. PG3x logs if something appears wrong 4. notes on any missing, duplicated, or misnamed nodes This is a beta release in Non-Production, so behavior and configuration may still change as more real-world systems are tested.