Panda88

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)

Both vibration sensor and speakerhub are supported with YoLink node. My guess is you want a small program that when the vibration sensor triggers triggers and action like saying somehting on the speaker hub, but it could be anything

AC it is the airthings account I am referring to

It is what I am trying, but it keeps being set back to the default (60) after restarting the node

It is the device - not the tree - The account combines different devices (different locations in my case) and I only want the one to show up that is "local" to the eISY

OK - I think Emporia just reports all 16 - I only have 8 connected to the device

Is there a way to only select one of multiple devices registered on the account. I have devices in different houses and only need data from one of the locations Are there hidden parameters to hide some of the devices

Is there a way to limit the number of nodes - i.e. I only use 8 sensors - but it defaults to 16

got it

Hi Installed the trial version - I have 2 AirThings sensors so I am supposed to set the poll rate to more than 60 sec - however when I do so after restart it reverts to 60 sec and complains - is this a bug Also, I noticed the particle count is not reported 2025-02-02 18:21:09.641 Thread-2173 (handler_poll) udi_interface WARNING Sensor:query: Unknown param pm1=0.0 2025-02-02 18:21:09.641 Thread-2173 (handler_poll) udi_interface WARNING Sensor:query: Unknown param pm25=0.0

Can you send a log with debug enabled - That way I can see if an error occur preventing the update to happen Are you running local or cloud?

I did not do it, but I can give it a try - was trying to keep system "clean"

Hi This is a heads up - Tesla is planning to charge for access to the API. We are working on an option for streaming changes to the car (vs. polling) and this should be lower cost, but is still work in progress. Note this only works for newer cars + 2021 Suggest to lower the update rate to the case and only wake it if it makes sense When developing the streaming option - are there fields of interest that should be added (I'll see if it is available) - there is a lot more data available

hi I get the following message after installing with a VUE3 device 2025-01-25 22:22:54.449 MainThread udi_interface ERROR udi_interface:write: import boto3 2025-01-25 22:22:54.449 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2025-01-25 22:22:54.449 MainThread udi_interface ERROR udi_interface:write: : 2025-01-25 22:22:54.450 MainThread udi_interface ERROR udi_interface:write: No module named 'boto3' any ideas?

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

found the bug - I think the doorbell will update if you press it It is difficult to test as the LockV2 reports data different compared to the old lock (which I have) Is it ok if I wait to release a new version - working on getting the dimmer to work in scenes - should be a few days (I hope)

Can you send a log again?