notify_devices repeating

[s0129]

Describe the bug
Previously when I enabled notify_devices I received a notification whenever the status changed, however recently I am receiving multiple duplicate notifications.

Expected behaviour
Only get a notification when the status changes.

Predbat version
v8.29.13

Log file
Will upload asap when have access.

[gcoan]

It sounds like a config issue as no-one else has reported this. Can you check your notify switch settings?

https://springfall2008.github.io/batpred/customisation/#inverter-control-options

should have set status notify on and inverter notify off.

If set correct please supply logfile and debug file

[s0129]

I think my config looks ok.

Have added log and debug files.

predbat_log.log
predbat_debug.yaml

[gcoan]

yes those settings should be fine

Predbat used to do this ages ago, send a notification every time it ran, but that was changed well over a year ago, so strange that it is reoccurring for you

[s0129]

I wondered if my setup was broken somehow as have been seeing some strange things recently. Some other odd behaviour in this issue #2658

[s0129]

Think I have worked out the problem. Looks like I have some errors in my config which are generating warnings and hitting the record_status function. For some reason these don't always end up updating the status entity but still trigger a notify call. I don't get a notification containing the warn message.

e.g. snippets from my log file.

2025-12-15 20:43:02.889484: Info: record_status Demand
...
2025-12-15 20:42:44.207307: Warn: record_status Warn: can not resolve watch_list value {car_charging_now}
...
2025-12-15 20:42:17.884618: Info: record_status Demand

[gcoan]

Good that you have found the problem

The notifications don't contain the warning status, only the predbat mode it is setting (charge/demand/export etc).
Interesting that it repeats the notification when this happens.
What does the predbat status show, it should show the warning?

[s0129]

Looking at the entity history, the predbat status is set to the warning for about 30 seconds before being set to the mode e.g. demand or export etc.

[gcoan]

thanks, so that in itself is a bug, if there's a warning set then the status should retain it until the next run.

Can you paste your apps.yaml file in so I can see the config error you had (and hopefully recreate it), and a screenshot of predbat.status

thanks

[s0129]

I have fixed my config now, but the error came from having an item in the watch list that wasn't defined.
e.g.

watch_list:
    - '{octopus_intelligent_slot}'
    - '{octopus_ready_time}'
    - '{octopus_charge_limit}'
    - '{octopus_saving_session}'
    - '+[car_charging_soc]'
    - '+[car_charging_planned]'
    - '{car_charging_now}'

When car_charging_now was commented out in the config.

Here is the predbat.status.

[gcoan]

thanks