ovmf packagelibvirt-bin/var/lib/libvirt/qemu/nvram to store NVRAM from a UEFI-enabled virtual machine (VM)libvirt edit $VM_NAME and amend the XML definition.
<os>
<type arch='x86_64' machine='pc-q35-2.11'>hvm</type>
<loader readonly='yes' secure='no' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram template='/usr/share/OVMF/OVMF_VARS.fd'/>
<boot dev='hd'/>
</os>
The device MOES IR Control Hub, which uses Tuya ESP8266 is no longer vulnerable to the vulnerability that tuya-convert exploits. You will need to open the device to flash it.
They are currently shipped with an TYWE3S which is an ESP8266 (as of June, 2021). You can see the pin outs for the TYWE3S at the Tasmota site.
Use a thin utility knife to open, I would recommend starting at the USB port area. There are two tabs on either side, and a few spread throughout. Once you have the device open and have connections setup you are ready to flash.
GPI0 to GND to start flash mode (when RST or power on the device, you will know you are in flash mode because the blue status LED does not come on)RX, TX, GND to your USB TTL (remember RX and TX are reversed for the USB TTL side)GND on TYWE3S is connected to the same ground plane as the rest of the board (i.e. GND on your USB TTL)esptool (rev 1ca08af instead of master due to Issue #635 in esptool)Last updated April 2, 2022.
My partner and I purchased a new home, and it came prewired with CAT5E, and outside rough-ins for security cameras.
With those requirements in mind, I settled on the following hardware from Ubiquiti for an end-to-end solution:
I decided it was time to get "serious" and have a proper pro-sumer setup at home for Internet access, and while we were at it: Security cameras! I didn't want to go with Hikvision or any of the other Chinese manufacturers of IP cameras.
For security cameras (UniFI Protect), I went with the following:
These products, in my opinion, are not prosumer. They have a number of issues, especially for the price point (I would expect better.) In a lot of cases, pfsense would buy you better bang for your buck.
I have replaced the UDM with an opnSense install, but I don't know what to do with my existing cameras as it was not a low-cost or low-effort investment.
Ubiquiti may be "okay" if you're not doing anything complicated, but at that point you might as well buy a cheaper solution that "just works" and doesn't arbitrarily have features removed or just plain not working.
deCONZ / Phoscon-GW recommends a full blown Xorg install on a Raspberry Pi to access their GUI. deCONZ is a utility to work with Zigbee controller provided by Raspbee / Conbee. deCONZ GUI provides more advanced control of Zigbee devices, and has functionality that is not available via web interface/REST API.
No need to install a full blown UI if you want to run headless. These instructions are for Raspbian.
Make sure to disable and stop existing deconz services if enabled:
systemctl disable deconz
systemctl stop deconzYou may also have deconz-gui service if you have followed their install guide, so make sure to disable and stop this as well if applicable.
Install TigerVNC which we will use to provide headless VNC access to the GUI:apt-get install tigervnc-standalone-server
You will create a new systemd service definition, which is outlined below .
/etc/systemd/system/deconz-vnc.service
[Unit]
Description=deCONZ: ZigBee gateway -- GUI/REST API VNC
Wants=deconz-init.service deconz-update.service
[Service]
User=1000
Environment="DISPLAY=:0"
ExecStartPre=/usr/bin/tigervncserver -geometry 1024x768 -useold -SecurityTypes None -localhost yes -noxstartup "$DISPLAY"
ExecStart=/usr/bin/deCONZ --http-port=80
Restart=on-failure
StartLimitIntervalSec=0
RestartSec=30
AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_KILL CAP_SYS_BOOT CAP_SYS_TIME
[Install]
WantedBy=multi-user.targetThen reload systemd, enable and start the newly created service:
systemctl daemon-reload
systemctl enable deconz-vnc
systemctl start deconz-vncOnce this is done you can setup a SSH port forward to localhost:5900 and access deCONZ GUI using your favourite VNC viewer.
RMCARD205 supplies metrics via SNMP for all supported CyberPower UPS. Who doesn't want to display power usage on their UPS via Home Assistant?
I created a "package" for CyberPower UPS RMCARD that exports data via SNMP. This assumes your default read-only community is named public.
packages/ups.yaml:
sensor:
- platform: snmp
scan_interval: 60
name: ups_nompower
host: x.x.x.x
baseoid: 1.3.6.1.4.1.3808.1.1.1.4.2.5.0
accept_errors: true
unit_of_measurement: Watts
- platform: snmp
scan_interval: 60
name: ups_nominv
host: x.x.x.x
baseoid: 1.3.6.1.4.1.3808.1.1.1.3.2.1.0
accept_errors: true
unit_of_measurement: Volts
value_template: '{{((value | int) / 10) | int}}'
- platform: snmp
scan_interval: 60
name: ups_itemp
host: x.x.x.x
baseoid: 1.3.6.1.4.1.3808.1.1.1.2.2.3.0
accept_errors: true
unit_of_measurement: "°C"
- platform: snmp
scan_interval: 60
name: ups_timeleft
host: x.x.x.x
baseoid: 1.3.6.1.4.1.3808.1.1.1.2.2.4.0
accept_errors: true
unit_of_measurement: 'minutes'
value_template: '{{((value | int) / 6000) | int}}'
- platform: snmp
scan_interval: 30
name: ups_status
host: x.x.x.x
baseoid: 1.3.6.1.4.1.3808.1.1.1.4.1.1.0
accept_errors: true
value_template: >-
{% set status = (value | int) %}
{%- if status == 2 -%}
Online
{%- elif status == 3 -%}
On Battery
{%- elif status == 4 -%}
On Boost
{%- elif status == 5 -%}
On Sleep
{%- elif status == 6 -%}
Off
{%- elif status == 7 -%}
Rebooting
{%- elif status == 8 -%}
On ECO
{%- elif status == 9 -%}
On Bypass
{%- elif status == 10 -%}
On Buck
{%- elif status == 11 -%}
On Overload
{%- else -%}
Unknown
{%- endif -%}
group:
ups:
name: UPS
entities:
- sensor.ups_status
- sensor.ups_nompower
- sensor.ups_nominv
- sensor.ups_itemp
- sensor.ups_timeleft
homeassistant:
customize:
sensor.ups_nompower:
friendly_name: 'UPS Nominal Output Power'
icon: mdi:flash
sensor.ups_nominv:
friendly_name: 'UPS Nominal Input Voltage'
icon: mdi:flash
sensor.ups_status:
friendly_name: 'UPS Status'
icon: mdi:information-outline
sensor.ups_itemp:
friendly_name: 'UPS Internal Temperature'
icon: mdi:thermometer
sensor.ups_timeleft:
friendly_name: 'UPS Time Left'
icon: mdi:clock-alert