Comments (6)
Maybe worth doing a real-world risk analysis - my needle's banging pretty low here ... = not worth the effort in my opinion. I'd rather go for simplicity and put more effort into functionality. 🤷🏼♂️
from alexa-fhem-docker.
I think this dedicated container doesn't work well anymore when using the latest and greatest FHEM alexa module because the new module is no longer designed to really work with dedicated instances (even though the maintainer says it should, but also states it's not tested as far as I remember).
I personally had used alexa as part of the actual FHEM container which works pretty will. In fact, there is no real reason or benefit anymore to keep alexa-fhem in a dedicated container (besides your ego, of course ;-)).
from alexa-fhem-docker.
Oh, i choosed the dedicated container, because it belongs to another security boundary in my opinion.
from alexa-fhem-docker.
sex what?!? :D
Anyway, as I was saying, there is no gain in security if you do not plan to use custom skills but simply the FHEM Home Automation skills. Connectivity is outbound only.
from alexa-fhem-docker.
I understand your point of view.
My understanding crrently is, that the echo device is sending speech to aws. AWS will hand over to the fhem e.V. server. The fhem e.V. server gives that information to the alexa-fhem node js deamon.
After all i know, the alexa-fhem deamon seems to get it commands from the Fhem e.V. server. So the alexa-fhem and Fhem e.V. server should not have access to my Server or container which runs FHEM, because this system hast access to serval internal systems.
I`ll try to get this working.
from alexa-fhem-docker.
Just to celarify some things.
The container works pretty good. It can communicate with fhem on the host or any other location.
There is only one thing which is critical during setup. Before starting the container, the connection to fhem needs to be configured properly so that it can connect to the alexa fhem device and configure anything.
I need to do a "reset" command to get this working, because at my first start the communication to fhem was not possible.
from alexa-fhem-docker.
Related Issues (9)
- Option for an environment variable to listen on different ip HOT 1
- Tag is specified with v as for version, but it has no version
- Bullseye als baseimage HOT 5
- sshautoconf error during container startup (home dir. permission error) HOT 3
- User/password fhem webgui HOT 3
- permissions on main working directory isn't enforced
- Dependency Dashboard
- add depends_on to docker-compose.yml example HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from alexa-fhem-docker.