sjenkins

No problem doing that. I currently cannot get the curl to respond for the access key. Did the given instructions work as written for you @Panda88 ?

after following the included documentation with the local hub at: https://www.yosmart.com/support/YS1606-UC/docs/instruction which will get you the client_id , client_secret , and local net ID the below is the specific to get the access token http://doc.yosmart.com/docs/overall/qsg_local with all the above and the ip you can fill in the config of the local yolink plugin

Received my unit and set it up through the app. All is fine in app, Got the customer number & customer pass I need setting up the local network. Ran the curl statement to get the access token and no joy, just times out. Tried from a few computers & played with the curl. Just even to get an error response, just server time-out. Are the instructions right on or did anyone need to play with them? I did not add any devices yet to the local if that matters. I know this isn’t a node question per se but appreciate it if anyone has some breadcrumbs. btw: the node did install just fine ; didn’t get all the data it needed because of above.

@Panda88 I’d love to start playing with a beta now that my hub is here within days. Understand the limited support with you travelling, but could start generating questions and feedback for discussion. I’d also like to play a bit myself with some direct programming to understand it, your beta will be a useful jump start for that. thanks again for your work on this ahead of us, your current plugin is well integrated in my system.

Thanks for the heads up! Just ordered mine as well.

thanks @bmercier , Lots of good stuff here in 0.5.1. !! note for everyone: I did have to clear the cache to get the new version to load in my browser 😀 New Portal Authorisation page under Settings 😀 Login with no connectivity ❓ icon search with synonyms (not sure what this is) 🤫 Nodes page: Added folders - (they keep closing ; need memory like AC) 😀 Nodes page: Display names in the tree instead of the address 🚫 Fix for Yolink (still blank detail screens) 😀 Dimmers can now send a DOF when turned to 0 😀 Admin Console save function is fixed

sorry @TJF1960 , I am not having reboots, portal, or Alexa issues

@bmercier Not sure if its on your known todo list but with the new eisyui service running.... I CANNOT save a program change in the AC when running it from port 80 with the portal credentials. I can edit but it will not save. Sometimes a pop-up with a save message comes up but usually not. I CAN edit and save in the AC if I run it using port 8443 and local credentials. Again, both are with the eisyui service running.

Yes the YolinkSetup node works as expected with status as "OnLine" and the details filled in with other details. All other Yolink nodes show a status of "1" and blank details screen. see attached images.

I just pinged them again today ; will report back here.

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.

yes

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

NOW I get it. I may be the only slow one but for others maybe. With eisyui service stopped it looks like before, listing my eisy with local ip and 8443 port. (Was going to insert pics but I can't upload files as the forum has been giving me 200 errors all morning) With the eisyui service running it finds my eisy with normal local ip and no port listed (assuming 80) I am understanding from bmercier that this is intended condition.

Just to explain again: I use 8443 with a local ip address and local logon I know 8080 is there as the base use but I thought with EISY that was turned off, so I don't use it. for some reason this "went away" in the AC logon screen & was replaced with the same local ip but with no port (80 I presume) that's where the popups show up. when I add back manually an 8443 with local ip, local login all is fine. I think the only oddball thing here is either with the new ISY or with the eisyui, it seems to be advertising the 80-port logon. if I use the non-local ipv6 ip and non-local login all is ok as well. not really a problem for an advanced user but will be an issue with others @GTench is this the same for you?

yes I am PM'd you my log from startup, login, to shutdown of service

That is after login and only on the one without 8443. Again the manually added one with 8443 works fine in the admin console. on the Eisy-ux, I think I did see status in the old version ; I can do control just fine. I didn't do any testing after changing to the new ISY version, worked fine before that, just don't know if something after that changed things.

So this is new as of today, see my IoX launcher, ignore the Polisy obviously. The eisy without the 8443 is populated automatically & if launched does not work properly, comes up with a: The one with the port 8443 I had to add manually and works as expected. Is this related to the last issue? btw: : I did do a reboot to "cycle the power". I did update my ISY to the 5.9.1_21 version. also, to answer one of your questions Insteon & plugin nodes, so all of my nodes show no status.

Yes, fixed, & thank you. Should the status column in nodes be populated? The controls work fine but the column is blank & in the details pop-out status is just shown by the label, no content.

@bmercier done.

@bmercier I upgraded to isy-5.9.1_21.pkg, needed to reboot to get isy service restart as it was Waiting for PIDS: xxxx forever. Didn't solve the nodedefs missing issue. When I do the "troubleshoot further" uri: https://eisy.local:8443/rest/nodes/55 79 DE 1/profiles it works fine and gives me data: {"timestamp":"2025-06-07T09:35:58.609185-04:00","families":[{"id":"1","name":"","instances":[{"id":"1","name":"","nodedefs":[{"id":"BinaryAlarm_ADV","properties":[{"id":"ST","editor":"I_OL_RELAY","name":"Status"},{"id":"ERR","editor":"I_ERR","hide":true,"name":"Responding"}],"cmds":{"sends":[{"id":"DON","name":"On"},{"id":"DOF","name":"Off"},{"id":"DFON","name":"Fast On"},{"id":"DFOF","name":"Fast Off"}],"accepts":[{"id":"QUERY","name":"Query"},{"id":"BEEP","name":"Beep","format":"/level/${c}/${c} ${v}/","parameters":[{"id":"","editor":"I_BEEP_255","optional":true}]},{"id":"WDU","name":"Write Changes"}]},"links":{"ctl":["I_CTL_RELAY_ADV"],"rsp":[]}}]}]}]} To be clear on the eisy-ux still getting: Error loading node 55 79 DE 1: Profiles loaded but nodedefs missing

Just got on board today with 0.4.1 & it sparked up without issue.... oh the potential !!! thanks @bmercier & UDI team !

Just wanted to let the crowd know about a known issue. Came up recently, but its not the first time. I have two hubs and when power is lost, cable is lost, or something else happens I can't identify ; sometimes one of the hubs does not come back & "loses master". Might also happen to one hub owners. So what that means is one of the hubs will be flashing orange/pink or just orange. The plugin locks with 'hub is not master' or 'hub doesn't respond'. Even with a cycling of the power on the hub or hubs, getting them back to blue status the plugin does not recover. Obviously I cannot fix the Hunter issues, unless I add a smart plug to cycle the power ; but I might be able to make the plugin more resilient. Just want everyone to know about it & as well ask if anyone else is experiencing this issue & can provide your context. Thanks!

See above. In my environment I am testing all the devices at once & seem to have a crash about once a month. Anyone else having this issue? If so can you send me what devices you are running & bonus points for logs (if you have them). Just had it crash when my cable company went up and down about a dozen times in the last few days ; was enough else going on that I haven't got to it yet, but this isn't the first time. Wanted to ping the user base. Thanks all !!

sorry I've been slow to respond ; been a busy week, @maxnorth you have a good link there the other way to get to that instruction is from the configuration tab of the MQTT nodeserver installed on your EISY. Basically you can use one of two methods to define your devices, deflist or devfile. The second is the one @TriLife was mentioning. The first is quicker/easier if you only have a device or two but the second is more sustainable over the long haul when you have lots of devices (the extreme being @TriLife). Don't worry if you use the devlist to start off you can easily switch to the other later. Hope this helps a bit. This is a pretty stable plugin now & more than a few people are using it for critical applications. Keep at it. Once you get the first one talking it will come pretty easy.