sjenkins

@bmercier , sorry I wasn't clear. When I log in the AC on port 80/443 with portal credentials the developer local nodes do not update & stay mostly blank ; same on the browser eisy-ui. Log in the AC with port 8443 with local credentials and they update. This is just for nodes on locally hosted plugins I am developing, no issue if I run it beta.

@bmercier Not sure if its a known condition but the status for nodes from my local plugins, which I use for development do not show up in the eisy-ui or the AC when I log in with my portal login. They are mostly blank. When I use the 8443 port and log in with my local login the status in the AC updates. Bit of a fringe case I know but I banged my head for an hour before I tried to log in with the local AC.

That made me laugh! (and I will use the Alexa equivalent with my family)

Two Three questions/observations: Unlike other node servers where the controller shows off-line when stopped I see that YoLinkSetup stayed "On-line" when the nodeserver is stopped. Is there any other indications? the speakerhub shows up as a device on both the nodeservers. Local hub does not show as a device in the AC but does in the configuration (it gets added automatically). Any plans there? will the speakerhub respond in local mode with the internet gone? Obviously I will test this, it cannot be added to the local network in the local-hub but it is on the local network.

So far testing of the beta plugin is good. Added my devices to local hub and starting to use its plugin as main. What I’ve done to skirt the slow update thing is stop the production (remote only) plugin. I’m putting in my ISY programs so they can use inputs from either plugin based on which one is running. this should allow me to survive as @Panda88 works his plan towards production and maybe one plugin to rule them all. I use YoLink for Leak sensors, temp/humidity, garage, and water valve. They are great for those things. So far I’m a happy chappy , I’ll let you know as I see issues, but so far so good. Going to pull the internet next & see if the point of this whole endeavour holds true.

@Javi unfortunately the new version, 1.2.12, is still crashing when I edit any favourite and try to change the display status. Rebooted my phone and thought it was going to fix it as the picker came up but then crashed when I picked. Next time crashed as soon as I chose display status. Both with old and new favourites.

I added one temp/humidity sensor to the local hub. Looks like that’s all you do is add it in those settings. Back in the app’s device screen there was now a symbol in that devices’s square like an Ethernet symbol. When I checked the node on the plugin there is a field for type of connection but that was blank for this and all the nodes which were added. @Panda88 is this a future feature? My next steps in testing was to: 1. simulate internet down and see what works. 2. Move more devices over 3. Move my programs over & disable the old ones. 4. not with plugin but was going to play with the local automations. Might still use those for the leak sensor to house water valve. question, is there any value to the old hub now except that it has a speaker (understanding we are still in beta on this plugin, so post beta)? are there any “duelling banjos” problems with two that you have seen?

@TJF1960 thank you for the kind words. Also, you are right the plugin does the heavy lifting and gets the access code for you. Like many here I am a bit of a geek and want to know how my new stuff works. The curl or python script is for those who want to talk direct to the device like plugin writers. But I am glad I did it because I would have been blaming @Panda88 when his plugin didn’t work! If someone isn’t up to curl and is having issues I could share my script as a setup/hardware tester to see if comms is happening.

So tech support got back to me this morning and told me they had pushed Firmware 0606 to my unit over night. And **BOOM** everything works as advertised & I no longer feel like I am insane or an idiot !! For those who have a box seeming like it is working in the app but will not talk to your curl or request to get the local access key, keep this in mind! now maybe I can test this plugin out....

Appreciated @Panda88, unfortunately still getting a timeout error. Was good to validate your python version with mine versus the curl equivalent. Still waiting for tech service to get back to me. So I can continue to pull my hair out can you verify the "obvious" for me..... 1. you are using port 1080 in your URL 2. the client secret starts in sec_v1_ and ends in == , those are included in the text sent 3. you don't use the button on the back for anything during this process, correct? 4. I have mine set-up with both ethernet and wifi and have tried both ; what do you use? Thanks for any breadcrumbs....

I have a ticket in with YoLink now. Just to understand in my communications with them has ANYONE besides @Panda88 been able to get the local-hub to give you the Access Key ?

Version 0.5.4 Thanks for the fix on the folder memory, checks out. Maybe for the TODO list. One nice feature of the AC was the ability to click on a node then to move up/down the list with cursor, opening and closing folders with left/right. For us old school keyboarders (I am known for using Emacs) that was really nice.

Tried out 0.5.3 You can see it developing, step-by-step, I like the node icons. It crashed once on me with a message about compressing, but I couldn't get it to repeat. I will document next time. If you compress any groups/folders then select a node it immediately uncompresses (assuming reloading the whole list), this means that you lose where you are in the list. I think you mentioned before that an ISY update was needed to fix this & get it to remember when you open/close a folder/group? Just ignore me for now if this is in the pipeline.

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