Diesel Exhaust Fluid (DEF) state 'Green' update needed #278
Comments
|
Could you please set the onstar2mqtt log level to "debug" instead of the default setting of "info" and provide the output of "Diagnostic request status" and "Diagnostic request response" from the log making sure to redact any sensitive information? Thanks. |
|
@almoney, all your credentials are still in the log, so I deleted your post. You should still change your password/PIN for safety. |
|
@almoney, the information I need to make the necessary code changes is not in the log you provided because the vehicle is in hibernation and didn't generate any diagnostic data. Could you please provide a sanitized extract of only the following fields when the vehicle has been brought out of hibernation and provides diagnostic data? I don't need anything else besides these fields/sections: "Diagnostic request status" |
|
Ok, I'm not available to do that until next week. |
|
Thank you!Jeff AlmoneyOn Aug 15, 2024, at 8:54 AM, BigThunderSR ***@***.***> wrote:
@almoney, the information I need to make the necessary code changes is not in the log you provided because the vehicle is in hibernation and didn't generate any diagnostic data. Could you please provide a sanitized extract of only the following fields when the vehicle has been brought out of hibernation and provides diagnostic data? I don't need anything else besides these fields/sections:
"Diagnostic request status"
"Diagnostic request response"
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
I started the vehicle and these are the responses: (let me know if you would like more info.) info: Requesting diagnostics {"timestamp":"2024-08-20 22:39:49"} |
|
Thanks. Let me see what I can do. |
|
@almoney, this might take me a couple of tries to get right. Could you please pull the "latest" docker image (not the latest release because I have not merged the changes into a release yet) and see if the changes I made worked? We can determine next steps based on that. |
|
I did a pull for latest and restarted the container for the Diesel. bigthundersr/onstar2mqtt:latest in Portainer. Is this what you wanted? This is the log minus the VINs in my HA log: Logger: homeassistant.components.mqtt.models Exception raised while updating state of sensor.2022_gmc_hummer_ev_high_voltage_battery_preconditioning_status, topic: 'homeassistant/sensor/VIN/high_voltage_battery_preconditioning_status/state' with payload: b'{"high_voltage_battery_preconditioning_status":"ACTIVE","high_voltage_battery_preconditioning_status_message":"na"}' The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
You will first need to stop the docker container and delete the MQTT topics from the MQTT broker for the following sensors as well as delete the following sensors from Home Assistant before starting the docker container back up again:
These are different issues from a Hummer, so we will have to work on these later: Exception raised while updating state of sensor.2022_gmc_hummer_ev_high_voltage_battery_preconditioning_status, topic: 'homeassistant/sensor/VIN/high_voltage_battery_preconditioning_status/state' with payload: b'{"high_voltage_battery_preconditioning_status":"ACTIVE","high_voltage_battery_preconditioning_status_message":"na"}' |
|
I used mqtt explorer to delete the entities and developer tools purge entities. They were recreated. This is the new error: Logger: homeassistant.components.mqtt.models Exception raised while updating state of sensor.2020_cadillac_ct6_awd_super_cruise_fuel_amount, topic: 'homeassistant/VIN/available' with payload: b'true' During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
@almoney, I made some additional changes. Could you please go through the same cleanup process from above and try again with the "latest" image? Thanks. |
|
After the latest update I see this in the dashboard: Exception raised while updating state of sensor.2022_cadillac_escalade_esv_diesel_super_cruise_exhst_part_fltr_warn_2_on, topic: 'homeassistant/VIN/available' with payload: b'true' During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
@almoney, a couple of things.
If you had correctly deleted the respective sensors, I would not expect you to see this error again:
|
|
I will take another look tomorrow. I am not with the Diesel right now. |
|
This is what I see in MQTT Explorer: This is the dashboard:
Interested to learn the process. Is the data typed somewhere that we need to update? |
|
@almoney, could you please do the cleanup again and see if it works now using the "latest" image that I just published? I'm hoping it should finally work now. 🤞 |
|
@almoney, did the latest update work? |
Sorry Ihave not been able to run the Escalade yet. Will report on Thursday. |
|
This is the debug log: 2024-09-09T20:47:35.821281571Z debug: Diagnostic request response: {"stats":["DIESEL WARNING:\n EXHST FL LEVL WARN IND: 1LVL\n EXHST FL LEVL WARN STATUS: GreenNA\n EXHST PART FLTR WARN ON: FALSENA\n EXHST PART FLTR WARN2 ON: FALSENA\n","ENGINE AIR FILTER MONITOR STATUS:\n ENGINE AIR FILTER MONITOR STATUS: 50.0%\n","ENGINE COOLANT TEMP:\n ENGINE COOLANT TEMP: 39.00°C\n ENGINE COOLANT TEMP F: 102°F\n","ENGINE RPM:\n ENGINE RPM: 900.000RPM\n","FUEL TANK INFO:\n FUEL AMOUNT: 105.88L\n FUEL CAPACITY: 105.88L\n FUEL LEVEL: 100.0%\n FUEL LEVEL IN GAL: 105.88L\n FUEL AMOUNT GAL: 28gal\n FUEL CAPACITY GAL: 28gal\n FUEL LEVEL IN GAL GAL: 28gal\n","HOTSPOT CONFIG:\n","HOTSPOT STATUS:\n","LIFETIME FUEL ECON:\n LIFETIME FUEL ECON: 10.99km/L\n LIFETIME FUEL ECON MPG: 25.9mpg\n","LIFETIME FUEL USED:\n LIFETIME FUEL USED: 4739.92L\n LIFETIME FUEL USED GAL: 1252.2gal\n","ODOMETER:\n ODOMETER: 52056.64km\n ODOMETER MI: 32346.5mi\n","OIL LIFE:\n OIL LIFE: 17.2%\n","TIRE PRESSURE:\n TIRE PRESSURE LF: 236.0kPa\n TIRE PRESSURE LR: 252.0kPa\n TIRE PRESSURE PLACARD FRONT: 250.0kPa\n TIRE PRESSURE PLACARD REAR: 250.0kPa\n TIRE PRESSURE RF: 256.0kPa\n TIRE PRESSURE RR: 244.0kPa\n TIRE PRESSURE LF PSI: 34.2psi\n TIRE PRESSURE LR PSI: 36.5psi\n TIRE PRESSURE PLACARD FRONT PSI: 36.3psi\n TIRE PRESSURE PLACARD REAR PSI: 36.3psi\n TIRE PRESSURE RF PSI: 37.1psi\n TIRE PRESSURE RR PSI: 35.4psi\n","VEHICLE RANGE:\n GAS RANGE: 1128.17km\n GAS RANGE MI: 701mi\n"],"timestamp":"2024-09-09 20:47:35"} The sensor still has Unknown as the status for the Exhst Fl Levl Warn Status. I think is should show GREEN. Logger: homeassistant.components.mqtt.models Exception raised while updating state of sensor.2022_gmc_hummer_ev_high_voltage_battery_preconditioning_status, topic: 'homeassistant/sensor/VIN1/high_voltage_battery_preconditioning_status/state' with payload: b'{"high_voltage_battery_preconditioning_status":"DISABLED","high_voltage_battery_preconditioning_status_message":"na"}' During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
Sorry about the delay on this. Unfortunately, if we don't get past the latest key issue which we discovered yesterday, then all of this becomes moot, so I'm going to pause on this until we have a solution to the key issue. |
Where is the issue documented? |
|
I have a Diesel Escalade in use and it generates this exception. Is there a dictionary that shows this sensor is a text string I can update? (I have 4 vehicles that are working well with the 2 in Home Assistant and 2 more in Docker Containers.
Logger: homeassistant.components.mqtt.models
Source: components/mqtt/models.py:383
integration: MQTT (documentation, issues)
First occurred: August 11, 2024 at 6:38:13 AM (81 occurrences)
Last logged: 6:38:26 AM
Exception raised while updating state of sensor.2022_cadillac_escalade_esv_diesel_super_cruise_exhst_part_fltr_warn_on, topic: 'homeassistant/VIN/available' with payload: b'true'
Exception raised while updating state of sensor.2022_cadillac_escalade_esv_diesel_super_cruise_exhst_part_fltr_warn_2_on, topic: 'homeassistant/VIN/available' with payload: b'true'
Exception raised while updating state of sensor.2020_cadillac_ct6_awd_super_cruise_fuel_amount, topic: 'homeassistant/VIN/available' with payload: b'true'
Exception raised while updating state of sensor.2020_cadillac_ct6_awd_super_cruise_fuel_capacity, topic: 'homeassistant/VIN/available' with payload: b'true'
Exception raised while updating state of sensor.2020_cadillac_ct6_awd_super_cruise_fuel_level_in_gal, topic: 'homeassistant/VIN/available' with payload: b'true'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 653, in state
numerical_value = float(value) # type:ignore[arg-type]
^^^^^^^^^^^^
ValueError: could not convert string to float: 'Green'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 383, in process_write_state_requests
entity.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1007, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1133, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1068, in __async_calculate_state
state = self._stringify_state(available)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1013, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 655, in state
raise ValueError(
ValueError: Sensor sensor.2022_cadillac_escalade_esv_diesel_super_cruise_exhst_fl_levl_warn_status has device class 'None', state class 'measurement' unit 'NA' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'Green' (<class 'str'>)
The text was updated successfully, but these errors were encountered: