jkosharek

@Goose66This is what I am seeing in the logs: PG3x Version 3.2.4 Frontend Version: 3.2.4 IoX Version: 5.6.4 MyQ Version: 3.1.21 2023-09-08 10:09:41,753 Thread-11 udi_interface INFO nodes:start: Establishing initial MyQ connection... 2023-09-08 10:09:41,753 Thread-11 udi_interface INFO nodes:start: Establishing initial MyQ connection... 2023-09-08 10:09:41,753 Thread-11 udi_interface INFO myqapi:_oAuthRetrieveToken: Logging in and retrieving access token via oAuth... 2023-09-08 10:09:41,753 Thread-11 udi_interface INFO myqapi:_oAuthRetrieveToken: Logging in and retrieving access token via oAuth... 2023-09-08 10:09:44,834 Thread-11 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-09-08 10:09:44,834 Thread-11 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-09-08 10:09:44,891 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-09-08 10:09:44,891 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-09-08 10:09:57,343 Thread-18 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:09:57,343 Thread-18 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:01,578 MQTT udi_interface.interface INFO interface:_message: Successfully set tc00019507633 :: GV1 to 1 UOM 25 2023-09-08 10:10:01,578 MQTT udi_interface.interface INFO interface:_message: Successfully set tc00019507633 :: GV1 to 1 UOM 25 2023-09-08 10:10:01,692 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: ST to 0 UOM 25 2023-09-08 10:10:01,692 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: ST to 0 UOM 25 2023-09-08 10:10:01,732 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV0 to 485823 UOM 58 2023-09-08 10:10:01,732 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV0 to 485823 UOM 58 2023-09-08 10:10:01,772 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV1 to 1 UOM 25 2023-09-08 10:10:01,772 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV1 to 1 UOM 25 2023-09-08 10:10:01,812 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV2 to 1 UOM 25 2023-09-08 10:10:01,812 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV2 to 1 UOM 25 2023-09-08 10:10:01,866 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV3 to 1 UOM 25 2023-09-08 10:10:01,866 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV3 to 1 UOM 25 2023-09-08 10:10:01,906 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV4 to 101 UOM 25 2023-09-08 10:10:01,906 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV4 to 101 UOM 25 2023-09-08 10:10:01,964 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV5 to 101 UOM 25 2023-09-08 10:10:01,964 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV5 to 101 UOM 25 2023-09-08 10:10:02,007 MQTT udi_interface.interface INFO interface:_message: Successfully set gw270009f38a :: ST to 1 UOM 25 2023-09-08 10:10:02,007 MQTT udi_interface.interface INFO interface:_message: Successfully set gw270009f38a :: ST to 1 UOM 25 2023-09-08 10:10:02,066 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 1 UOM 2 2023-09-08 10:10:02,066 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 1 UOM 2 2023-09-08 10:10:17,350 Thread-19 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:17,350 Thread-19 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:17,507 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV0 to 485839 UOM 58 2023-09-08 10:10:17,507 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV0 to 485839 UOM 58 2023-09-08 10:10:37,392 Thread-21 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:37,392 Thread-21 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:37,422 Thread-21 udi_interface WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/############/Devices 2023-09-08 10:10:37,422 Thread-21 udi_interface WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/############/Devices 2023-09-08 10:10:37,422 Thread-21 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:10:37,422 Thread-21 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:10:37,455 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 0 UOM 2 2023-09-08 10:10:37,455 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 0 UOM 2 2023-09-08 10:10:57,405 Thread-22 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:57,405 Thread-22 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:58,733 Thread-22 udi_interface WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/############/Devices 2023-09-08 10:10:58,733 Thread-22 udi_interface WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/############/Devices 2023-09-08 10:10:58,733 Thread-22 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:10:58,733 Thread-22 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:17,410 Thread-23 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:17,410 Thread-23 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:19,187 Thread-23 udi_interface WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/############/Devices 2023-09-08 10:11:19,187 Thread-23 udi_interface WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/############/Devices 2023-09-08 10:11:19,187 Thread-23 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:19,187 Thread-23 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:37,411 Thread-25 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:37,411 Thread-25 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:38,566 Thread-25 udi_interface WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/############/Devices 2023-09-08 10:11:38,566 Thread-25 udi_interface WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/############/Devices 2023-09-08 10:11:38,567 Thread-25 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:38,567 Thread-25 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:57,420 Thread-26 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:57,420 Thread-26 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()...

@Goose66, any options to have control and/or status of a garage light through MyQ? Also what about temperature and battery status?

Not sure I understand, I want the Rachio device in UDI/IoX to use UDI/IoX for the timers/control/status of the device.

I was hoping the new Rachio Smart Hose Timer (https://rach.io/products/smart-hose-timer-kit/) would show up as a node in IoX but the Rachio NS seems to find the Rachio Bridge but doesn't find the hose valve. @bpwwer are you or do you know if anyone is maintaining Rachio?

The parent node exists and has a status but it doesn't seem functional. @Jimbo.Automates are you able to have a look at the parent node and the ability to look at the status from a program IF? ST-Inventory seems to be similar in that the status isn't accurate, but it is available in the program IF section.

One thing I am stuck on, I create an alert when a node server is down or disconnected. This node server seems to have a parent node with some options and the 'Status' I normally look at but the status and other functions in the parent node are not available in a program in the If section. Is this something that can be enabled?

I hadn't bought this one yet so I purchased it. AWESOME! AWESOME! AWESOME! Night Sound and Speech Enhancement work perfectly. Thank you!

Nicely done, seems to be working as intended.

Part of my sleep timer program turns on Night Sound and Speech Enhancement via a node https://github.com/jishi/node-sonos-http-api/blob/master/README.md on IoX as a http get network resource. @simplextechAny thoughts on adding Speech Enhancement and Sleep control in ST-Sonos?

It basically turns off the items that one touch turns on.

Not in the mobile app screen, just in the web pop-up browser.

I have the iAqualink and a Salt Gen/Salinity Sensor. PM sent with my login details. The One touches show on the main app page, it would be great to have those in IOX because you cannot recreate them in programs. All of the options in configured in OneTouches aren't nodes in IOX.

Goose66, Just installed a new pool/spa with all Jandy equipment and installed the Node in trial. Salinity does seem to be work, is that expected? Will there be any plans to set light colors or pump speeds to the Node? Or bring One Touch configurations, or pump speed and watts info over to the ISY?

I have gone through the setup process and entered the client_id, client_secret, user_id and it finds the Thermostat and seems to be working but displays 'Discovery failed please check logs for a more detailed error.' Seems to be working and added the nodes to in IoX. IoX Version: 5.5.5 PG3x Version 3.1.22 HoneywellHome Current Version: 2.0.1 [Production]

After the IoX Version: 5.5.5 update and a reboot of PG3x(PG3x Version 3.1.22), the Kasa node won't start, press stop and it displays 'Node Server Stop: Kasa not running' press start and it displays, 'Node Server Start: Node server already starting' It's like it's stuck in a starting state.

Did a sudo reboot on the EISY and it wiped out node #1 isylink again! After the reboot PG3 seems to have come back to life and updated itself to PG3x Version 3.1.20 and nodes show connected but are not showing data in the Admin Console or UD Mobile. Re-installs all nodes and rebooted the admin console and they still show no data in the Admin Console or UD Mobile. PG3 web also does not show slot 1 isylink is configured in IoX, even though isylink is the only node that is working.

Update on my EISY from 5.5.3 to 5.5.4 status P3 no longer seen the IoX or PG3 isn't running but it seems to be: This update seems to have hosed PG3: It also wiped out the node #1 for isylink (nodelink), I re-added it and it's working but PG3 is down

Apparently the developer is washing their hands of support and UDI support is looking in to it.

I am running PG3x v3.1.18 which fixed NS not correctly being added to IoX (KASA NS was one it fixed) but ST-Inventory is still an issue. I have a ticket open with UDI support and will update the thread once resolved.

I did the same this morning after the update to IoX 5.5.3 and get similar results, mine creates the NS connections in IoX but doesn't even create the node device it's self and the Node shows disconnected in PG3x.

This update seems to have fixed UD Mobile updating the status of devices and nodes! Nice work UDI Team.

2023-01-04 16:20:38,130 Thread-8 udi_interface.node ERROR node:setDriver: d847329a946104:TP1 - 4 - Invalid driver: ST 2023-01-04 16:20:38,130 Thread-8 udi_interface.node ERROR node:setDriver: d847329a946104:TP1 - 4 - Invalid driver: ST 2023-01-04 16:20:38,130 Thread-8 udi_interface.node ERROR node:setDriver: d847329a946105:TP1 - 5 - Invalid driver: ST 2023-01-04 16:20:38,130 Thread-8 udi_interface.node ERROR node:setDriver: d847329a946105:TP1 - 5 - Invalid driver: ST 2023-01-04 16:20:38,130 Thread-8 udi_interface.node ERROR node:setDriver: d847329a946104:TP1 - 4 - Invalid driver: ST 2023-01-04 16:20:38,130 Thread-8 udi_interface.node ERROR node:setDriver: d847329a946104:TP1 - 4 - Invalid driver: ST 2023-01-04 16:20:38,130 Thread-8 udi_interface.node ERROR node:setDriver: d847329a946105:TP1 - 5 - Invalid driver: ST 2023-01-04 16:20:38,130 Thread-8 udi_interface.node ERROR node:setDriver: d847329a946105:TP1 - 5 - Invalid driver: ST

Should the EISY have TPM enabled like it did on POLISY? Also should we upgrade the BIOS since it is available?

simplextech, any input on ST-Inventory not working with EISY 5.5.2?

After updating PG3x to v3.1.17, I was able to get the KASA NS installed, licensed, and it picked up my TP devices, it shows connected and created Nodes in ISY, but they aren't functional. I deleted the NS from PG3x and it removed the nodes from ISY, re-installed KASA NS and get the same thing. It's like when a node is added to ISY when the Admin Console is open, but I restarted the Admin Console, and even cleared JAVA (deleting the console app), downloaded the new console, connected to EISY and it's the same. Also the nodes KASA created are in the Main tab in ISY Admin Console, but are not available to use within programs.