Everything posted by TJF1960
-
In UDM unable to open Settings>Plugins>YolinkLocal
@Javi, could this error also cause the inability to open Settings>Plugins>Yolinklocal?
-
In UDM unable to open Settings>Plugins>YolinkLocal
I reinstalled about an hour ago, did a hard reboot to eisy. No change. It must be UDM them. Thanks, -Tim
-
In UDM unable to open Settings>Plugins>YolinkLocal
Lucky man you are then! Thank you for taking the time to respond, I appreciate it. Its really not a big deal, unless for some reason I am away and need to restart the plugin. But there are worst things in life. Thanks @Panda88 for all of your laboring and hard work. I appreciate it very much. -Tim
-
In UDM unable to open Settings>Plugins>YolinkLocal
Interesting! Thank you for checking @oberkc. This is the only plugin out of like 20 that does this. It started with the first or second non-production YolinkLocal. I guess this indicates something on my end, but what? Weird. Question, when you resync UDM do you get the message to let the dev know about ST name for the nodeserver? That also started with one of the non-production versions as well. One last detail, if I go to settings plugins and select this plugin, wait 20 seconds or so then close the app, reopen the app and go to settings>plugins I get an error message of: "Could not get pg3 auth PG3 (Plugin Software) is not online. Then at the end it says :Developer Tip: This issue may be caused by PG3's Portal Connection mismatch. 500"
-
In UDM unable to open Settings>Plugins>YolinkLocal
@Panda88 ,I noticed last night that YolinkLocal was not triggering programs. I went to UDM, Settings>Plugins and selected YolinkLocal and the little wheel kept spinning, never would stop. I had forgotten about this, it has been this way since I think non-production days. If I back out and select another plugin it wont open either. So I closed it down. Opened it back up and selected a few different plugins and they all would open properly. I once again selected YolinkLocal and it would not open. I am not sure if this is just a me thing or it just hasn't been noticed and reported before. Also, as of the last update, yesterday, when I resync UDM it still does complain that slot 15 (YolinkLocal for me) is not setting or hasnt set ST name. or something like that. So I don't know if the two are linked or not. Thanks! -Tim
-
Delete Favorites or home page?
How do you delete the favorites main page or home page? Or, how do you add or delete nodes from the home or favorites page? Thanks! Updated eISY yesterday to the latest version.
-
Temp Sensors and Programs in 1.6.2 with IoX 6.0.0
@Panda88 Lol, thank goodness, no. Back in the day, early on I was using this program as a heartbeat for the plugin so I selected the lowest temp possible. But now I see, at some point, you added Last Poll Time for the plugin which I have now switched over to use as the heartbeat (thank You). But when that program fired and alerted me the heartbeat was down is when I discovered that the temp nodes in programs were wacky. Thanks! -Tim
-
Temp Sensors and Programs in 1.6.2 with IoX 6.0.0
Hi @Panda88 , I think there is an issue with temp sensors suddenly on my system. This worked in previous versions. This is an old program I set up. I was checking to see why the program was not running. The program used to have temp of around -40F but not the program displays, well take a look at the pics. The second picture shows the actual values but at the top it doesnt. I looked in the logs and found some errors but they appear to be plugs that are disconnected right now. I tried restarting the plugin but it did not change. Thanks! Tim YolinkLocal_11-1-2025_15729_PM.zip
-
Having to reboot Vue every 3ish days
Thank you for looking into it for me.I I will keep an eye o other plugins. Thanks again, Tim
-
Having to reboot Vue every 3ish days
Heollo @bpwwer, Not sure where to turn as I seemed to be having problems with both Vue and YolinkLocal. I installed 6.0 a last weekend. Since then Vue works for about 3 days then doesn’t update values or control switches. A reboot fixes it for another few days. This morning, I had PGx open in Eisy_ui and in the bottom right side a red warning kept popping up, something about Slot 13 (Vue) was...I am sorry I don’t remember exactly what it was but it seemed to indicate Vue was using too many resources to quickly, is how I interpreted it.. Alternately another warning about slot 15 (YolinkLocal) was struggling as well. Unfortunately, I didn’t capture when vue became unresponsive, but I think I did capture today's events. I reboot and so far so good. I will also add that whatever is going on seems to have affected other plug ins today, devices turning on and off by program were taking way to long. I am on 6.0.0_04 With everything up to date as of yesterday. I have PM’ed you the logs from today. Thank you! -Tim
-
Yolink Local API
Just wanted to let you know I went from YolinkLocal Beta to Production without a hitch. I was able to install production right over the beta, same slot. Easy. _Tim
-
Yolink Local API
Worked perfect! Deleted, installed and once it was done indexing I rebooted the eIsy. I didn't have much time to test programs but the ones I tested which control yolink devices worked perfect. Thank you! -Tim
-
Yolink Local API
Yes, I have a license and it would not allow me to upgrade. I will backup/delete and install the new one in the same slot and restore. Will let you know. Thanks!
-
Yolink Local API
@Panda88, I am not able to update. It acts as if it is a new plugin, only option to install is to a different slot.
-
0.6.1 eisyui is now the default interface
Hi @bmercier, two questions. When Michel mentioned that eisyui is now the default interface, I took that to mean no more Launcher. But I seemed to have been mistaken. I don't see a way to edit programs in eisyui.? When I used launcher (after clearing java and redownloading launcher) I noticed the user/password popup was different. I expected to have to use my email associated with the portal but it appears to be still admin for user. Which is fine by me, its quicker to enter than my email address for sure. Is there a prefered http:// to select in launcher? Updates went great, no issues. Thank you! -Tim
-
Yolink Local API
I am also enjoying being able to view the status of switches and temp sensors in UDM without having to open each node to see whether it is on or off or what the temp is...I may never look at the Yolink app again! I know it was a pain, but Thank You for including this in the last build. It is awesome! Everything is performing perfectly, now two days into the new beta! -Tim
-
Yolink Local API
I have not done the 6.0 upgrade yet, and probably will not for a few days to a week, my system is finally back together and working the way I want it to, I want to enjoy it for a bit
-
Yolink Local API
Hey @Panda88, the new beta has been working great for about 24hrs. I noticed snappier response time over the previous version I had installed. I have not had any of the issues I had before. I really like the "Initializing" driver state in the Yolink Setup node, very handy since it takes about 20 minutes after restart to receive all the data from all of my devices (47 Yolink devices, many are temp sensors) and switch to Initialized. A couple of questions. I have trouble remembering the difference beween Connection State and Node Server State or maybe now its Online State. Is Connection state the devices are talking to TSTYolink node server and Online is TSTYolink is talking to IoX? Thanks for making this all happen! -Tim
-
Yolink Local API
Speaking for myself only, that works for me. You have put a lot of time and effort into it not to collect a fee. Thank you! -Tim
-
Yolink Local API
@Panda88, I too have lost access due to expiration date. I know you are working on it. I also wanted to report that while PG3 shows the plugin as disconnected, the devices seem to show as being connected. And some show Cloud, 1 or two show Local. Please see screenshots -Tim
-
Yolink Local API
Hi @Panda88, Since, for the time being, this will be a stand alone plugin for the local hub, can you look into fixing the display value of the device node icons in UDM? It would be nice to see the status value of plugs (on or off state) as well as temp values displayed on the device icon instead of having to click on the icon to open up the detail page. Currently they display the device connected state instead. Thanks! -Tim
-
Yolink Local API
I fully agree with @sjenkins, He beat me to it! One note of possible promise. In my brief testing between production and beta, it looks like Yolink plugin uses the same reference number of each device. I was able to delete Yolink, and install the local version in the same slot. Once you get all the devices ported over to the local hub, all, theoretically should work and all programs should work as be as well. I only tried this with 4 devices, but it worked perfectly. But I have over 40 so time will tell. -Tim
-
Yolink Local API
Hello @Panda88, The local hub has been working for me as well. I am at a crossroads and would like your input. I can move over all of my Yolink devices to the new local hub and run it. However I am wondering what your plans are for integration? Integrating it into the current production version or keeping it a stand alone plugin? I would rather not move all the upwards of 40ish devices, fix all the programs only to find out that I will have to do it again. I am sure you understand. Thanks very much! -Tim Oh, forgot, I received notification the trial period was almost up for the local plugin. I already have the paid production plugin, will there be a fee for the beta version? How can I correct it?
-
Yolink Local API
That is a great question, I have not been able to schedule a time with my family for shutting down internet in my house, but as I think about it, it would only interrupt for 20 minutes or so I would think. Maybe I can test this weekend before everyone is up and around. @sjenkinsHave you been able to test and confirm the local hub delivers locally when the internet is interrupted? Or anyone else for that matter? Thanks! -Tim
-
I messed up PLM eisy integration – BADLY – now what?
Awesome, fingers crossed!