Panda88

On the polling issue - If you are automating maybe poll once a day and then perform an update as first step in your program used for your automation. I assume you are making decision in programs, so when these program execute you can update the data before making the decision. I assume it is a few times a day keeping the data calls to a minimum. Naturally, if you look at the AC and want data updated polling would be needed

We are working on a streaming option where data is only updated when data changes so polling becomes less of an issue.

I was told in the fall the local Hub would be different from the cellular one (Hub3) - They likely need more horse power for the local integration - apparently the CPU is different in the local hub than what is in its documentation

I received mine. It is still beta but you get it cheaper

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

Looks like the Local API is simple for now. No MQTT so we will need to poll devices for now. . Hopefully the will support in future

You likely need the new local hub device - it is supposed to be in beta stage - there is some discussion on the HA forum and discord

I ordered the new HUB required for local control. Did not receive it yet. My understanding is it is in Beta and there is no API to control it yet

Try to run the update once more. The send me a full log with debug enbled. I do expect it is some missing file - note the installation is handled by PG3 and not the node itself I have some time in a plane thursdy

I have seen the same. I believe is it related to the eIsy i did a reboot /power cy le and IT went away. I am travelling but will check for updates to the mqtt package to see if there could be some fixes there

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

I think the new version solves the upgrade issue (OS14)

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

You do not need eIsy for that. You can do it with yolink app. Naturally you can also do it with eIsy

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)