Trevor
Trevor
There's also still the case of moving the controller from a different platform where the devices are already paired but don't have names. In that case, they'll all just show...
I actually tried that but it's the same result: ``` class ChangeParentGame extends FlameGame { bool shouldChange = false; final childComponent = Component(); final parentComponent = Component(); @override Future? onLoad()...
FWIW, the same code using the flag doesn't crash with flame 1.0.0 but does with 1.1.0+.
It seems to only be an issue when the child component was previously a sibling of the new parent or a sibling of an ancestor of the new parent. This...
I would vote for just excluding them by default. To me, auto-entities is essentially part of a DIY auto generated dashboard (just in card form) and I imagine the whole...
Can't you already do this with the [filter](http://www.mitchellbosecke.com/pebble/documentation/tag/filter) tag?
A potential workaround for this would be to use the [default](http://www.mitchellbosecke.com/pebble/documentation/filter/default) filter: ``` {% if car | default is not null %} ```
I looked into this a bit and while the data can all be obtained without HTML parsing, I can't find a way to actually log in without parsing the csrf...
I'm having issues with this as well. I tried pulling all the latest changes but it still never finds any Chromecasts without net=host. However, I have other things running on...
It would be nice if the port was configurable when creating the container, e.g. via an environment variable, so that it can work without going in and making manual modifications.