502: bad gateway

[browiw]

I wa setting up a custom integration via the web ui for national grid. When i had done this I got the message 502: bad gateway. Tried the try again but still the same result, Can anyone suggest what the problem may be and how to solve it please.

latest-1.txt

[gcoan]

I don't see anything 502 errors in your logfile but I do see lots of other errors that you need to address:

1. You are getting errors from givtcp about it using deprecated object id. This is fixed by upgrading to the latest givtcp version

2. There are also givtcp errors about duplicated battery sensor names being rejected. It looks like you've upgraded from givtcp v2 to v3 and the upgrade didn't work properly. I had this and it means that a number of your battery sensors are not being populated. You need to stop givtcp, then with mqtt explorer delete all entries with 'battery' in the name. Then do a full shutdown and restart of HA and all the addons

3. There are a lot of warnings about recorder entries being too large from predbat. Details of how to suppress these are in the predbat faq's

4. There is from the national grid carbon intensity component which is I guess what you are referring to. This is a question for that integration not predbat, but I think others have reported that it's broken. Instead you can use the carbon intensity feature direct from predbat and remove this integration

[browiw]

I Believe I am on the latest version which is 3.5.

Would you think it a good idea to click the rebuild option on predbat to solve the problem and or remove the national grid component

[browiw]

Disabling the national gid integration seems to have been the problem as disabled it and the web ui is nw available. Thank you.

[gcoan]

I Believe I am on the latest version which is 3.5.

Would you think it a good idea to click the rebuild option on predbat to solve the problem and or remove the national grid component

rebuilding predbat wouldn't have done anything as the error is not in predbat, its in the national grid integration. As you've found, disabling it will cure the issue its reporting

you have some legacy battery entities sticking around in Home Assistant that is causing the givtcp/mqtt errors you see in the log. Its certainly causing the duplicate errors and maybe is causing the object_id errors as well:

2025-12-27 17:38:19.793 WARNING (MainThread) [homeassistant.components.mqtt.entity] The configuration for entity sensor.givtcp_dz2317g448_battery_cell_3_temperature uses the deprecated option `object_id` to set the default entity id. Replace the `"object_id": "GivTCP_DZ2317G448_Battery_Cell_3_Temperature"` option with `"default_entity_id": "sensor.GivTCP_DZ2317G448_Battery_Cell_3_Temperature"` in your published discovery configuration to fix this issue, or contact the maintainer of the integration that published this config to fix this. This will stop working in Home Assistant Core 2026.4
2025-12-27 17:38:19.795 WARNING (MainThread) [homeassistant.components.mqtt.entity] The configuration for entity sensor.givtcp_dz2317g448_battery_cell_4_temperature uses the deprecated option `object_id` to set the default entity id. Replace the `"object_id": "GivTCP_DZ2317G448_Battery_Cell_4_Temperature"` option with `"default_entity_id": "sensor.GivTCP_DZ2317G448_Battery_Cell_4_Temperature"` in your published discovery configuration to fix this issue, or contact the maintainer of the integration that published this config to fix this. This will stop working in Home Assistant Core 2026.4
2025-12-27 17:38:19.804 ERROR (MainThread) [homeassistant.components.sensor] Platform mqtt does not generate unique IDs. ID GivTCP_DZ2317G448_Battery_Capacity is already used by sensor.givtcp_dz2317g448_battery_capacity - ignoring sensor.givtcp_dz2317g448_battery_capacity_2
2025-12-27 17:38:19.805 ERROR (MainThread) [homeassistant.components.sensor] Platform mqtt does not generate unique IDs. ID GivTCP_DZ2317G448_Battery_Cell_10_Voltage is already used by sensor.givtcp_dz2317g448_battery_cell_10_voltage - ignoring sensor.givtcp_dz2317g448_battery_cell_10_voltage_2
2025-12-27 17:38:19.807 ERROR (MainThread) [homeassistant.components.sensor] Platform mqtt does not generate unique IDs. ID GivTCP_DZ2317G448_Battery_Cell_11_Voltage is already used by sensor.givtcp_dz2317g448_battery_cell_11_voltage - ignoring sensor.givtcp_dz2317g448_battery_cell_11_voltage_2 

As I mentioned these need to be deleted with the mqtt explorer addon.

[browiw]

Will get them deleted, thank you once again for the invaluable help.

…

On Sun, 28 Dec 2025, 12:39 Geoffrey Coan, ***@***.***> wrote: *gcoan* left a comment (springfall2008/batpred#3133) <#3133 (comment)> I Believe I am on the latest version which is 3.5. Would you think it a good idea to click the rebuild option on predbat to solve the problem and or remove the national grid component rebuilding predbat wouldn't have done anything as the error is not in predbat, its in the national grid integration. As you've found, disabling it will cure the issue its reporting you have some legacy battery entities sticking around in Home Assistant that is causing the givtcp/mqtt errors you see in the log. Its certainly causing the duplicate errors and maybe is causing the object_id errors as well: 2025-12-27 17:38:19.793 WARNING (MainThread) [homeassistant.components.mqtt.entity] The configuration for entity sensor.givtcp_dz2317g448_battery_cell_3_temperature uses the deprecated option `object_id` to set the default entity id. Replace the `"object_id": "GivTCP_DZ2317G448_Battery_Cell_3_Temperature"` option with `"default_entity_id": "sensor.GivTCP_DZ2317G448_Battery_Cell_3_Temperature"` in your published discovery configuration to fix this issue, or contact the maintainer of the integration that published this config to fix this. This will stop working in Home Assistant Core 2026.4 2025-12-27 17:38:19.795 WARNING (MainThread) [homeassistant.components.mqtt.entity] The configuration for entity sensor.givtcp_dz2317g448_battery_cell_4_temperature uses the deprecated option `object_id` to set the default entity id. Replace the `"object_id": "GivTCP_DZ2317G448_Battery_Cell_4_Temperature"` option with `"default_entity_id": "sensor.GivTCP_DZ2317G448_Battery_Cell_4_Temperature"` in your published discovery configuration to fix this issue, or contact the maintainer of the integration that published this config to fix this. This will stop working in Home Assistant Core 2026.4 2025-12-27 17:38:19.804 ERROR (MainThread) [homeassistant.components.sensor] Platform mqtt does not generate unique IDs. ID GivTCP_DZ2317G448_Battery_Capacity is already used by sensor.givtcp_dz2317g448_battery_capacity - ignoring sensor.givtcp_dz2317g448_battery_capacity_2 2025-12-27 17:38:19.805 ERROR (MainThread) [homeassistant.components.sensor] Platform mqtt does not generate unique IDs. ID GivTCP_DZ2317G448_Battery_Cell_10_Voltage is already used by sensor.givtcp_dz2317g448_battery_cell_10_voltage - ignoring sensor.givtcp_dz2317g448_battery_cell_10_voltage_2 2025-12-27 17:38:19.807 ERROR (MainThread) [homeassistant.components.sensor] Platform mqtt does not generate unique IDs. ID GivTCP_DZ2317G448_Battery_Cell_11_Voltage is already used by sensor.givtcp_dz2317g448_battery_cell_11_voltage - ignoring sensor.givtcp_dz2317g448_battery_cell_11_voltage_2 As I mentioned these need to be deleted with the mqtt explorer addon. — Reply to this email directly, view it on GitHub <#3133 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAFMJAQ3OWYTIN6OGNSELOT4D7FQNAVCNFSM6AAAAACQFBYD6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOJUG4YTMNZZGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>