Panda88

I think it is because some of it is cached when the AC starts so it is not aware if changes are made

Did you try a reboot?

Keep fingers crossed - continuing to work on it - I will have an updated version soon - with some more bug fixed

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

Did you restart the node and enable debug. If so then I believe I have what I need. I'll check later

To be honest it may not be the case. Can you send me a log file and i can check

I have had some issues with the release system - trying to get the bottom of this

Working on the update issue Can you send a debug log with the heated steering wheel. I honestly don't know the difference on pre condition it is just available api calls there is minimal documentation Update updates all data - it is just not propagated to the screen. In programming you should be fine. I plan to remove the options on the other nodes and only keep status I am having issues with publishing updates so this is why it has not been released yet

Done - takes a few hours to propagate

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

I see the problem Let me take a look and see if I can figure out what is happening - it is likely in the node definition