Panda88

Enable debug and send me a log (you can PM me) - I'll take a look I do not know how devices instantiate and I do not have one yet - just ordered the new one with shutoff valve. I believe it should be an easy add once I get a log

I am not expecting a special version for you - just for you to test if it helps before I would release it as a new version (there is no need to do a new version if it does not help) Nothing obvious in the log (from my side)

I can provide a non-production store release with traditional config file to see if that fixes your issue Let me know and I can prepare it - if OK I'll make a full release of the node

It may be related to you setup with separate ISY - any particular reason not running it internally on the Polisy? I know this node has some "optimization" on how the NLS file is made and I wonder if that could cause this - I can try to change it to not use common NLS settings - I know it affects the REST interface in some cases

I do not have this issues in my setup - both status and control work for temp sensors Can you try to install in a new slot - just do a backup before you try it Note, you can use condition - it is the internal trigger (high and low warnings) level set in the yolink app - and it is actually preferred as it updates quicker than status, but you can only use one of the two if you cannot get the condition I guess Are you fully updated on AC and PG3x?

I would create a ticket at UDI and mention your can is too old to support the streaming version. UDI operate the store You actually did not need to erase the old to try the new The app is no longer needed - not even for the previous version

Yes - too old I guess You should be able to find the previous version in your purchases and reinstall from there

It seems your car or FW is too old (not supported) or the key is missing 'response': {'updated_vehicles': 0, 'skipped_vehicles': {'missing_key': ['5YJSA1E44GXXXXXX'], 'unsupported_hardware': ['5YJSA1E44GXXXXX'] The following requirements exists The vehicle must not be a pre-2021 Model S or Model X. Vehicles must be running firmware version 2024.26 or later Note, this is a Tesla limitation

It looks like it is working but I need more time from log - it can take a few mins before data starts flowing - it seems like it passed the test this time

I need a little more of log time - log stops before data starts to flow Do you have a firewall that can prevent the communication?

did you restart the node? I did not find it in the log

Can you try again - seems there was an infrastructure issue causing some users not to work properly

Giv it a try again - seems there was some infrastructure issue causing some commands to be lost

If you can enable debug and provide a log maybe I can check if there are any errors - I have not found a way to force an update of the data - The car decides when to post data - I have a minimum of 1 min between updates on most data (non-charging) - I could try to lower that. Note, the data from streaming is different from existing polling (and it is way more expensive to execute a poll) There is a newer beta on the non-production store with powershare data enabled - maybe you can try that one

you have to scroll down to see the result of the test Did you do the following to enable webhook - It looks to me webhook is not working (from readme) Additionally, one must open external access on the eISY/Polisy. Go 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).

Can you run the test button - the results shows below the time on the main page - did you enable access as described in the readme through ISY portal - Also - send me a new log with more data

looks to me like you just need to wait a little longer - las line of the log just achieved sync with the streaming

can you try TeslaEVpwrSh in the non-production store. It is supporting powershare but it should not affect your car. There is some strange bug I believe I fixed in this version I am close to release this version as the real version

Did you press authenticate? Did you ry the test button to make sure you can communicate through the portal? It seems it is not getting the token If still an issue enable debug in log and send it do me

Yes - that should work - the local hub controls the devices (not the cloud) - it then sends the control data back to the cloud to the app - This allows EISY to control even without internet access.

Good to hear Local is mostly limitrd to the availability of the local hub. You can not extend you network with additional hubs (presently all local devices must be connected to the local hub). A few devices are not working for me but besides this it i stable for me I have not deployed it fully in my home due to the lack of ability to expand network (i have a few critical devices in my pump house that uses its own hub)

Yes on notifications For settings you select the home Go to user -> advanced setting and create credentials for that home (copy them to the first eIsy's yolink node) The switch home and repeat and copy to 2nd eisy It is good to note what credentials go with what home as it is not clear in app

They way I handle this is to create multiple homes in the app - each home has separate credentials so you can run 1 home on the one eISY and 1 on the other - there is a way to switch between homes in the app and Favorites can combine the 2 homes This should work well for local as well once the release the hub (there are still some device I cannot make work with localHUB but SW is in beta so expected)

I so not believe it is related to the yolink node server. Linking is between Amazon and yolink app

Ok - I'll keep working on it here - let me know when the hub becomes available? (I need to get one more as well)