First of all, thank you for your work on this integration!
The newer versions of HA alerts and makes component updates easy via a built-in feature on the Settings page's menu.
However if I update Mikrotik_Router this way, it will get into some trouble, and every component got re-added.
I have a custom (handcrafted) page for the router, and it drives me mad to manually change the graph's / menus entities randomly :)
For example:
type: entities
title: Firewall
entities:
entity: switch.mikrotik_router_nat_5
entity: switch.mikrotik_router_nat_6
entity: switch.mikrotik_router_nat_7
entity: switch.mikrotik_router_nat_8
becomes
entity: switch.mikrotik_router_nat_10
entity: switch.mikrotik_router_nat_11
entity: switch.mikrotik_router_nat_12
in the 'old' ways of working it was not an INT value, but was named accordingly ex.: switch.mikrotik_router_nat_tpc_raspi_rdp
and for the graphs, sensor names fluctuate between the proper and a secondary:
yup, I'm aware of that. it has to do with how new HA methods handle devices.
I have a solution already on other integration I'm currently working on and it will be migrated here too.
First of all, thank you for your work on this integration!
The newer versions of HA alerts and makes component updates easy via a built-in feature on the Settings page's menu. However if I update Mikrotik_Router this way, it will get into some trouble, and every component got re-added.
I have a custom (handcrafted) page for the router, and it drives me mad to manually change the graph's / menus entities randomly :)
For example:
becomes
in the 'old' ways of working it was not an INT value, but was named accordingly ex.: switch.mikrotik_router_nat_tpc_raspi_rdp
and for the graphs, sensor names fluctuate between the proper and a secondary:
sensor.mikrotik_router_pppoe_out1_rx becomes randomly sensor.mikrotik_router_pppoe_out1_rx_2
I have 10 graphs with 20 items, Total ~40 entities on this page, and randomly it becomes a NaN/NaN / entity not found mess :(
What is the proper way of updating this component?
Software versions
Diagnostics data
In the Integration's diagnostics page, the component has 0.0.0 as a version: