sorry i dont understand what you are asking to look for
do i need to look at the read me or the js?
in the readme i see you still use
hagraph_path: http://path_to_your_home_assistance_instance:8123 # will change name to base_url or similar
hagraph_token: YOUR_LONG_LIVED_ACCESS_TOKEN # Can be created through the Home Assistant front end.
instead off ha_url and ha_token
in the examples i see you use hagraph (and not graph)
and the needed options are not in the example (url and token)
i also see that you say: example dashboards for …
that should be example widget definitions
i see your description to add other DBs. nice.
i think we will have to add an url to your readme after we have it in AD, because what you got in the readme is to extensive for the docs from AD at this point.
we would need a description in this style when it is implemented:
A widget to monitor and activate a lock
Note that unlike HASS, Dashboard regards an unlocked lock as active. By contrast, the HASS UI shows a locked lock as “on”. Since the purpose of the dashboard is to alert at a glance on anything that is unusual, I chose to make the unlocked state “active” which means in the default skin it is shown as red, wheras a locked icon is shown as gray. You can easily change this behavior by setting active and inactive styles if you prefer.
entity - the entity_id of the lock
title - the title displayed on the tile
title2 - a second line of title text