overview for Ecclestoned

Relay and sensor for ice maker in c/homeautomation

[–] Ecclestoned 1 points 9 months ago (1 children)

My concern is that the Shelly won't be able to tell if the ice machine is on or off. The automation would be something like "toggle the ice machine" vs "turn the ice machine on".

If there is some way I could wire a Shelly sense pin to the ice machine controller and tell it to use that to tell whether toggling would turn it on or off. IDK

7

Relay and sensor for ice maker (self.homeautomation)

submitted 9 months ago by Ecclestoned to c/homeautomation

3 comments fedilink

I recently bought a portable ice maker, and want to be able to set it to a schedule/make it smart. Unfortunately, it does not power on when plugged in, and the power on is operated by a momentary push button.

I'm trying to find a relay that can send a power on/off pulse, with a voltage sensor that can tell if the machine is currently on. It would have to accept a variety of voltage supply, because I don't know exactly what the internals operate on yet.

For technology: I don't have zigbee/zwave hub, but am happy to buy one. Currently doing automations through Google Home, and plan to switch to home assistant at some point, so it would need to be compatible with both.

I've been looking at some of the Shelly relays (1, uni), but I've seen mixed reviews if they can operate a momentary switch without flashing tasmota, and if they would be able to sense if the machine is on.

Should I use a dedicated DHCP/DNS server hardware in c/selfhosted

[–] Ecclestoned 1 points 10 months ago

Damn this is so much simpler than the USB 2 version I have from 8 years ago...

Should I use a dedicated DHCP/DNS server hardware in c/selfhosted

[–] Ecclestoned 1 points 10 months ago

make are the controller gas a static IP -- not a static DHCP lease

Ahhh that makes complete sense. I'll look into it. Thanks!

Should I use a dedicated DHCP/DNS server hardware in c/selfhosted

[–] Ecclestoned 1 points 10 months ago (1 children)

Damn, I didn't realize the amount of hate for DHCP. Ive used an already configured system with a DHCP/DNS server set up and it was super easy to manage. Want to change or add a static IP? Edit the text file, add the MAC, reload.

I didn't know this wasn't reflective of the overall experience.

Should I use a dedicated DHCP/DNS server hardware in c/selfhosted

[–] Ecclestoned 1 points 10 months ago

Already done, but I ran into issues when I needed to change the IP or MAC.

Should I use a dedicated DHCP/DNS server hardware in c/selfhosted

[–] Ecclestoned 1 points 10 months ago

Is there any specific reason you need DHCP to assign an IP to your main hosting server vs setting it all statically?

I've done this. I think the real problem is if I ever change the server MAC or IP, as now the unifi server isn't picked up by the USG, which means I can't change the static address.

Should I use a dedicated DHCP/DNS server hardware in c/selfhosted

[–] Ecclestoned 1 points 10 months ago (2 children)

So this is where I'm a little confused. The USG had the option to assign a static IP (which I've done), but if you ever need to CHANGE that IP... Chaos. From what I understand the USG needs to propagate that IP to all your devices, but it uses the controller to do that. Then you also run into issues with IP leases having to time out. Same problem occurs if I ever upgrade my server and change out the MAC address. Because now the IP is assigned to the old MAC.

I'm not sure if there's any way around this. But it basically locks me in to keeping the controller (and thus my server) at a single, fixed IP, without any chance of changing it.

Should I use a dedicated DHCP/DNS server hardware in c/selfhosted

[–] Ecclestoned 1 points 10 months ago (2 children)

I've completely bricked two SD cards using a Pi. The USB option sounds interesting, I'll have to try it.

37

Should I use a dedicated DHCP/DNS server hardware (self.selfhosted)

submitted 10 months ago* (last edited 10 months ago) by Ecclestoned to c/selfhosted

30 comments fedilink

My current setup has my DHCP + DNS on my Unifi USG. However, as I have all my apps hosted on a different server (unifi, plex, home assistant, NAS, etc.) I've ran into issues trying to get things set up.

Basically, Unifi needs to know where the unifi server is, but it's assigning the IP address to it.

Should I put DHCP+DNS onto it's own system? Should I put it on my current server? And any non-Pi recommendations for systems? (I've had the PI filesystem clobber itself too many times)

Edit: I'm starting to think that the real problem is having UNIFI on the same system as the server, as it prevents me reconfiguring any of the server routing information without also disconnecting unifi...

Edit 2: I'm going to try switching the server from a static DHCP lease to a static IP. If that's doesn't work, then I think I'll move the unifi server onto it's own system. Thanks!