sjenkins

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.