Panda88

A new TeslaEVstream node server has been added to the beta (non-production) store for testing It uses the new tesla official streaming interface allowing data to update when data changes on the EV - NO NEED TO POLL DATA. This node will replace the existing udiTeslaEV2 node going forward. If more or different data is desired take a look at https://developer.tesla.com/docs/fleet-api/fleet-telemetry/available-data to see what data is available (long list) and let me know. I can try to add it during this beta release Short Poll generates a hear beat Long Poll updates the state of the car (Online, Offline , asleep etc). It also checks if tokens need to be updated None of the Poll gets data from the EV - the EV streams data as they change (max rate is set to 60 sec for most settings). To use the node server, one must install an electronic key on the car On your mobile device open https://tesla.com/_ak/my.isy.io. It should open the tesla app where you can approve the key-install - Older EVs may not support the virtual key. Note, currently only supports NA EVs Additionally, one must open external access on the eISY/Polisy. got to https://my.isy.io/index.htm and log in Select PG3->Remote Connections on the eISY/Polisy Make sure that Remote Connection is ACTIVE To validate if the connection works, there is a TEST button/command on the main page on the node (result shown in the last field in the main page).

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)

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