tazman

Awesome Panda88 you got it! The node created in the AC is now called EV1 instead of the car name which does not matter to me and everything looks good to me initially. Thank you for your quick response!

I did have the log on debug and I don't notice anything else but I can PM you the log later today to see if anything else looks wrong to your trained eye. Thanks for the quick reply!

Is anybody else having issues with the node server working? I'm getting this error 2023-06-12 20:08:49,313 Thread-6 udi_interface ERROR TeslaEVController:createNodes: Exception Controller start: 'display_name' 2023-06-12 20:08:49,313 Thread-6 udi_interface INFO TeslaEVController:createNodes: Did not obtain data from EV I tried redoing the refresh token but it did not help and I'm wondering if there is an issue because Tesla changed something.

I have a Blink camera system including the door bell that I'm mostly happy with but I know they have added fees where I don't have a monthly payment with my older system. I also have some Reolink cameras the I stream to a monitor for constant viewing at home with a NVR connected. I could never get the Reolink motion sensing to work well to use the notification portion of it but other then that I'm happy with the Reolink cameras.

Have you tried pressing the multi function button 4 times to reset the network settings?

Also don't forget to check if the programs are in a folder that might have a condition that is preventing them from running.

Just to wrap this up I found a Z-Wave device that died and was not responding any more. I deleted the device from eisy and have not had any issues since.

I first received my Tempest 3/2021 and did not have to touch it until 12/2022 when I had a battery failure and they easily/quickly sent me a new replacement unit and I have not touched it again since then. So before my failure I went over a year without problems but I have a small single story home where the units are less than 60' from each other.

Once you pick a lock from your devices it puts it in as a lock on it's own. If yours does not show as a lock in the portal I would open a ticket with UD because I would imagine the device is not being identified properly in IoX or you are picking the wrong node.

I am using eisy with the ZMatter USB stick and running IoX 5.5.9

I have had all my Z-Wave devices become unreachable and the only way to get them back is to reboot eisy and after the reboot Z-Wave is operational again for days until it happens again. I have submitted a ticket and just wanted to post here to see if anybody else has experienced any similar issues.

Did you have sentry mode off? Do you have FSD and if so do you have smart summon turned off? Do you have any other programs that you gave access to the car?

It looks like mine goes up to 2.75 during the day and drops to just under 2.7 over night.

No we were not sure if the short poll was waking the car so the idea was to set the short and long poll around the same time so it was not constantly waking the car. In my opinion pending on what you are using the node server for there probably is not much value in constantly polling the car.

On the Configuration tab it has a short poll and a long poll and my understanding is that the short poll is suppose to pull the information from the cloud and not wake the car but I don't know what information is updated with it. The long poll wakes the car and I assume updates all the information. Maybe @Panda88can confirm if my understanding is correct and if both should update all the information or not.

I have my short poll set for 86399 because I was worried about waking the car. I recently installed a Bluetooth 12V battery monitor and just ran a test and changing the short poll did not wake the car so I'm going to set my short poll to 14400. I usually charge my car over the weekend using the excess solar with programs to control the charge rate and query the car to have the information updated when charging starts and stops since I display it on my mirror. I have a trip coming up and if I remember I plan to stop the node server so it doesn't add any unwanted drain on the battery for my trip.

Yes the PLM will work in any USB port with the proper cables.

@asbrilglad you got it working and I hope this is a reliable solution for you.

I will say your electrical situation is unsafe and not proper but will not harp on that, it is up to you what risk you take. Have you tried controlling maybe the HVAC from the node server to verify your connection to the car? If you are trying to set the charge rate while the car is sleeping it might not get through.

That is you problem right there!

The mobile connector with a 30 amp end should only allow 24 amp if it is drawing more then that something is wrong. If you plug in it should say 24/24 amps and if you lower it to 20 amps on the screen of the car it should remember that setting for that area but my thought is if there is no GPS signal it might not remember it

You did not answer what you are using to charge the vehicle. If you use the mobile connector with a 30 amp plug on it the car will know it is a 30 amp circuit and will be limited to the 24 amps. If your car does not get a signal in the garage there probably is not going to be a reliable way to set it other then the device being used to charge the car being setup properly to tell the car what is available.

@asbrilthe car should remember what is set for each location. Can the app access the car when it is parked in the garage? How are you charging the car? If you are plugging into a 30 amp receptacle the charging should be limited to 24 amps. It sounds like there is something wrong with your charging setup and it is best practice to not rely on the vehicle to limit charging.

@toddlockfor PG3X you use the same password as what you use for ISY login.

Depending on your lock if you look through the options in creating a program I know my lock shows "locked" "unlocked" "jammed" and "unknown" that you can write a program to notify you when it is in any of those state.