Jimbo.Automates

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

Known issue with PG3 /topic/43088-plugins-no-longer-working-with-error-unsupported-callback-api-version-version-20-added-a-callback_api_version-see-migrationsmd/ Sent from my Pixel 8 Pro using Tapatalk

Due to the issue below, do not upgrade until Monday after @bmercier releases the below and you update:

Also, please confirm at PG3x UI says the node server is connected, and in Admin Console -> ELK Controller -> Nodeserver Errors = 0.

PG3 ELK Plugin 3.10.15 released, see OP for info. IMPORTANT: If using ELKID or ELKNAME you must enable the "Allow ISY Access by Plugin" on the configuration page. This will be required in PG3x Version 3.2.19 and beyond.

@wmcneil Released 3.10.12 which should fix this issue. Please confirm since I don't have this keypad to test with.

That would explain it, I'll try to get a new release soon to fix it, issue 103 created.

Sorry for the delay I neglected to add this to my task list and forgot about it. Does that keypad have a thermostat? I have a profile entry for keypad and keypadT and looks like I never updated keypadT.

The program must be triggered by a node change , if you are just running it manually it won't show the node. Program is a little confusing that most reference Garage Entry and one references Front Entry? Sent from my Pixel 8 Pro using Tapatalk