| 22 Nov 2021 |
 @hexa:lossy.network | neat | 13:45:14 |
| @hexa:lossy.network | with the nvme ssd mount? | 13:45:24 |
 CRTified | That's also why I'm able to switch to an SSD as boot device now | 13:45:27 |
 Linux Hackerman |
- don't run your HA on an SD card
| 13:45:28 |
| @hexa:lossy.network | *
use the nvme ssd mount
| 13:45:38 |
| Linux Hackerman | SD cards are the worst | 13:45:38 |
| @hexa:lossy.network | * ~> use the nvme ssd mount
| 13:45:42 |
| CRTified | yes, bought that and it will be delivered today | 13:45:54 |
| @hexa:lossy.network | using an sd card for write intensive stuff is asking for trouble | 13:46:01 |
| @hexa:lossy.network | decoupling the controller/api and the frontend of homeautomation would be neat | 13:47:02 |
| @hexa:lossy.network | the controller could work in a consensus based fashion | 13:47:08 |
| CRTified | In reply to @hexa:lossy.network
using an sd card for write intensive stuff is asking for trouble Yeah, I kind of knew that before | 13:47:10 |
| CRTified | In reply to @hexa:lossy.network
decoupling the controller/api and the frontend of homeautomation would be neat Well, that should be easy, at least for the whole MQTT-based stuff | 13:47:26 |
| @hexa:lossy.network | to be fair, I'm only using mqtt for z2m these days | 13:47:40 |
| @hexa:lossy.network | moved away from tasmota completely in favor of esphome | 13:47:49 |
| CRTified | Same for me | 13:48:01 |
| CRTified | esphome for DIY-projects and sonoff stuff, and z2m for everything else | 13:48:11 |
| CRTified | But esphome is also able to do mqtt | 13:48:16 |
| @hexa:lossy.network | yep, we're controlling our hackspace door via esphome and authenticated mqtt for a protected path in mosquitto | 13:48:38 |
| CRTified | So it should be relatively easy to use $favorite_language and any MQTT library to get something working | 13:48:43 |
| CRTified | As a workaround for lacking integrations, it would probably make sense to use the integrations available in HomeAssistant (exposed over the http component) | 13:49:57 |
| CRTified | That would allow interacting with newer stuff from HA while having the automations separated away from it | 13:50:21 |
| CRTified | * That would allow interacting with newer/unsupported stuff from HA while having the automations separated away from it | 13:50:34 |
| CRTified | So HA would have two roles in that case:
- Providing an API for the integrations unsupported by the "automation engine"
- Providing the frontend
| 13:51:26 |
| CRTified | Someone here wanted to start an alternative to HA, IIRC. Maybe that "easy HA integration" might also be great for the first prototype | 13:52:40 |
| @hexa:lossy.network | one does not simply... | 14:13:47 |
| 23 Nov 2021 |
|  @server_stats:nordgedanken.dev left the room. | 01:48:11 |
|  felschr joined the room. | 16:28:44 |
| CRTified | Running on an NVMe-SSD now (with no SD-card involved in any way 😁) | 23:18:19 |
| CRTified | As a side-effect: deploying with nixops got significantly faster | 23:18:34 |
