Jimbo.Automates

Not a recent upgrade issue. More likely you deleted those customization that used to be there? Sent from my Pixel 8 Pro using Tapatalk

Yes, this would have to be fixed in the AC, nothing I can do about it. Need @Chris Jahn to fix. Sent from my Pixel 8 Pro using Tapatalk

It's working fine for me. Sent from my Pixel 8 Pro using Tapatalk

See Editions https://github.com/UniversalDevicesInc-PG3/udi-poly-notification Sent from my Pixel 8 Pro using Tapatalk

Sorry, missed your previous posts, I'll look into it when possible. Sent from my Pixel 8 Pro using Tapatalk

I'm not sure why you are seeing SD's, the manual says: These commands allow programming and reading Insteon device addresses via the M1XSP Serial Port Expander configured in the Insteon mode So the SD is a response back from the M1EXP with an insteon device description. Must not be supported by the Python API I use. The KA is M1EXP response saying which areas all the keypads are assigned to. No need to worry about this one. The KF is M1EXP response reporting a function key was presses, not sure why you would see a timeout. The CS is M1EXP response reporting the control output status. I'm not seeing any of these timeouts in either of my ELK plugin logs. I'll have to dig into the Python API to see if I can figure out why it's complaining.

It happens if I just unplug the PLM then plug it back in.

I shut down the plugin, disconnected the Autelis and it still randomly turned on. Pool tech is going to take a look. Sent from my Pixel 8 Pro using Tapatalk

Thanks for checking. When you say disconnected, do you mean unplugged the USB or unplugged the PLM from power? When I unplug the PLM from power, then plug it back in IoX says no PLM connected...

Sorry, I meant USB PLM, no idea why I said serial. Weird that mine has issues and others don't. Sent from my Pixel 8 Pro using Tapatalk

I have my eisy on a UPS, with a USB PLM that is of course not on the UPS. So when I loose power the eisy stays online, but when power is restored the IoX on eisy never sees the PLM come back. Is there someway to fix this without rebooting?

Issue created. https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/105

Ok that helps, now I know where to look. Sent from my Pixel 8 Pro using Tapatalk

With the API? Please elaborate. Sent from my Pixel 8 Pro using Tapatalk

Is that a keypad or touchscreen? I don't think the Elk API gives access to that but I'll look it up. Sent from my Pixel 8 Pro using Tapatalk

I've asked my installer to check when these will be available for order or pre-order.

Sorry, I'm not sure what you are asking for can you be more descriptive?

Great, please let me know if you have any issues.

Yes, but what I was asking you was if you agreed that based on the log I posted in the OP that it looked like IoX was turning on the device? No That was my next test, but I thought just deleting the node would suffice. But I like having it running because I have IoX send me a notification whenever that slide (or any other node we seldom use) is turned on because the pool guys sometimes forget and leave them on. Thanks, that was my next question.

I had delete the node, restarted the node server so the node for the Slide is not in ISY but it's still randomly turning on. Very odd since it really looked like a DON was being sent to the Plugin based on the log? You agree @Goose66?

Yes, I wanted to make different options for people to choose from. But didn't want to put too much effort into it In case it changes since this is the first release from Javier. Sent from my Pixel 8 Pro using Tapatalk

I don't think so because based on the plugin log it's being sent a DON which can only come from isy. If it was turned on by something else it would just be a ST change. I deleted the node, restarted the plugin and isy. So far it hasn't happened again but will take a few days before I know for sure. Sent from my Pixel 8 Pro using Tapatalk

Nope, also checked that, but forgot to mention it. Sent from my Pixel 8 Pro using Tapatalk

Yes appears so, but I just can't figure out how. I had a random issue like this after upgrading to eisy, so deleted and readded the device and the problem went away. I'm tempted to do it with this as well if event log can't catch it. Sent from my Pixel 8 Pro using Tapatalk

I've had a very strange problem for a while now, randomly one of my aux devices will turn on. This device is not in any program, except for the one which monitors if it is on and notifies me. Here's the excerpt from the log where it turned on today, logging was only in info mode. 2024-03-22 17:15:16,289 Thread-174275 udi_interface INFO iaqualinkns:longPoll: Sending Heartbeat command to iAquaLink service node... 2024-03-22 17:15:16,290 Thread-160873 udi_interface.interface DEBUG interface:_send: PUBLISHING {'command': [{'address': 'service', 'cmd': 'AWAKE'}]} 2024-03-22 17:15:16,372 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-03-22 17:15:16,373 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-03-22 17:15:16,373 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'service', 'success': True} from Polyglot 2024-03-22 17:15:30,151 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-03-22 17:15:30,152 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-03-22 17:15:30,152 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-03-22 17:15:30,152 Thread-174277 udi_interface DEBUG iaqualinkns:shortPoll: In shortPoll()... 2024-03-22 17:15:41,318 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-03-22 17:15:41,319 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-03-22 17:15:41,319 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '189308_aux_1', 'cmd': 'DON', 'query': {}} from Polyglot 2024-03-22 17:15:41,319 Command udi_interface INFO nodes:cmd_don: Turn on aux_1 in DON command handler: {'address': '189308_aux_1', 'cmd': 'DON', 'query': {}} and the PG3 log shows it happening: 3/22/2024, 17:15:41 [pg3] info: [00:21:b9:02:5d:7d(20)] IoX HTTP Inbound: Received DON for node: 189308_aux_1 3/22/2024, 17:15:43 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:02:5d:7d_20: set 3/22/2024, 17:15:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:5d:7d] :: - http://localhost:8080/rest/ns/20/nodes/n020_189308_aux_1/report/status/ST/1/25 3/22/2024, 17:15:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:5d:7d] :: [200] :: 1.903103ms - http://localhost:8080/rest/ns/20/nodes/n020_189308_aux_1/report/status/ST/1/25 So obviously something is sending the DON but I can't figure out where it is coming from. The ISY Log only shows: PoolSpa / Pool and Small Spa / Slide Status On Fri 2024/03/22 05:15:43 PM System Unknown I now have the event viewer open to see if I can catch it triggering. If anyone has an idea how this could be happening, or more ways to debug please let me know. - Jim