![]() I'm working on an MQTT solution with Mosquitto and Node Red (on a Raspberry Pi) and it will also require some Groovy on SmartThings but a much simpler solution IMO. ![]() SmartThings is going to be moving in another development platform direction as well at some point. Because there was C++ code on the MySensors side of things and then Groovy on the SmartThings side it just seemed like a brittle integration with the design and how I wrote the code. I felt like the custom transport would require more maintenance and I wanted more of any option that was configuration rather than coding. After writing the transport and using it for a bit I've decided to go another direction with the integration to SmartThings. There doesn't seem to be a ton of interest in this but I wanted to provide an update. This way I don't have to worry that I created too small a VM disk, or that the VM will later outgrow the disk size that was originally allocated for it. So, having proved that to myself, I'll pass on the tip: I now create a VM's disk to be as large as I can imagine it would ever need to grow, and then I let the thin-client mechanism maintain the true size of the virtual disk to be only as large as what is actually necessary. So, I did the experiment, and it turns out that is true if the ProxMox dataset isn't configured as "thin-client" or if automatic file compression isn't turned on, but fortunately the true size of the raw file does indeed shrink down if those two conditions are enabled. ![]() Originally I was concerned that because, if using ZFS as the file system, ProxMox only allows storing a VM as a pre-allocated "raw" file (rather than as a qcow2 file as ProxMox would if ProMox were using a linux ext16 file system instead of ZFS) that the file would take up enormous space even if the raw file (i.e. So, in total, four things need to be set correctly for it to work optimally. So, those two things plus the ssd emulation that you mentioned, and of course automatic file compression like lz4 needs to be enabled. ![]() Also the ProxMox dataset that the VM is saved on needs to be set to thin-client. Looking into this, I think checking the "Discard" box on the "Hard Disk" tab of the "Create a Virtual Machine" dialog box inside ProxMox may automatically accomplish the same thing. You can also use the command line tool fstrim to manually discard unused data. It's a bumpier ride at least at first but i think homeassistant wins in the long run - and it's open said in Best PC platform for running Esxi/Docker at. Actually used and appretiated by everyone in the house Is has integrations for more or less everything and if not there will be soon or you can add it yourself.Įxample dashboard that i have in the house with car heating/charging, cameras and tons of sensors and zigbee devices. For my personal homeautomation i have moved over completely to homeassistant and it's possible to create beautiful dashboards with little effort. It has a very active community that isn't afraid of changing core concepts when needed which is both a strength and sometimes a weakness. Very light weight.Īnother alternative (maybe obvious) is homeassistant but it might be a bit overwelming since it's very flexible and can be run in so many different ways so you will find tons of howtos that doesn't work anymore. I have a few weather station systems running remote and then i use domoticz in docker containers on off site servers (but i've also had it running on rasberry PIs). The UI is not the prettiest (even if you can fix that by setting up custom dashboards like dashticz or so) but it's very functional and i think it has a good default setup with trendlines per sensor for day/month/year using highcharts. If you want the fastest way to get started with good trend charts i still think Domoticz is a great choise. I think i've tried them all in the table but i always return to 2 alternatives: homeassistant and domoticz. Normally i don't give advice like this (and i agree with - It's great to discuss with a friend!) but here a my 2 cents. Selecting the "right" controller is of course a matter of opinion and depends how far you want to go into the homeautomation swamp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |