Panda88

When installing the node a version update should be forced - it needs 3.3.x to support OAUTH. It may be a display issue but this is an issue in PG3. I would contact universal-devices to get help on this one

Create a ticket at universal-devices. They can help

it took me a while for it to take effect - not sure why - check tomorrow and see if it is updated The update is a question for Universal-devices - I do not have any control over this - you need minimum 3.3.6 (I think it is) to get the node working (to support OAUTH)

I am referring to the build of the PG3x - it needs to be 3.3.16 I think it is released now - my other system just updated. Go to AC (Admin console) and select configuration and upgrade packets. It will update for a while If upgraded successfully it should look like this in the web interface If ok try to do an install again

i can reverse it. Make sure you do an upgrade in AC

If you PM me a log with debug enabled I can see what happens

3.3.16 is released - it fixes the update issue for me Working on new Yolink release - should be there shortly

Yes - I can see they added more seats to control as well - not I have no idea how it will be reported by the API

thanks - yes - should be simple fix

Should I remove the rear middle seat heating - It does not seem to be reported. Does it make sense in automations - would you turn on the seat heat remotely?

Universal devices found a bug preventing updates It will get fixed in next release of the PG3x (coming soon) 3.3.14

Can you try to contact Tesla on the APP not installing the virtual keys - it is the first case I heard on new cars (older do not need it)

Can you PM me a log with debug enabled - I do not know what the settlings will look like when writing the node. The Km vs miles - documentation is not clear - I guess it reports miles in API even if display is set to km I am not sure about the app - this is a tesla thing and possible Universal-devices - it maybe they need to allow it in Canada We currently only support NA for the node - but I think that includes Canada

I am aware of the issue - trying to understand what is happening in the node store

Ok I'll look at the log over the weekend or early next week busy today and tomorrow