Jimbo.Automates

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

Haha. I studied your first picture for a while trying to see the error. Just glad it was something simple Sent from my Pixel 8 Pro using Tapatalk

Your first example should work perfectly. This is simple example I previously posted of a program on IoX to lock the locks when the Elk is armed or disarmed. The node "Home" is my main area. Lock Example - [iD 01F7][Parent 020F][Enabled] If 'Alarm-Elk / Home' Armed Status is Disarmed Then Set 'Locks / Garage Door Inside Lock' Unlock Else Set 'Locks / Garage Door Inside Lock' Lock Sent from my Pixel 8 Pro using Tapatalk

I'll be back home early tomorrow morning so will try to look soon. Sent from my Pixel 8 Pro using Tapatalk

Will need @bmercier to review your PG3 logs.

Sorry I am traveling with spotty Internet, I'll try to look those up when I can. Sent from my Pixel 8 Pro using Tapatalk

Looks like you are on a polisy with PG3? You'll need to upgrade to PG3x, this is a known bug in PG3. Search the wiki for more info on upgrading. Sent from my Pixel 8 Pro using Tapatalk

I can access both of mine just fine in UDM Plugin. You'll have to work with @Javi Sent from my Pixel 8 Pro using Tapatalk

Yes, thanks. Then nothing I can.do if the Elk API doesn't support it. But I'll check and make sure it's not an issue on my side. Sent from my Pixel 8 Pro using Tapatalk

Yes that's what I was saying, try the Armed next Stay Mode and see if it actually works and I can move it to a button instead. Sent from my Pixel 8 Pro using Tapatalk

With my ELK keypads this is not possible, once the system is Armed you have to disarm it to arm in another mode. However when you arm you can push the Stay button multiple times to scroll thru the modes, you can do the same with the " Armed next Away Mode" and " Armed next Stay Mode", although I can't remember if I actually have ever tested those. Maybe they should be buttons instead of selections under the Armed Status menu?

You mean in my post? I looked on my phone using tapatalk and it didn't show up, but just looked using Chrome on my laptop and it shows up. So I edited the post and deleted & adding it, so hopefully you can see it now? It's not much to look at

Custom Tiles are in Beta for UD Mobile: https://forum.universal-devices.com/topic/42756-ud-mobile-custom-tile-testing I made a pretty simple, and pretty ugly example for ELK if anyone wants to check it out. Just use your area node and reference https://jimboca.github.io/ELK/example-1%3Fheight=180&span=3.html

I made a pretty simple, and pretty ugly example for ELK if anyone wants to check it out.

Looks like it may be related to a change in the latest PG3 interface @bmercier and @Goose66 will need to review 2024-02-26 07:44:56,873 Thread-12 udi_interface ERROR udi_interface:write: Exception in thread 2024-02-26 07:44:56,876 Thread-12 udi_interface ERROR udi_interface:write: Thread-12 2024-02-26 07:44:56,878 Thread-12 udi_interface ERROR udi_interface:write: : 2024-02-26 07:44:56,880 Thread-12 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2024-02-26 07:44:56,885 Thread-12 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2024-02-26 07:44:56,901 Thread-12 udi_interface ERROR udi_interface:write: self.run() 2024-02-26 07:44:56,905 Thread-12 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2024-02-26 07:44:56,915 Thread-12 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2024-02-26 07:44:56,917 Thread-12 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9532a30_10/nslib/nodeserver.py", line 40, in _parameters_handler 2024-02-26 07:44:56,922 Thread-12 udi_interface ERROR udi_interface:write: self.checkParameters() 2024-02-26 07:44:56,924 Thread-12 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9532a30_10/iaqualinkns/iaqualinkns.py", line 223, in checkParameters 2024-02-26 07:44:56,930 Thread-12 udi_interface ERROR udi_interface:write: self.sessionTTL = int(self.Parameters.get(PARAM_SESSION_TTL, DEFAULT_SESSION_TTL)) 2024-02-26 07:44:56,933 Thread-12 udi_interface ERROR udi_interface:write: TypeError 2024-02-26 07:44:56,935 Thread-12 udi_interface ERROR udi_interface:write: : 2024-02-26 07:44:56,937 Thread-12 udi_interface ERROR udi_interface:write: get() takes 2 positional arguments but 3 were given

Because I am just an independent plugin developer who is compensated a little, but nowhere near the time spent developing and helping users. Starting out with "What a joke" is extremely offensive since I try very hard to not release with issues. This issue was out of my control and completely unrelated to my plugin Of course I tested on my production system and let it run for a while before announcing the release. If you have issues with UDI procedures then post in an appropriate forum so your criticism is directed appropriately and try to be considerate. Sent from my Pixel 8 Pro using Tapatalk

That would be nice, but out of my control. If you are worried then don't update right away. I was responding directly to communication issues, not release methods. That should be discussed in another sub forum. Sent from my Pixel 8 Pro using Tapatalk

As soon as the issue was discovered I posted a warning, not sure how it can be communicated sooner than it's discovered. Sent from my Pixel 8 Pro using Tapatalk