Magnus Nyström

Hi @adlpharm I'm guessing you are not running the container on the host network? The flow validator you got caught by is trying to avoid setting up devices that can't...

Hi @markfrancisonly Hmm maybe changing default network in home-assistant?  Else editing the "look up" command and specify the interface. I only have one network in my household, can't really...

Hi @kuduacz Thanks for trying the pre-release! For now only the consider home time can be configured once the entity is set up. You do that in the Configuration ->...

Ah, sorry. I messed up when first releasing and have since adjusted the code under the same version. Was hoping no one had downloaded yet. Please redownload the integration in...

Strange, should work after restart of HASS. At this time I would recommend reverting back to 1.4.0 as basically no logging is done. I have this running on both HASSOS...

See my silly mistake.. I have more device_tracker platforms in my configuration.yaml so didn't catch it before. For you the code was trying to access stuff that wasn't there so...

Thanks for reporting @gieljnssns Just pre-released 2.0.2 that hopefully solves it. Sidenote, I realize imported entities gets suffixed (like device_tracker.phone_2) on import from configuration.yaml Meaning one still has to update...

> @mudape Thanks a lot. This version(2.0.2 and 2.0.3) works as expected. I updated, restarted, removed old entities from known files, removed yaml config, restarted, rename all entities(remove _2) Thanks...

Hi @ildar170975 Config flow for this integration came with its beta release, not HA. You can downgrade to 1.4 again or continue with what you have now. I agree configuration.yaml...

Hi @lhlxx2010 device_tracker don't have a Device [https://github.com/home-assistant/core/pull/63328](url) So, as you've shown the state is needed to act as trigger in automations. You can use a template with _trigger.to_state.state ==...