Panda88

Found the issue 
I'll make a new version in a few min 0.1.25
It was a node definition problem

Found a bug - try 1.2.5 just released 

Can you send me the log file - you can message it to me 
Did you make sure there is no space at the end of the UAID and Secret Key 
Just to be cleat - the node shown is the PG3 node (to show it state) - it is not the HUB = there is no node for the hub as it offers no functionality - there are no Yolink devices imported 
 

i looked at it before.  did not find an easy solution.  it has been a while so it may be possible but it will take some time
i usually handle this by running a special program on boot of ISY

Erasing the node in the node server (PG3) does are bigger reset that from the AC - You need to find it in the list there 
I doubt it helps when a new node does not work - but may be worth a try 

Try now - I did forget to update the version number in the code - you should be running the latest already but update message should disappear now 

It is always difficult to handle connection when there are multiple connections - one is from node to ISY - the other is node to YoLink API
I have used ST (shown above to show connection to ISY
I have used GV20 to show connection state to Yolink API
I believe the leak sensor should be fixed in 1.0.7
 

I replied already - you need to generate UAID and secretKey in the yolink app and copy them to the configuration of the node server 
 
 

OK - I though you had the flow meter as well 
I believe this is the same API as the manipulator that is/was used to control valves before.  The name of the node is what you specify in the YoLonk app (short of special characters) - the yomanipu is the manupulator driver.  This shoudl work fine 

Sorry - it is not possible to control these parameters from the provided API.  There must be a superset API, but it is not publicly available

Can you try a new install - I am not able to update the node store, but if you install now is should pick the latest code.  
There are changes in the structure from tesla so there may be other changes needed in the code, but I cannot test as I do not have a car
 

Try 0.8.90 - should fix the issue

Did you try to upgrade from the AC - I heard there was a bug the prevented deletion of files in a prior version

Added sensor  temperature reporting for 0.8.50.  Let me know if it works.

Latest release (0.8.41) has a possible fix for the X3 - I cannot test as I do not have a device - The X3 sends data in a different way  If there are issues, please enable debug log and send log 
 

Late, but you can run PG2 and PG3 in parallel

Strange - it is doing exactly what it is supposed to do - It says is does not see any changes in node-defs - (which is true) - 0.7.5 corrects a few spelling errors -that is all 
I am not sure - it is possible the SW is too smart and does not upgrade because it does not see a change.  The changes actually end up on the ISY 
I just received the power-fault detection device and will add this soon - I believe that release will force an update for sure as I will be adding a new node type 

I see a smartRemoter API.  I assume that is the remote.  I can buy one next time I buy devices and then try to integrate - unfortunately I just bought some so it may be a little while - I'll add it to the list

will do
thanks
Christian

List is up to date.  I did not get a thermostat yet, but It should not be too much effort to add it 
If you are willing to work with me (or let me access it for a little while) I can try to add it
 

0.2.18 hopefully fixes it - there was one more conversion bug in the code

0.7.2 - I see it inthe production store - maybe try to refresh the store

Just released version 0.7.0 - I believe it resolves the resource use
 

I think I fixed it - I made a wrong commit about 12 days ago and that code caused this to happen 
I am working on redoing the message handling and hope to have a new and improved version soon