joeria

Hi Javi, yes it was. Thanks!

I'm at the end of a very long 9 hour migration saga and can't get past this last item. Migrating the plugins did not work so I wound reinstalling and reconfiguring 12 plugins. In a support conversation, the rep had me migrate licenses to get the plugins working. Then when I got to the step to migrate UD mobile I had could not clear the UUID since it show as expired. BTW the UD Mobile migration instructions keep referring to System under the setting tab, which doesn't exit, so I have been on the controller settings. In order to try to follow the directions, I purchased a one year license for the Polisy on the portal, but still no joy in clearing the UUID, yet it functions fine on remote. If I delete the Polisy and add the eisy and then do a restore from my backup it deletes the eisy and adds the Polisy. I'd really like to be able to migrate as I did a lot of work to my favorites look and act as I want. For now, I'm back on the Polisy. Anyone have any thoughts. I did also open a support ticket Thanks!

Thanks Bob, I tried several times and took several backups and tried those. The plugins were always unmanaged. I wound up migrating licenses on the portal and still needed to reinstall and reconfigure all of my plugins. Oh well. I'm now struggling with migrating favorites with UD Mobile. Oh well!

I'm migrating from a Polisy running PG3x to an eisy. I the IOX migration went fine, but I am unawake to migrate the plugins. I made a backup (actually several) from the Polisy. I chose the Migrate from PG3 Backup option (again several times with different backups) and each time I get an error PG3 Backup Format Incorrect. I have also factory reset the eisy and get the same result. I don't want to resinstall all the plugins because of the custom configs and the purchased licenses. Any advice? FYI I'm also opening a ticket with UD on this. Thanks!

Same here. I think they finally blocked us completely. I am using IFTT plugin for web hook. No status reporting but at least my programs can still arm the system.

Thanks. I reinstalled from non-production store and it is working now

Thanks, I'll look there. Interesting that it was working and it stopped

Hi, Hi @Goose66 & @Michel Kohanim I noticed that my nest devices were not updating in iox and when I check the plugin it is disconnected. I've tried restarting, no change and nothing appears in the log even on debug setting. I've tried to authenticate again and that seems to run fine but still no connection and nothing in the log. I then noticed that the NestSDM does not appear in the store or my purchases. Is this no longer available? Thanks!

Hi, I really appreciate this plugin! Would it be possible to add thermostat sensor status and the ability to change it in a future release? A shortcoming of Nest is that it only allows you select which sensor to use from the choices of morning, afternoon, evening and night. This does not give flexibility as to what time each segment starts and ends and does not allow for different sensor changes on different days. I was hoping to control this with a program. Thanks for considering this! Joe

Hi @Goose66, Thanks so much for writing this! I have installed (and dented and reinstalled) the trial today. The authentication went very smoothly. I have four thermostats in the house. 2 heat only, 1 cool only and one Heat & Cool. On discovery it shows 5 nodes, the house and the four thermostats. For 3 of the thermostats all the data elements are listed below the node entry and load fine into the iox. For the heat & cool thermostat it shows in the PG3x screen with the first line looking just ;ike the others with its unique name, a unique address and in the hint column, the same hint as the three other thermostats but with a trailing ".0". There are no other lines and this thermostat does not load in the iox admin console. Again, I deleted the node and reinstalled it into a new slot but the condition is the same. I'd appreciate any advice or insight. Thanks again! Joe

I plan to try it

Hi Javi, Thanks for your work on UD Mobile, really appreciate it! Any plan to make the app available on Apple Watch? Best, Joe

I was having the issue and just updated to 1.1.60. Issue continues. Some items display properly. A couple of devices display if I tap them and then go back. Other items (some scenes but not all, all nodes from pg3 do not display). Nodes do not display status in devices tab but respond to commands

Thanks @vspete. That's not a good option for me, at least not right now. I can't get the installer code. Also, not sure I'd want another company with access to my panel. Appreciate the insight. The link to the post is broken, but I can imagine the content

