garybixler

After inadvertently deleting eisyIOX from the ISYs in PG3 I am unable to add it back. I did a factory reset but it is still not showing up. Did the add ISY with all the parameters but no luck. Did this countless times. Any suggestions appreciated. Thanks Gary

Similar issue as @brianswith the ZEN 17.

I tried a factory reset and re-including. It does work with default settings in the config. But when I set the input type to 10 it won't pick up the additional child devices doing a synchronize with interview. The manual suggests doing an exclude and re-include but that just sets the Zen 17 back to defaults. I tried the write changes but just get errors. Not sure how to save the config so Z wave can pick up the new devices.

I found an issue with another two devices. The Zooz ZEN 16 does not have all its interfaces loaded. Should be 3 switch inputs and 3 relays out. The Zooz ZEN 17 seems to have all the interfaces loaded but the switch state is not being seen by the AC. Tried many things but no luck. The Zooz 71 switches seem to work fine. Just information as I am not using Z-wave for anything necessary. Thanks Gary

I am not getting a status update from one of my z-wave devices. Aeotec by Aeon Labs Nano Switch. Its a small switch that sits inside a switch box. I can turn it on/off from the AC but if I switch it on or off locally the status never gets updated on the AC. I see no device traffic in the event monitor if switched locally. It did work with the Zooz stick. Tried different settings but no changes. Thanks for any suggestions. Gary UPDATE: I found the issue with my Nano switch. Home Assistant forum mentioned a parameter not mentioned in the Nano switch documentation. So after trying a few values I found the one that works. Parameter: 80 Value: 2

All is working now. I installed the latest version, deleted the nodes, restarted and did a discovery. Also did a query on the thermostat to load all the values. Not sure if that was needed however. Thanks Gary

One more.

Two snapshots of the program. It does work using fan state

Just checked and it says 3.0.10. I had updated when that version came out. The Heat/Cool state shows correctly on the AC but fails to trigger a program. I tried a restart but with same results. I'll keep testing.

I believe I captured the event on the log. Edit: added debug log. New Text Document (3).txt

I hadn't used this parameter before so I checked it out with the latest release. Unfortunately it didn't seem to work. Tried with state heating and state off (idle).

Just finished up installing into the NS and all is working. Thanks so much. Gary

Success. Finely got an IR code. Thanks. Just one question. Do I want to save in hex to copy into NS?

Unfortunately GC doesn't have this code set. I did look for a hole and even took it apart but didn't find any IR receiver. The only hole is for the reset button. iLearn only shows module and connector as capture options. Maybe missing something.

Has anyone had luck with using iLearn on the wf2ir device. I thought that I had done this in the past but now it doesn't seem to work. Is the GC IR receiver absolutely necessary. I don't have that IR receiver so I have been trying to use one from an HDMI extender. Thanks for any insight. Gary

Luckily after about an hour it suddenly started working again. So not sure if was the email to support or their server had to catch up with the change of lowering the forecasts to 5 days.

Unfortunately I only have the one email so I sent an email to their support. Will see what happens.

Same problem but can't find a way to get a new key. Canceled plan but still no selection to get it again. Is the free plan no longer available?

Just wondering if in the future a device could be added to display the value from a variable in percentage. I'll try using the generic light dimmer. Mainly for things light light and tank fill levels. Thanks Gary

Not triggering routines started for me Friday afternoon. Called Amazon and they saw the problem and are now working or it or at least opened a ticket.

