DennisC

I also never saw anything for eisy requiring a specific IP address. UD wants you using DHCP to reduce support issues.

Have you updated eisy and UD Mobile this week? There was an issue with UD Mobile that I think has been recently corrected. Not sure if it was the UDX for eisy that was updated this week, or a recent UD Mobile app update, but it has been fixed for me.

Thanks for the information. I did find the following in the debug.log: 2025-12-04 11:40:24.373 Command udi_interface.node DEBUG node:setDriver: vg9pyas6:DH Garage Reporting set GV2 to 1 to Polyglot 2025-12-04 11:40:24.373 Command udi_interface.node DEBUG node:reportDriver: Updating value to 1 2025-12-04 11:40:24.383 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'vg9pyas6', 'driver': 'GV2', 'value': '1', 'uom': 17, 'text': None}]} 2025-12-04 11:40:24.414 MQTT udi_interface.interface INFO interface:_message: Successfully set vg9pyas6 :: GV2 to 1 UOM 17 I will pm you the full log package, if you could offer me some direction, it would be appreciated.

Thanks for both porting this over to pg3x and for responding. I did a comparison of the UOM values listed in sensibo_node.py and pg3x, besides GV2 showing 17 instead of 25, I also found the following discrepancies (clarification - I compared UOM values from github to pg3x): CLISPC - pg3x UOM = 17 instead of 4 CLISPH - pg3x UOM = 17 instead of 4 ST - pg3x UOM = 17 instead of 4 Let me know if there is anything I can do to correct this. Here are some screen shots of what I see.

I have Sensibo plugin installed on eisy running 6.0.3 I noticed that the temperature in the space dropped below the setpoint in a program to trigger heat mode, but the unit didn't turn on. When I signed in to the admin console, the none of the Sensibo nodes where populating. Next I checked pg3x and while the configuration screen looked fine, plugin wasn't responding and the log didn't populate. I reinstalled the plugin in the same slot and everything came up fine. However, I noticed the Power State in the admin console was reading 0 degrees F. In pg3x the Power State is listed as GV2 and a UOM of 17, which is used for other temperature settings. Turning the unit on, the Power State updates to 1 degree F. Something appears incorrect? As a follow up to my initial post, I have eisy count runtime utilizing the Power State. In a program, the values available for the Power State are on & off, making the counter program inoperable.

As I said in my post above: "It is available from the upgrade packages in the admin console."

There is an update to udx (v4.2.0) that corrects the Elk Plugin from displaying names instead of numerical values in UD Mobile & eisy-ui. It is available from the upgrade packages in the admin console. After the upgrade, the values are displaying correctly , as I indicated above. However, after deleting Java files and downloading a new start.jnlp, the Launcher will no longer save to the desktop. While I suspected this for awhile, I also was able to confirm that after the upgrade, signing in to eisy-ui the first time, disconnects the Elk Plugin. The Elk Plugin then reconnects. Signing in a second time shortly after has no impact on the plugin. As a follow up, I went back and deleted Java files again (3rd time) and re-downloaded start.jnlp. This time the Launcher was added to my desktop without issue.

As per my conversation earlier this week with UD support, they should have a firmware upgrade early next week that they hope will address this issue and some others. For now, the best you can do is add names to your favorite status tiles in UD Mobile to match the Elk action. The actual name would be added to Set Formatted Value. See this post for an example:

Suggest trying to exclude your zwave devices ( do it two times in a row), then try to include the device.

I suggest you do nothing else until you open a UD support ticket and receive instructions from them on how to proceed.

I would suggest setting the logging in pg3x for the Elk plugin to debug and checking for any errors. If none are visible while monitoring, you can download a log file and look through the text files. If you still can't identify the issue, send the log file to plugin developer for review.

Just double checking, are you using your portal credentials to login?

The portal address is: https://my.isy.io/index.htm This is a UD website that allows exterior connection with out opening ports and additional services. It is a paid subscription for a nominal fee. UD is moving to single sign on for all services.

If the IoX launcher is showing v6.0, you need to use your portal login credentials.

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?