Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

RFulton

Members
  • Joined

  • Last visited

  1. 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
  2. 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.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.