Note that in the `sys.path`variable the path is given as absolute path (I only
wrote it relative to `~` in the in my post, but in the script the absolute path
is used everywhere). See line 2:
```
['/home/pyuser/.homeassistant',
'/home/pyuser/.homeassistant/deps/lib/python3.7/site-packag
On Mon, Jul 30, 2018 at 3:15 PM, dieter wrote:
> stefand...@gmail.com writes:
>> ...
>> The "story" is: In homeassistant (short HA) some modules are installed at
>> runtime during first start ("bootstrapping"), and for some reason loading
>> the modules fails directly after installing the module
stefand...@gmail.com writes:
> ...
> The "story" is: In homeassistant (short HA) some modules are installed at
> runtime during first start ("bootstrapping"), and for some reason loading the
> modules fails directly after installing the modules. Subsequent starts work
> fine.
>
> The modules tha
Am Sonntag, 29. Juli 2018 01:32:07 UTC+2 schrieb MRAB:
That was also my first suspicion, but I checked that the path exists by
printing the directory contents out, right before the ìmport ` statement.
The "please check your config" message are a result of another package
(aiohttp_cors) that is a
On 2018-07-28 22:16, stefand...@gmail.com wrote:
Hi everyone,
I am currently investigating an interesting bug in homeassistant which is a bit
hard to reproduce. I already dug so deep that I ask here, because I think the
root cause has to do with how Python locates and loads modules/packages.
T
Hi everyone,
I am currently investigating an interesting bug in homeassistant which is a bit
hard to reproduce. I already dug so deep that I ask here, because I think the
root cause has to do with how Python locates and loads modules/packages.
The "story" is: In homeassistant (short HA) some mod
