tazman Posted Thursday at 04:15 AM Posted Thursday at 04:15 AM I installed 0.4.3 and the status are coming through on eisy.local except for the yolink plugin does not show for my temperature sensors. I also noticed UD Mobile does not load status unless you click on the item then it brings up the status but they load automatically when I'm on the local network. Quote
bmercier Posted Thursday at 01:45 PM Author Posted Thursday at 01:45 PM 9 hours ago, tazman said: I installed 0.4.3 and the status are coming through on eisy.local except for the yolink plugin does not show for my temperature sensors. I also noticed UD Mobile does not load status unless you click on the item then it brings up the status but they load automatically when I'm on the local network. > the status are coming through on eisy.local In eisy-ui? AC, UDM? > except for the yolink plugin does not show for my temperature sensors. What is it that does not show. The properties? The status values on the properties? Is that in eisy-ui, or AC and UDM connected on port 80 or 443? Quote
sjenkins Posted Thursday at 11:38 PM Posted Thursday at 11:38 PM (edited) great job, I have status & properties on everything, Insteon, nodes, zwave except yolink devices from that node server, get a status but no properties on any devices Edited Thursday at 11:40 PM by sjenkins Quote
bmercier Posted Friday at 12:16 AM Author Posted Friday at 12:16 AM 36 minutes ago, sjenkins said: except yolink devices from that node server, get a status but no properties on any devices Can you see the status for Yolink in AC? Quote
sjenkins Posted Friday at 12:20 AM Posted Friday at 12:20 AM 4 minutes ago, bmercier said: Can you see the status for Yolink in AC? yes Quote
bmercier Posted Friday at 12:56 AM Author Posted Friday at 12:56 AM 33 minutes ago, sjenkins said: yes Then I can think of one possibility. There is a known issue in the current IoX release that would affect eisy-ui, but not the admin console. That will be resolved in the next IoX build. To confirm that, open eisy-ui, open the browser console, and navigate from another node to your Yolink node. You should see and error related to a missing "editor". Quote
tazman Posted Friday at 03:05 AM Posted Friday at 03:05 AM 13 hours ago, bmercier said: > the status are coming through on eisy.local In eisy-ui? AC, UDM? > except for the yolink plugin does not show for my temperature sensors. What is it that does not show. The properties? The status values on the properties? Is that in eisy-ui, or AC and UDM connected on port 80 or 443? > the status are coming through on eisy.local In eisy-ui? AC, UDM? I was referring to the eisy-ui For the yolink plugin I see the same as what @sjenkinsposted in his screen shots and it also shows correctly in UDM. I think the issues I s waseeing with UDM might be related to the portal issues of lately because I did see it work at times today. Quote
GTench Posted Friday at 04:26 PM Posted Friday at 04:26 PM 15 hours ago, bmercier said: To confirm that, open eisy-ui, open the browser console, and navigate from another node to your Yolink node. You should see and error related to a missing "editor". I have the same issue as @sjenkins Not sure if this is exactly what you mean but I opened the nodes screen in eisy.local, selected a non Yolink node (shows properties correctly) then selected a Yolink node (no properties shown) but I do not see any error message Not sure if this is at all related but I notice when I add in a Yolink node server, the Yolink devices show up scattered among all existing nodes in the AC. That is, they are not automatically grouped under a Yolink master node Quote
bmercier Posted Friday at 04:30 PM Author Posted Friday at 04:30 PM 1 hour ago, GTench said: I have the same issue as @sjenkins Not sure if this is exactly what you mean but I opened the nodes screen in eisy.local, selected a non Yolink node (shows properties correctly) then selected a Yolink node (no properties shown) but I do not see any error message You would not see an error in eisy-ui. It's in the browser console. Use the same steps, but look at the browser console (F12 on Chrome, tab "Console") Quote
GTench Posted Friday at 05:33 PM Posted Friday at 05:33 PM 58 minutes ago, bmercier said: You would not see anu error in eisy-ui. It's in the browser console. Use the same steps, but look at the browser console (F12 on Chrome, tab "Console") Interesting. I see errors when I click on Zwave but not insteon or Yolink or other node servers like weatherflow. Here is what I see in the console Quote
bmercier Posted Friday at 05:38 PM Author Posted Friday at 05:38 PM 4 minutes ago, GTench said: Interesting. I see errors when I click on Zwave but not insteon or Yolink or other node servers like weatherflow. Here is what I see in the console The 5 errors at the bottom should be fixed with the next IoX update. If Yolink does not give you a similar error, then I need to investigate further why the status are not appearing. Quote
sjenkins Posted Friday at 09:24 PM Posted Friday at 09:24 PM (edited) I get the above, the last line will come up when I select any node except for the YoLink. It will repeat if I select another node. No additional lines come to the console when I select a YoLink node & receive no parameters. Edited Friday at 09:26 PM by sjenkins Quote
bmercier Posted yesterday at 01:21 AM Author Posted yesterday at 01:21 AM 3 hours ago, sjenkins said: I get the above, the last line will come up when I select any node except for the YoLink. It will repeat if I select another node. No additional lines come to the console when I select a YoLink node & receive no parameters. Ok thanks, will investigate further. Quote
apnar Posted 9 hours ago Posted 9 hours ago On 6/7/2025 at 8:13 PM, bmercier said: Make sure to login with your portal credentials. Everything on port 443 requires portal creds, not IoX creds. To get back to the regular IoX, I'm pretty sure an upgrade packages would do it. But I don't think that would fix statuses though. @bmercier Is this the future direction of the platform or just short term for easy testing? One of the main appeals for me of the ISY devices over the years is they can be run 100% locally with the cloud stuff being optional. Tying local device management to cloud credentials would obviously contradict that. Regardless, exciting to see a replacement for the admin console in the works. I have a straight forward all Insteon setup and the install went smoothly. Only annoyance was having to add a manual entry for 8443 back to the launcher finder as mentioned by others. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.