Panda88

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

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.

I have been playing a little with the local control - it seems to work well at the basic level. Hybrid works well with some device having local control and others still on cloud (but I see no reason to have could devices as functionality is the same for local devices (naturally you need to register the devices on-line (cloud) and then move them to local later). APP shows a little delay when controlling local devices, but ISY control works well - naturally local control without cloud access will most likely not work with APP I still have to try to go completely off-line, but it should work - the issue is more how the system recovers after an internet outrage I need to understand how the solution works with multiple hubs (one local and rest traditional) on the same network (LAN). I have asked yolink, but did not hear back yet I probably need to separate the code into a new nodeserver but time will show

The new hub is ys1606 - the ys1605 only supports cellular - it was supposed to include local support, but as far as I know the plans changed - the 1606 also supports cellular BTW

They just provided me a beta of their local MQTT solution. It kind of eliminates the need for local vs cloud - it is using local if the device is registered locally (and send info back from hub to internet if connected) and uses cloud if not registered locally so there is really no need to select a mode.

How do you guys envision the local integration - For now the functionality is limited and requires polling of devices. It is a hybrid model where a device can be controlled both local and via cloud - with more functionality in the cluld control My thinking is using cloud if connected, and if the device goes off-line fall back to use local. One could also go local first and only use cloud for advanced features - Once they get MQTT working on the local hub local could go first with advanced features using cloud Let me know what approach is preferred