I checked after waking the car and it shows car on line in the query. TeslaCloudEVapi:teslaEV_getLatestCloudInfo: teslaEV_getLatestCloudInfo (car is online) RETURN: {'response': {'id': 1 It may be the release that I am at. I can PM a snippet just before and after I woke the car up. The dedicated sleep state sounds good.

I finally noticed what happens when the tesla goes to sleep. I was wondering if this event could be shown as EV Online False on the AC. Would be a nice way to know if a wake command may be necessary or just generally knowing if the car is asleep.. Thanks so much. 2022-10-26 23:19:17,680 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-10-26 23:19:17,681 Thread-92 udi_interface DEBUG TeslaEVController:systemPoll: systemPoll 2022-10-26 23:19:17,683 Thread-92 udi_interface INFO TeslaEVController:shortPoll: Tesla EV Controller shortPoll(HeartBeat) 2022-10-26 23:19:17,683 Thread-92 udi_interface DEBUG TeslaEVController:heartbeat: heartbeat: 1 2022-10-26 23:19:17,684 Thread-92 udi_interface.interface DEBUG interface:send: PUBLISHING {'command': [{'address': 'controller', 'cmd': 'DOF'}]} 2022-10-26 23:19:17,686 Thread-92 udi_interface DEBUG TeslaCloudEVapi:teslaEV_getLatestCloudInfo: teslaEV_getLatestCloudInfo: 1492932395099962 2022-10-26 23:19:17,739 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2022-10-26 23:19:17,741 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2022-10-26 23:19:18,388 Thread-92 udi_interface DEBUG TeslaCloudEVapi:teslaEV_getLatestCloudInfo: teslaEV_getLatestCloudInfo (car not online) RETURN: {'response': None, 'error': 'vehicle unavailable: {:error=>"vehicle unavailable:"}', 'error_description': ''} 2022-10-26 23:19:18,389 Thread-92 udi_interface DEBUG TeslaCloudEVapi:process_EV_data: process_EV_data 2022-10-26 23:19:18,390 Thread-92 udi_interface DEBUG TeslaCloudEVapi:teslaEV_getLatestCloudInfo: Exception teslaGetSiteInfo: argument of type 'NoneType' is not iterable 2022-10-26 23:19:18,391 Thread-92 udi_interface ERROR TeslaCloudEVapi:teslaEV_getLatestCloudInfo: Error getting data from vehicle id: 1492932395099962 2022-10-26 23:19:18,392 Thread-92 udi_interface ERROR TeslaCloudEVapi:teslaEV_getLatestCloudInfo: Trying to reconnect 2022-10-26 23:19:19,130 Thread-92 udi_interface DEBUG TeslaCloudApi:tesla_refresh_token: tesla_refresh_token RETURN: {'access_token': SiO9A9PJQcn1QqbRHnRYJmss9rOBywjrw', 'expires_in': 28800, 'token_type': 'Bearer'} 2022-10-26 23:19:19,140 Thread-92 udi_interface DEBUG TeslaEVController:shortPoll: Controller poll node controller 2022-10-26 23:19:19,142 Thread-92 udi_interface DEBUG TeslaEVController:updateISYdrivers: System updateISYdrivers - Controller 2022-10-26 23:19:19,142 Thread-92 udi_interface.node DEBUG node:setDriver: controller:Tesla EV Info Reporting set GV0 to True to Polyglot 2022-10-26 23:19:19,143 Thread-92 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2022-10-26 23:19:19,144 Thread-92 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV0', 'value': '1', 'uom': 25}]} 2022-10-26 23:19:19,146 Thread-92 udi_interface.node DEBUG node:setDriver: controller:Tesla EV Info Reporting set GV1 to 1 to Polyglot 2022-10-26 23:19:19,147 Thread-92 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2022-10-26 23:19:19,148 Thread-92 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV1', 'value': '1', 'uom': 107}]} 2022-10-26 23:19:19,150 Thread-92 udi_interface.node DEBUG node:setDriver: controller:Tesla EV Info Reporting set GV2 to 1 to Polyglot 2022-10-26 23:19:19,151 Thread-92 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2022-10-26 23:19:19,152 Thread-92 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV2', 'value': '1', 'uom': 25}]} 2022-10-26 23:19:19,154 Thread-92 udi_interface.node DEBUG node:setDriver: controller:Tesla EV Info Reporting set GV

@Panda88 I think the wrong parameter is showing for estimated range in miles. I found two parameters in the download from tesla. 'battery_range': 123.08 which is correct according to app and the car and 'est_battery_range': 167.12 which is displayed in the AC. I can't figure what the 'est_battery_range' is referring to. Thanks

After starting charging it went online so short polling at that time is probably the case. Polling as is I think works the best. I didn't realize short poll worked that way. 0.2.7 corrected mileage. Thanks

@Panda88Hi, I installed the latest version 0.2.5. All looked good and I see the additional functionality without having to reboot iop. The only thing that I see that isn't correct is the 'Estimated Range'. For example it shows 222 miles but should only be 135. I did find what is received down from the Tesla Server. 'est_battery_range': 135.77, which would be correct. Also when I plugged in the charger the info was immediately feed into the NS without the need for any action like wake or update and continues to update without polling. Nice. I have the long poll set for 1 day as not to keep the car awake. The short poll is set for 300. Is it possible that the short poll just polls the Tesla server rather than the car itself? Great additions. Thanks Gary