Jimbo.Automates

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

A lot of people have converted to PG3x since it was released a long time ago, I did 3 systems with no problems. Submit a ticket and someone can take a look. Sent from my Pixel 8 Pro using Tapatalk

Looks like you are still on PG3 not PG3x. This is a know issue with PG3 on Polisy where files are not properly created during an install. The issue was never resolved since it no longer happens with PG3x. See "Upgrading to PG3x" at https://wiki.universal-devices.com/Polisy:User_Guide

I see. So you should never need to do anything in the plugins configuration menu for PG3 plugins, and editing and or saving changes can break the plugin. I wish that could be disabled for PG3 plugins... Sent from my Pixel 8 Pro using Tapatalk

That's odd that 1,3 doesn't work, that should mean 1 and 3, where 1-3 means 1 2 and 3. I can look into that. The library supports 208 zones, so it should work. A zone will be added if it is not disabled, and its area is included in the areas list. Set the Log Level to debug, restart the node server and after it completes the startup download log package and PM it to me with the number and name of a zone you expect to be added that isn't showing up. The node server configuration page help shows the format of the host as ipaddress:port where port is 2101. and you must specify a proper user_code which is only needed to arm/disarm the system.

Looks like I never upgraded telegram to use the new method, it still uses the old method where you set the custom message on the controller then send it from the service node. I'll try to add the new method soon.

Thanks Javi, didn't think about that. But the node server does support multiple portal accounts by adding separate "UD Portal" service nodes. The UD Mobile node doesn't support multiple portal accounts.

Sorry, I can't see how this could happen. I'll try to look into it and get back to you.

In UDM the only option is called group. This is a group I call JimsPhone which contains my current phone. Sent from my Pixel 8 Pro using Tapatalk

Actually, it is recommended to only use Groups, put the new phone in a group and send to the group. That way when you get a new phone you just have to edit the group.

Restart the Notification plugin, then after a couple minutes resync UDM. Sent from my Pixel 8 Pro using Tapatalk

Those errors are PG3 issues that @bmercier is aware of. Sent from my Pixel 8 Pro using Tapatalk

I wasn't saying the connect/disconnect was related to IoX being busy, only commenting on the error/warnings you posted, which I don't think are related to the same issue. You must be a light sleeper if the watch can wake you up [emoji16] mine is always on DND. Sent from my Pixel 8 Pro using Tapatalk