https://community.home-assistant.io/t/victron-venus-os-with-mqtt-sensors-switches-and-numbers/527931
https://www.imval.tech/index.php/blog/victron-mqtt-server-bridging
https://www.imval.tech/index.php/blog/add-your-victron-system-in-home-assistant
https://github.com/Mikescops/terraform-provider-homeassistant
https://siytek.com/home-assistant-shell/
https://community.home-assistant.io/t/using-shell-command-in-automations/150164/7
https://community.home-assistant.io/t/switch-template-entities-not-showing-up/162353/5
More privileged commands
https://community.home-assistant.io/t/ssh-command-to-shutdown-hassio-on-a-pi3/75423/9
Zigbee2mqtt
ESXi installation
https://community.home-assistant.io/t/hass-io-on-vmware-esxi-6-7-step-by-step/151419
https://community.hom.ee/t/aqara-xiaomi-geraete-in-homee-zigbee2mqtt-nodred-enocean-simulation/24617
https://community.home-assistant.io/t/sharing-your-configuration-on-github/195144
https://community.home-assistant.io/t/how-can-i-backup-hassio-to-github/97095
https://community.home-assistant.io/t/hisense-tv-control/97638/40
https://community.home-assistant.io/t/hisense-tv-control/97638
To connect to your own MQTT broker:
# Example configuration.yaml entry mqtt:
broker: IP_ADDRESS_BROKER
YAMLCopy Manual configuration is required when connecting to a broker over TLS.
# Example configuration.yaml entry mqtt:
certificate: "PATH_TO_CA.crt" broker: "IP_ADDRESS_BROKER" port: 8883 username: "MQTT_USERNAME" password: !secret MQTT_PASSWORD
all mounts to be done under /share/ so that plex docker can see them.
mount -t nfs4 10.11.x.253:/mnt/hdd/movie/ /media/movie/
synoboot.vmdk is not a ESXi format. You can not create snapshots for synoboot.vmdk before you convert it to ESXi format.
Apparently synoboot.vmdk was copied from Workstation or Fusion by somebody who was not aware of the different vmdk formats.
If you open synoboot.vmdk you will see that the createType is not VMFS but monolithicSparse.
Also note:
DiskLib_Check() failed for source disk 'synoboot-s001.vmdk': The file specified is not a virtual disk (15). So to sum it up - we are seeing expected behaviour here !
Power off the VM and run
vmkfstools -i synoboot.vmdk synoboot-esxi.vmdk
and then replace the WS-type vmdk with the newly created one.
After that is done you should be able to create a snapshot as expected.
Ulli
Do you need support with a recovery problem ? - send a message via skype “sanbarrow”