This is probably the most complete all in one presence sensor for Home Assistant, that integrates a SEN0395 from DFROBOT, a BME680 for the temperature, humidity, air pressure as well as air quality, a BH1750 as an ambient light sensor for automations, and a WS2812 LED that changes colour depends on the air quality level.

You can use the SEN0395 mmwave to detect presence as well as motion, and along with the BH1750, create automations in Home Assistant that will turn on and off the lights depending the ambient light. Get an accurate temperature and humidity temperature, and use a WS2812 to change colour depending on the AQI reading from the BME680.

Bellow are few cases that you can print.
Allot of effort and time went in making this sensor, printing the cases, and making the video, so if you like it, please share it, like and subscribe.

https://www.thingiverse.com/thing:5446184

In depth comparison of the 3 mostly used mmwave sensors for Home Assistant. The SEN0395 from DFROBOT, the LD1115H from Hi-link and the LD2410B as well from Hi-link.

All 3 sensors are 24GHz millimetre-wave radar sensor. All 3 uses a GPIO pin as a sensor as well as UART to interact with the board.
The SEN0395 and the LD2410B support distance detection as well as sensibility, the LD2410B has also Bluetooth so that can be also adjusted and controlled via a mobile app.

The LD1115H on the other hand only support changing the sensibility.


The SEN0395 from DFROBOT, this sensor senses the human presence, stationery, and moving people within the detection range of maximum 9m. This 24GHz millimetre-wave radar sensor that has separate transmitter and receiver antennas.
It has a transmit power range between 13 to 15 decibel-milliwatts, its 28 cm by 24 cm, operating temperature range for this sensor is -40 degrees Celsius up to 85 degrees Celsius, the default UART baud rate is 9600 and it has 6 pins.
To connect this, you can simply use the V, G and IO2, but if you also want to interact with the sensor and change the values also for debugging purposes, you will also need to connect the TX and TX pins.

The LD1115H it’s a high sensitivity 24GHz mmwave sensor that can detect movement to up to 4 m and up to 16 m movement, This sensor its about 2.5mm x 2.5mm in size, the default UART baud_rate is 115200, data_bits: 8, stop_bits: 1, parity: NONE and has 5 pins
When the radar detects a large motion, it will output mov,a small number that represents the spectral line and the another number that represents the signal strength. If the value changes from mov to occ, then it detects a static object, the rest of the values are the same as the movement.

The LD2410B is a high-sensitivity 24GHz human presence radar with a distance detection of up to 6 meters when the detection resolution is 0.75 or uo do 1.6 meters when the detection resolution is 0.2. Its 7mmx35mm the pin hole diameter is 0.6mm, and the pin spacing is 1.27mm so smaller than the normal, so I recommend buying the version without the header. It has 5 pins as well VCC 5V, Ground, RX, TX and OUT. The out pin is low when there is no presence detected and hight when there is presence.
The power supply voltage of the module is 5V, and the power supply capacity of the power supply is required to be greater than 200mA.

In this video I´ll show you how you can easily create a much better alarm system for home assistant than the built in one. It´s easy to install and easy to set up, no codding need it, no automations need it, all its done from an easy to use interface.

In this video I’ll show you how to create a 3D floorplan Picture Elements in Home Assistant. We’ll use the Sweet Home 3D to create the layout and the floorplan, GIMP to edit the pictures and create the layers and to finish elements card in home assistant to add some icons to the image and how to interact with different switches, lights, sensors.

http://www.sweethome3d.com/
https://www.gimp.org/

Fix Tuya Switch Not Keeping Its State When Toggled by manually controlling them without flashing tasmota firmware.

This custom component is a modified copy of the original tuya component built into the home assistant with some modifications to the library used to communicate with Tuya Cloud. Because it still uses the tuya cloud, there is no need to get the local key, device id or ip address, and the integration and use is as easy as installing the original tuya integration.

This is a very simple solution and its been working great for me for the past few weeks.
First go to the page bellow and download the package zip. Extract and copy just the tuya_custom folder from the archive to your Home Assistant custom_components folder.

The custom_components is located at the same path as your configuration.yaml, if you don’t have this folder, simply create it and copy inside the tuya_custom folder you just downloaded.

https://github.com/ollo69/ha_tuya_custom

Now all you have to do is restart the server, after the server has restarted, go to Configuration then Integrations click on the + sign on the lower right to add another integration and search for tuya, you will find a tuya custom integration click on it, and add your account email or phone number, password, country code and select what app you use Tuya, Smart Life or Jinvoo and click submit.

If all the details are correct them a new integration will appear and all the devices will appear under the entities. Now if you have configured as well the official tyua integration then the devices from the custom tuya will have the same name followed by a _2 say if you have a switch.4816744334se3 then the custom tuya will be switch.4816744334se3_2

Configure them in the dashboard and …. That’s it.

Fix Tuya Switch Not Keeping Its State When Toggled by manually controlling them without flashing tasmota firmware.

In order to control the Tuya/Smartlife plugs locally without flashing the firmware, we need to get the device_id, local_key and ip address of each plug or switch on the network. To get the ip address, install any app like WHO'S ON MY WIFI or similar, and you will get a list of devices connected, the Tuya devices will either identify with the name set on the Tuya app or more likely with the device_id.
Now to get the device_id and the local_key, you either need a phone o tablet with root access or we can install an emulator on windows.
1. So, lets start by installing ldplayer. Download and install the emulator:

https://www.ldplayer.net/blog/download-64-bit-android-emulator-for-64bit-required-games.html

2. Download the es-file-explorer-file-manager.

