Sevket Gökay
Sevket Gökay
i think i found the issue. the sql query of the current `ocpp_tag_activity` view is: ``` SELECT ocpp_tag.*, COALESCE(tx_activity.active_transaction_count, 0) as 'active_transaction_count', CASE WHEN (active_transaction_count > 0) THEN TRUE ELSE...
> the query from @kibeki with the new ocpp_tag_activity view was slower than the original (V0_9_9_update.sql) can you quantify this? i shared the code that you can use to benchmark.
@NikSays thanks for your investigation, discovery and bringing this topic back to my attention. i have created the PR for the previous improvement and will integrate your suggestion as well.
@NikSays i think there is an issue with your updated transaction: as a consequence of the change, you start applying `GROUP BY tx2.transaction_pk, tx2.event_timestamp;` on the joined/global table which does...
the group-by has unwanted side effects when taken one level higher (to the joined/global table) because it starts to act as a filter on the right side of the LEFT...
> Problem: when connected more than 100 chargers 4-5 chargers randomly always go offline there is no limit we set in code/config. you can have as many charging stations as...
closing due to inactivity.
this issue mixes two topics: 1. wrong usage/reporting of ocpp id tag by the station. as a consequence, steve does the right thing marks it as invalid. nothing to do...
superseded by https://github.com/steve-community/steve/pull/1611
i consider this issue resolved, and am closing it.