DennisC

While I didn't experience problems with this plugin when upgrading to IoX 6.0, I did experience the same problem with the Elk plugin with 2 different systems. In both cases, the fix was reinstalling the plugin in the same slot. Worth noting, it did take several reinstalls before everything worked like it should.

See how I did it from the attached screenshot. See how I did it from the attached.

I'm on IoX 6.0, UD Mobile 1.4.4 (Android), and Yolink 1.6.8. Over the last 5 days, I updated both my systems to IoX 6.0. no problems with the update remain except with Elk not parsing data correctly and showing numeric values. I have opened a support ticket with UD, but they haven't located the issue yet. I also have reached out to Jimbo, but he hasn't responded yet. For critical items and wife acceptance, I programed UD Mobile favorites to show what the numerical values should represent.

I am running Yolonk plugin at two locations. Since the last update, I am not receiving errors in UD Mobile when synching.

The main problem here is you are using two outdated and no longer supported services. Both PG2 and ISY994 are well beyond their anounced end of life date. To continue taking advantage of the features you are looking for, you would need to update to eisy and PG3x. You can't expect a developer to attempt to support an out dated plugin when he would have no way to test or even distribute the product. UD has stated that PG2 will be shutdown at some point, I'm surprised you can still access it. If you are interested in updating, I think UD has a current discount offer for eisy.

Updated and synchronized with UD Mobile without errors. Thanks for taking care of this.

I upgraded over the weekend. Besides what was already mentioned, I experienced two issues. First, the Elk plugin would not connect. Nothing I did would get it started. I had to reinstall the plugin two times to get it back on. Second, the Elk plugin is not properly displaying node vales in UD Mobile. Instead of parsing the values, it is displaying numeric values. It is a known issue that is being investigated.

I experienced the Elk plugin being disconnected after updating to IoX 6.0. I tried restarting the plugin several times but nothing I tried would work. I then tried reinstalling the plugin. I had to do the reinstall 2 times, but did manage to get it connected and working again.

@Panda88 I had submitted a support ticket regarding the ST issue. @Javi replied with a message to see this post: https://forum.universal-devices.com/topic/45909-in-udm-unable-to-open-settingspluginsyolinklocal/#findComment-399529 Wasn't sure if you were aware of this post.

I can confirm this is still happening in v5.9.1. I also agree that I would prefer to only receive the messages I program - especially at 3 am.

Does that mean it is a new purchase (that's ok, just trying to be sure)? Can it be installed in same slot has original, or does it need to go in to a new slot and all programing updated?

@Jimbo.Automates , Not sure if this is an issue with UD Mobile or Elk plugin, but after updating to IoX 6.0, UD Mobile is displaying numeric values for certain fields, including Armed Status, Arm Up State, Chime Mode, Physical & Logical Status, as well as some others. I have synchronized, rebooted eisy, and synchronized again with no change. Please see screenshots. Thanks for your help.

@Panda88 , after updating to IoX 6.0 and synchronizing UD Mobile, I received an error for Node Server 7 which is Yolink on my system. Please see attached screenshot. As an aside, I have a Yolink local hub that I would like to add to my system. I just want to verify current procedure for including the local hub node server support. Does this require a new plugin purchase (which is fine, just want to know best migration path)? If so, can the updated plugin be installed in same slot, or is a new slot installation required? Keep both running, or just the updated version? Thanks, Dennis

I'm on Android and my screen is different. Try clicking on the help button (? in circle) left of the trash can along the top. See if the instructions are any help.

Try clicking the arrow where it says Set Enable. You need to change the command.