docker-jitsi-meet VS esphome

Jitsi Meet for selfhosted Video Meetings

With this version I am facing the same issue as describef by you. This version is broken: https://github.com/jitsi/docker-jitsi-meet/issues/1377

Most video conferencing suites allow starting a call with video disabled so they don't block you from using only audio all the time. Most video suites will also provide either a docker container or suite of containers via docker-compose to get you started quickly. Personally, I host Jitsi using https://github.com/jitsi/docker-jitsi-meet. If you want to try before you host then you can use https://meet.jit.si/ which is the free/public Jitsi instance. They don't require accounts to try. When you host it yourself, there's even an end-to-end encryption option you can enable.

proxy_http_version 1.1 may not be necessary. I copied it from the nginx configuration files included in the official jitsi docker images. I think they are making sure that no HTTP 1.0 requests are made because websockets aren't supported on 1.0. It would be rare for a device to use 1.0 these days, though.

If you need to configure options that are not supported through the ".env" file then, first, be sure to open an issue because the Jitsi maintainers intend for ".env" to manage all the configurations. From there, you can inject only your configuration overrides for the config.json by mounting it in your container as "/config/custom-config.json". This would look like a ' - "/path/to/my/config.json:/config/custom-config.json' entry in the "volumes" section of your docker compose. See https://github.com/jitsi/docker-jitsi-meet/issues/768 for a discussion on this.

https://github.com/jitsi/docker-jitsi-meet/blob/master/docker-compose.yml <-- this is the docker-compose.yml in the official repository, did you tried it?

download the latest release from https://github.com/jitsi/docker-jitsi-meet/releases (at time of writing stable-6173: release)

+1 Jitsi, but host it yourself! This is the Docker install that let's you customize the experience. Browser or app based, platform-agnostic, fully encrypted back to your container, with the option to register a SIP endpoint for people to be able to dial into the conference via your IP PBX and do audio-only conferencing. Jitsi does ALMOST everything that Teams / Zoom can do but for regular conferences with screen sharing, it's hard to beat. I built a web scheduler that initializes meetings via JWT so no inadvertent meetings can start without the organizer, solving one of the drawbacks.

Jitsi is pretty secure and private with using meet.jit.si their server. Also it supports all the devices Android IOS PC and Mac. For your small group I would give it a shot and see what you think. As for server, yes it can be done - https://www.osradar.com/deploy-jitsi-meet-server-with-docker/ or https://github.com/jitsi/docker-jitsi-meet I had issues with Android getting connected so we just use meet.jit.si and it all works fine with 3 people.

For the ESP32, an hero is in the process of adding LVGL to ESPHome. You can try it out now: https://github.com/esphome/esphome/pull/6363

Here's the (very good!) preview documentation: https://deploy-preview-3678--esphome.netlify.app/components/...

This is such a game-changer for me that I'll be using the ESP32 over the ESP8266 for any projects involving displays from now on.

Solid state relay is probably a bad idea with all the extra heat-sinking, extra cost, and chance of getting counterfeits.

I do this with ESPHome & a J115F21C12VDCS.9 relay (note only the NO side is rated for 40A resistive): https://i.imgur.com/MqqOkoY.png

Choose any of the temperature sensors here for air temperature sensing: https://esphome.io/

Configuration is so easy. For the sensor, just copy the config from here, for example: https://esphome.io/components/sensor/bme280. Add a gpio output (https://esphome.io/components/output/gpio) and a bang-bang climate controller (https://esphome.io/components/climate/bang_bang.html)

You might want to take a look at https://esphome.io/ for an easy integration of an ESP32/8266 into home Assistant.

You can do this with a $30 Sonoff S31 running ESPHome [0]. Since the Sonoff wall switch can run a ping sensor against your server you could create a watchdog automation right on the S31 to shut off the mains power to the S31 switch and turn back on after X seconds.

There are other ways you could have the S31 do operational checks but ultimately ESPHome is probably an interesting consideration and supported by tons of off the shelf hardware.

[0] https://esphome.io/

They're pretty great and compatible with most things. ESPHome [1] is a great resource for getting ESP32's working nicely with HA and you can find lots of projects using it to learn from.

You'll likely need to do soldering if you want to connect sensors, batteries and the like.

Personally I really like what SEEED Studio [2] does with their ESP32 boards and they have nice docs.

1. https://esphome.io/

Maybe you could set up ESPHome on the ESP32. It might make connecting those components easier, plus a decent web server built in. Then your app can be set up to access data provided by the ESPHome web server.

# # Setting pins for sda and scl will be required until https://github.com/esphome/esphome/pull/2970 is released

Probably an unpopular opinion, but for the simple stuff you may just want to use something like EspHome where you just need to create a yaml file. Once you’re comfortable with that maybe get into something a bit more advanced, but esphome make it a breeze. It integrates with home assistant if you already have that in place as well.

ESPHome