Jimbo.Automates Posted March 23 Share Posted March 23 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 Quote Link to comment
Goose66 Posted March 23 Share Posted March 23 It does appear the DON command for aux_1 is coming from IoX. Quote Link to comment
Jimbo.Automates Posted March 23 Author Share Posted March 23 It does appear the DON command for aux_1 is coming from IoX.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 Quote Link to comment
Jimbo.Automates Posted March 23 Author Share Posted March 23 Could it be in a scene?Nope, also checked that, but forgot to mention it.Sent from my Pixel 8 Pro using Tapatalk Quote Link to comment
dbwarner5 Posted March 23 Share Posted March 23 Could it be coming from the web interface for iAqualink... an old program that is running? Quote Link to comment
Jimbo.Automates Posted March 23 Author Share Posted March 23 Could it be coming from the web interface for iAqualink... an old program that is running? 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 1 Quote Link to comment
Jimbo.Automates Posted March 25 Author Share Posted March 25 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? Quote Link to comment
Goose66 Posted March 25 Share Posted March 25 (edited) Not sure I understand the current context. No node for aux_1 in IoX, yet aux_1 is still turning on randomly? Are there any corresponding log entries for aux_1 and DON commands, like in the first log snippet you posted? Have you tried shutting down the plugin for a couple of days to see if the random aux_1 behavior stops? Just FYI, I did a quick check to verify that the cmd_DON method that generates the INFO log entry in the first post is not called by any other part of the code, i.e., only called as a result of DON commands received from PG3 for the node. Edited March 25 by Goose66 Quote Link to comment
Jimbo.Automates Posted March 25 Author Share Posted March 25 4 hours ago, Goose66 said: Not sure I understand the current context. No node for aux_1 in IoX, yet aux_1 is still turning on randomly? 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? 4 hours ago, Goose66 said: Are there any corresponding log entries for aux_1 and DON commands, like in the first log snippet you posted? No 4 hours ago, Goose66 said: Have you tried shutting down the plugin for a couple of days to see if the random aux_1 behavior stops? 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. 4 hours ago, Goose66 said: Just FYI, I did a quick check to verify that the cmd_DON method that generates the INFO log entry in the first post is not called by any other part of the code, i.e., only called as a result of DON commands received from PG3 for the node. Thanks, that was my next question. Quote Link to comment
Jimbo.Automates Posted March 31 Author Share Posted March 31 Any resolution/new info here? 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 1 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.