Hi, Se just had some work done on our alarm - added some zones and deleted others. The changes are not populating in the plugin. When restarting, I am also getting Discovery Failed. I have a valid user and password in the config but see the no user code in the log. Log below (identifying info replaced), any insight? 2024-02-08 14:05:12,177 Thread-2 root WARNING TotalConnectClient:populate_details: No usercode for location XXXXXX. 2024-02-08 14:05:13,953 Thread-2 udi_interface DEBUG totalconnect-poly:discover: Adding devices for location XXXXXX with name Home 2024-02-08 14:05:13,954 Thread-2 udi_interface DEBUG totalconnect-poly:discover: Found device LTEM-XA in location Home 2024-02-08 14:05:13,955 Thread-2 udi_interface DEBUG totalconnect-poly:add_security_device: Adding security device panel_YYYYYYY with name LTEM-XA for location Home 2024-02-08 14:05:13,957 Thread-2 udi_interface.node DEBUG node:_updateDrivers: Update panel_YYYYYYY default GV0 to 1 / 25 2024-02-08 14:05:13,958 Thread-2 udi_interface.node DEBUG node:_updateDrivers: Update panel_YYYYYYY default GV1 to 0 / 2 2024-02-08 14:05:13,959 Thread-2 udi_interface.node DEBUG node:_updateDrivers: Update panel_YYYYYYY default GV2 to 0 / 2 2024-02-08 14:05:13,959 Thread-2 udi_interface.interface INFO interface:addNode: Adding node Home - LTEM-XA(panel_YYYYYYY) [None] 2024-02-08 14:05:13,960 Thread-2 udi_interface.interface INFO interface:setController: Using node "panel_YYYYYYY", driver "False" for connection status. 2024-02-08 14:05:13,966 Thread-2 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: discovery_failed = Discovery failed please check logs for a more detailed error. ...saving 2024-02-08 14:05:13,967 Thread-2 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2024-02-08 14:05:13,968 Thread-2 udi_interface ERROR totalconnect-poly:discover: Discovery failed with error Missing element isSceneZones (GetPanelMetaDataAndFullStatusEx_V1.isSceneZones) Traceback (most recent call last): File "/var/polyglot/pg3/ns/000db953c5b4_5/totalconnect-poly.py", line 157, in discover self.add_security_device(loc_id, loc_name, device, update) File "/var/polyglot/pg3/ns/000db953c5b4_5/totalconnect-poly.py", line 176, in add_security_device panel_data = self.tc.soapClient.service.GetPanelMetaDataAndFullStatusEx_V1(self.tc.token, loc_id, 0, 0, 1) File "/usr/local/lib/python3.9/site-packages/zeep/proxy.py", line 46, in __call__ return self._proxy._binding.send( File "/usr/local/lib/python3.9/site-packages/zeep/wsdl/bindings/soap.py", line 123, in send envelope, http_headers = self._create( File "/usr/local/lib/python3.9/site-packages/zeep/wsdl/bindings/soap.py", line 73, in _create serialized = operation_obj.create(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/zeep/wsdl/definitions.py", line 224, in create return self.input.serialize(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/zeep/wsdl/messages/soap.py", line 79, in serialize self.body.render(body, body_value) File "/usr/local/lib/python3.9/site-packages/zeep/xsd/elements/element.py", line 232, in render self._render_value_item(parent, value, render_path) File "/usr/local/lib/python3.9/site-packages/zeep/xsd/elements/element.py", line 256, in _render_value_item return self.type.render(node, value, None, render_path) File "/usr/local/lib/python3.9/site-packages/zeep/xsd/types/complex.py", line 307, in render element.render(node, element_value, child_path) File "/usr/local/lib/python3.9/site-packages/zeep/xsd/elements/indicators.py", line 256, in render element.render(parent, element_value, child_path) File "/usr/local/lib/python3.9/site-packages/zeep/xsd/elements/element.py", line 226, in render self.validate(value, render_path) File "/usr/local/lib/python3.9/site-packages/zeep/xsd/elements/element.py", line 284, in validate raise exceptions.ValidationError( zeep.exceptions.ValidationError: Missing element isSceneZones (GetPanelMetaDataAndFullStatusEx_V1.isSceneZones)

Thanks I got it. Was a copy of one from another that's why the remnant still existed. So in this case, to test I changed the <= to NOT=. I then chose RUN IF. So the IF came into play yet it did'nt display the node name. Is that because I forced the IF to run rather than the stats change forcing it?

Hi @Jimbo.Automates I have tried to use node substitution but I can't seem to get it right. I have created a program and a customization. In the customization I include the program name variable and the node name variable. The resulting notification includes the proper program name but for the node is says node[#]. Please tell me what I missing or doing incorrectly. I've tried reading the doc several times and searching the forum but can't find the error. Program and customization screenshots attached. Thanks!!

Thx

Hi @DennisC Folliwing the update the condition stopped and the node ran clean. The condition reoccurred once or twice over a couple of days. No big deal. Today it has occurred three times. Any thoughts? Thanks!!

Thanks. I've done this and will monitor. Appreciate the quick reply!

For the past week or two I’m getting notified many times a day that the node failed and then immediately after I get a notice that the node connected. is anyone else experiencing this? Any thought as to cause? Thanks

Above is a quick inventory from the st-inventory plug in. seems like the address of most devices having the issue begin with 1, 2 or 3. Note they always all go on at the same time. The are no response or comm issues with them. Also the status change does not hit iox unless the next time the device is queried. thanks for taking time to try to help

Hi Geddy, Thanks for the reply!! Yes, I did follow the troubleshooting in the last post and addressed all the programs by either eliminating the condition or putting a delay of several seconds at the start of the then or else statements. Also, I con confirm that the event often occurs when no program has executed for several minutes prior. Most of the devices turning on are older, there are one or two newly replaced ones also affected. In response to the questions: What ISY device are you using? Polisy What is your firmware? 5.7.0. Was happening on prior also Have you factory reset and restored devices that have randomly turned on? Not again since it started to recur How old is your PLM? Changed as part of troubleshooting in the spring. Thanks again! Joe

I had a thread titled as above without the again a few months ago. Below is the last post I made in that thread. Unfortunately after several months of quiet, I'm seeing a handful of devices (same devices each time and same as in the past events) turn on randomly. The devices are not in any common scene except my good night scene which has many more devices. Any thoughts again? So, it has subsided, but my solution/answer is not straightforward. I first tried restoring from IOP the links on all devices that would turn on. That did not solve the issue. I also went through all my programs looking for situations where an "on event" on a device would trigger an "on event" for a scene in which the device was a member as this was a known cause. I either eliminated those situations or put a substantial (several second) delay before executing the scene on. This also did not resolve for me. I note these 2 solutions appear to have helped others. Finally, knowing that the devices that the devices impacted appeared to be older and likely had an "all on" bit in their code, I would take on or two off the network (air gap or unplug) at a time and see if that would stop it. Doing this, I found a couple of old devices that would not air gap or would not take a restore device. I changed these out and have not had an occurrence since. Cost me replacing about 5 devices that appeared to be working fine, but stability is king.

thanks!