does anyone know if you had a scene wtih an insteon keypad as a controller would the youlink dim like insteon when the keypad button is held in?

Edited January 2Jan 2 by jkraus

well, I answered my own questions.  I installed the Yolink dimmer in a scene and while Insteon keypads will turn it on and off, holding the keypad button does NOT dim the Yolink

If someone can tell be the command sent from the insteon device, I can see if I can make it work 

In other thread I asked this question:

"BTW if I set the youlink "on Level" to say 50%, when I trigger the scene via the KPL it shoud come on at 50% correct?  (i.e. not controlling the brighness via the KPL, but just setting the "on level")"

I can report that does indeed work

I think it is possble to dim Yolink from an Inseton switch, but operation is very differnt - Insteon sends a start-dim and stop-dim - I can decrease the level in a loop but it will be difficult matching a rate of the insteon - If dimming using the yolink switch it only reports the new level (after user stops dimming)  - so I must wait until a level is selected before I can send the dim command to Insteon and again the DIM level I do not know how to send to Insteon (only a command to start/stop dimming) - If I know the rate maybe I can estimate the time to send the DIM commands).   I think a program approach is easier 

If it needs to work, we need to specify a DIM rate as a minimum 

1.4.15 is released - it has rudimentary support for dimmers in scenes.  It has a dim-up and a dim-down level you can specify for the Yolink device.   Once an dim up/down is received by the scene yolink dimmer will move to the set limit.  Similarly if the yolink dimmer detect light change it will dim up/down for time equal to the ramp time specified for the yolink device (app setting) times the % of light change.  Say the dimming range is 50% to 100% with 2 sec ramp up time and a change from 50% to 75% is detected (50% of the range) it will send a dim up command for 1sec (50% of 2sec)

It is the best I can come up with as there is no dim time for yolink - is just reports the change when done.   Note, the above will happen after the yolink has it new value (as there is no way to know it is dimming until done)

There are a few other improvement and new devices supported in this version as well.  Note, It also move to report last update time as a readable time. UDI will add a time.now function as a parameter that can be used to determine the time in seconds from last update (in automations)   

@Panda88 First of all let me thank you for the Yolink NS.  I have been using Yolink for a while with remote temp measuremnt, but only recently started to integrate them into the Polisy.  The results are so much better than I am having with Kasa device as the NS continuously need to be rebooted, so thanks much!

 

Regarding the  dimming function, are you saing you can control the dim from an Insteon KPL in a scene, or by program?  I turns out that controlling from the KPL is not as important for my application as I thought it would be, but still curious

 

 

I believe it should work in scenes with a specified fade level 

I tried updateing the NS three times and it seems to then reverts back to old revision

Did you update to latest ISY FW 5.9.1?

There are issues with previous fw to update nodes.  Lastest works from what I know

no

OK, I was sooo happy the Yolink NS was stable and such a good replacement for the Kasa NS which I had to reboot every couple of weeks...until last night where I had to reboot the Youlink NS as it stopped working.  Interesting when I did reboot it took quite a while for the nodes to be recognized again despite the NS being connected

 

Also, I could not upgrade the NS to latest as not on 5.9.1 yet as there seems to be a lot of people with problem upgrading

It does.take a long time to restart the node.   It is caused by deliberate delays needed to ensure the api is not overloaded by calls to the yolink server.   There is a limit of calls per minute Once restarted everything is back to normal.   This is done to handle systems with many devices

The upgrade issue is related to the FW and not the yolink node.  The node relies on the FW to perform the upgrade