My question now is i noticed that when the asset location is updated it’s only updated and rendered on the Mini map widget on the asset page, so how can it also be rendered on the Main map page.
I did add the show on dashboard configuration item to the asset location attribute but it’s only update the asset location on the small map widget only not on the main map page
I have just pushed a fix relating to showOnDashboard which establishes the correct behaviour so Assets will show on the main map if there is no showOnDashboard configuration item or if showOnDashboard=true. So by default an Asset will show on the map to hide it you add showOnDashboard=false.
Just to avoid any confusion can you confirm exactly what your issue is:
Asset not showing at all on the Map page
or
Asset shows on the Map page but its’ position does not update automatically when the location attribute value is changed
If it is 1 then please try the latest ‘manager’ image from docker hub (with timestamp greater than this message) and you should not need to add showOnDashboard configuration item.
I added both Access public write and Show on dashboard configuration items for Location attribute
I created a 3rd party application - for testing - that send route’s waypoints coordinates every 2 seconds to the asset using HTTP Asset API to update its location attribute.
What i noticed that it successfully updating the asset location attribute and its marker updated also on the Mini Map widget (from the asset details page), when i switched back to the Main Map (Dashboard Page) also the marker moved to the updated location ONCE only- not updated with all other waypoints like in the Mini Map Asset Widget.
My question here:
How i can let the Main Map (Dashboard) updating the displayed marker location continuously for each update without going back and forth between the asset details and the main map?
Kindly find below images :
Updating asset location on the mini map (continuously updated)
Updating asset location on the Main map (updated Once only)
I have just pushed an update to the Manager UI that fixes this issue, please try the latest manager image in docker hub (timestamp greater than this post).