https://www.apkmirror.com/apk/es-global/es-file-explorer/es-file-explorer-4-2-2-1-release/es-file-explorer-file-manager-4-2-2-1-android-apk-download/

3. Download the smart-life-smart-living apk.

https://www.apkmirror.com/apk/tuya-inc/smart-life-smart-living/smart-life-smart-living-3-6-1-release/smart-life-smart-living-3-6-1-android-apk-download/

After you installed the emulator, and drag the 2 apk over to install. Open es-file-explorer and click on TOOLS and enable Root. Click on LOCAL, DEVICE, DATA, DATA and look for com.tuya.smartlife, open it and then shared_prefs then look for an xml called preferences_global_keyeuXXXXXXXXXXXXXXXX.xml, XXX is a combination of number and letters depends on account.
Open this file with a file editor, the at the top right corner click the 3 dots, the save as to /mnt/shared/Picture (this is the shared folder in my case). If you don’t want to save it in your computer you can just copy and paste to a notepad or just leave it open and look for the info in there. If you look properly you will find the device_id, local_key and the device name for every single device you have on your account.
Once you get all the information you need to add the following to your configuration.yaml, in this case is a switch, replace the ip from the example with the real ip for your device, the local and the dev_id with the real one.
switch:
- platform: localtuya
host: 192.168.0.8
local_key: xxxxxxxxxxx
device_id: yyyyyyyyyyyy
name: give_any_name
protocol: 3.3

Save the configuration.yaml and now go to the link bellow and download the custom component package. Unzip it and copy just the localtuya folder to your server home assistant into the custom_components folder that is located the same place where your configuration.yaml is. If you don’t have this folder, just create it and copy the localtuya folder you just downloaded.

https://github.com/fastcolors/localtuya-homeassistant

After this go to your Home Assistant page, configuration and first click on check configuration, it you get no errors the restart the router. After you restart the server, all this device will appear under the entities list and you can just use it as normal, in our example, we will have an entity called give_any_name.

If its working, then you did it, if it doesn’t work, then check if the ip, local_key and device_id is correct. If everything is correct and it still doesn’t work try another protocol, like 3.1 or 3.2
If after all this is still doesn’t work them maybe your device has an older protocol and this custom_component is not compatible. In this case check my other video using the modified cloud custom_component.

Thank you and good luck.

En este video, intentaremos configurar el botón de Xiaomi Aqara de segunda generación modelo WXKG11LM como un mando para armar o desarmar la alarma de Home Assistant. También crearemos una pestaña para el panel de alarma.
En un video anterior hemos creado el panel de alarma y las automatizaciones para armar y desarmar.
Si encuentras el video útil, déjanos un comentario. Gracias.

######################
# #
# Alarm #
# #
######################

alarm_control_panel:
- platform: manual
name: Alarma Casa
pending_time: 0
delay_time: 5
trigger_time: 5
code: 1234
disarmed:
trigger_time: 5
armed_home:
pending_time: 5
delay_time: 5
trigger_time: 5
armed_away:
pending_time: 5
delay_time: 5

The link for the Xiaomi Binary Sensors:

https://www.home-assistant.io/integrations/binary_sensor.xiaomi_aqara/

In this video will try to configure a Xiaomi Button (2nd gen) model WXKG11LM as a arming and disarming device for the Home Assistant alarm panel, as well as create an alarm tam on our dashboard for the alarm panel.

You see in my previous video how to create and configure the arm/disarm panel using 5 automations, and 4 scripts.

If you find this useful, please leave a positive comment.


#######################
# #
# Alarm #
# #
######################

alarm_control_panel:
- platform: manual
name: Alarma Casa
pending_time: 0
delay_time: 5
trigger_time: 5
code: 1234
disarmed:
trigger_time: 5
armed_home:
pending_time: 5
delay_time: 5
trigger_time: 5
armed_away:
pending_time: 5
delay_time: 5

The link for the Xiaomi Binary Sensors:

https://www.home-assistant.io/integrations/binary_sensor.xiaomi_aqara/

Así es como tengo yo integrado el Xiaomi V2 dentro del panel de alarma de Home Assistant, los sensores de movimiento de Xiaomi, Sensores de puerta y ventanas, y botones de Xiaomi, para crear una alarma domestica muy potente y totalmente gratuita.

Podéis modificar las autorizaciones para que enciendan mas luces o menos, o crear otras escenas.

Utilizando estas 5 automatizaciones y 4 scripts, tendríais unos 5 segundos después de armar alarma para salir de casa, en este tiempo, la luz del Gateway se pondrá verde, el altavoz de Google reproducirá el mensaje de que el sistema esta siendo armado, y recibirías un mensaje en el móvil que el sistema está armado.

Cuando volvéis o cuando cualquier sensor detecta movimiento, la luz del Gateway se pondrá naranja, el altavoz reproducirá un mensaje de que tenéis 10 segundos para introducir el código.
Si el código se introduce correctamente la alarma se desarma y no sonara, en caso contrario el Gateway de Xiaomi sonara y las luces cambiaran de rojo a azul.

Os dejo debajo el código que tendréis que añadir al archivo configuration.yaml donde podéis modificar el delay, pending y el código de 1234 a lo que quieras.
Después de cualquier modificación es necesario reiniciar el servidor.

Si habéis encontrado el video útil por favor dejar un comentario positivo.

alarm_control_panel:
- platform: manual
name: Alarma Casa
pending_time: 0
delay_time: 5
trigger_time: 5
code: 1234
disarmed:
trigger_time: 5
armed_home:
pending_time: 5
delay_time: 5
trigger_time: 5
armed_away:
pending_time: 5
delay_time: 5