User Tools

Site Tools


burim:home-assistant

https://youtu.be/_FktMQSD5LE

sun hours calculation

Multiplus integration

Backup

Home Assistant upgrade

Bugs

Victron integration

Kalendar Google integration

Thermostat

Water leak detect

Headline

Github documentation

Thermostat

Sieren

Privileged cmd

Zigbee2mqtt home assistant

Homekit remotly

home assistant docker + mqtt

switch command use this for rest api integration

Headline

Headline

Remote cmd server

Rest api

rest API integration e.g. tasmota

node-red aqara

issues SNZB-03

backup

Hisense TV

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

mount

snapshot

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”

mail notification

burim/home-assistant.txt · Last modified: 2025/06/16 09:02 by burim

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki