
Panda88
Members-
Posts
697 -
Joined
-
Last visited
Everything posted by Panda88
-
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)
-
Just a quick update on the local support for YoLink using hub YS1606 It is working well so far - I have a device that appears offline with the new hub (IRremoter) - it works if I move it to cloud (the node allows both ways of operation)- but get off-line replies once in a while even in that scenario It appears to be transparent if operating local or via cloud from the node perspective. I could release a beta version if there is interest, but it seems the hub is not fully released yet Let me know if there is interest in a beta
-
The new streaming node server for Tesla EVs have been released as a 90 day trial to the main (production) store The node uses streaming services, so the EV only sends data to the node when the data changes. Given this there is no need to poll data, and as a result there is less battery drain on the EV. Short-poll (5min default) sends a heartbeat and updates the EVs connection status (online, asleep, offline etc). Long-poll (2 hours default) check and updates tokens required to maintain the connection. A few more data fields have been added, and sentry mode control is now supported. It is expected that existing nodes will need to move to this node/model, as this is the preferred use model by Tesla. If more data is desired, check the list of available data at Available Data | Tesla Fleet API and request it to be added
-
- 1
-
-
I did post a new version to fix it
-
I think you are correct that something is wrong - It is a raw number from the API - it may be reporting in BAR and not PSI- so you actually need to multiply the number by 14.5 I believe - I'll fix it
-
I think this is a question for UDI - They are in charge of the payment system. Yes - we are testing how reliable the new approach is - data is running through UDI servers - I think we are getting close, so there should be an official release soon The new node has some real benefits - i.e. it will use less battery of the car, as it only updates data when there is a need. There are also a few more info fields and support for sentry mode.