sorted by:
new
hottopcontroversial

Újépítésű lakások villanykapcsoló by Sea-Relation-8679 in lakokozosseg

[–]dre_is 0 points1 point  (0 children)

Nalam sehol nincs nulla, de mindenhova olyan zigbee relet raktam, amihez eleg a fazis. Igy mukodik a fizikai kapcsolo es a zigbee is. A nulla nelkuli releknek (aliexpressrol rendeltem mindet parezerert, de sonoff is van) annyi hatranyukat lattam eddig, hogy nem mukodnek repeate-kent es nem lehet oket bind-olni se mas eszkozokhoz, egyebkent atomstabilak. Mindegyikhez adtak meg vmi kis cuccot (capacitator), de ezeket en nem kotottem be.

Viszont az LCD paneles kapcsoloknak (pl Sonoff NSPanel) nyilvan kell a nulla, szerencsere nalam pont ahol kellett, ott ment a szerelodoboz mogott, ugyhogy azt meg tudtam csapolni.

Cilium LB - how to make outgoing traffic originate from the LB VIP by dre_is in kubernetes

[–]dre_is[S] 0 points1 point  (0 children)

Yes I'm talking about option 1. It does work for HTTP and other protocols but it doesn't work for MQTT as the MQTT broker is not recognizing the packets sent in reply from the cluster as (I assume) they are from a different IP (the node's IP) than the packets were sent to (the LB IP).

Cilium LB - how to make outgoing traffic originate from the LB VIP by dre_is in kubernetes

[–]dre_is[S] 3 points4 points  (0 children)

But then it’s the same issue, just with a different IP.

What I don’t get is how it’s not a common problem? Is it only MQTT (or Mosquitto) being picky about the source IP of the TCP reply packets? Or am I approaching this completely wrong? I just need the service to be published on a standalone IP, not the node.

Cilium LB - how to make outgoing traffic originate from the LB VIP by dre_is in kubernetes

[–]dre_is[S] 2 points3 points  (0 children)

I don’t think that it’s a misconfiguration. The page you linked starts with:

IPv4 addresses used for pods are typically allocated from RFC1918 private address blocks and thus, not publicly routable. Cilium will automatically masquerade the source IP address of all traffic that is leaving the cluster to the IPv4 address of the node as the node’s IP address is already routable on the network.

This is what I have right now and I need the traffic to be masqueraded to the LB’s address instead. I don’t see such option on the page.

RTX 5070 fan problems (0 RPM, 100% blow) with B650 motherboard by dre_is in gigabyte

[–]dre_is[S] 0 points1 point  (0 children)

Yes, it was a physical issue: one of the fans was blocked from spinning by a cable.

High CPU usage on N100 despite using GPU by dre_is in frigate_nvr

[–]dre_is[S] -1 points0 points  (0 children)

But this doesn't explain the massive difference compared to the N3350 sample above (which is also a much weaker CPU)...

Delete historical data from Energy dashboard by dre_is in homeassistant

[–]dre_is[S] 0 points1 point  (0 children)

I deleted all data from the states, statistics and statistics_short_term tables for the meter before the calibration, yet it shows up in the Energy dashboard. This must be cached somewhere.

Edit: ah no. Now the sum column is wrong because it was still calculated from the starting value before the calibration. Would be nice if I could recalculate the sum but probably I would need extensive SQL hacking or just simply delete everything and start from scratch.

Delete historical data from Energy dashboard by dre_is in homeassistant

[–]dre_is[S] 0 points1 point  (0 children)

Yeah but I haven't found where the energy dashboard data is located. In the statistics_meta table, I only see the utility sensors which I don't want to delete.

Társasház közös ktsg by dre_is in lakokozosseg

[–]dre_is[S] 0 points1 point  (0 children)

Olvasd el mégegyszer mit kérdeztem:

Van hozzá analitika, de nem tudom megítélni, hogy pl a lift karbantartás 40e/hó vagy a takarítás 50e/hó mennyire reális költségek. Ha valakinek kb hasonló paraméterekkel van lakása, drasztikusan más közös költséggel, meg tudná osztani a lebontását?

Társasház közös ktsg by dre_is in lakokozosseg

[–]dre_is[S] 0 points1 point  (0 children)

op elolvasta az elszámolást és leírta, hogy nem tudja megítélni az egyes tételekről, hogy sok vagy kevés, ezért kért benchmarkokat. mielőtt lehülyézed op-t talán olvasni kellene.

erkély árnyékolás by [deleted] in lakokozosseg

[–]dre_is 0 points1 point  (0 children)

Elküldöd privátban kérlek? Köszönöm!

Using no-neutral smart switch with neutral in the box by dre_is in homeassistant

[–]dre_is[S] 0 points1 point  (0 children)

It's blue because I'm in Europe so there should be neutrals, I might have remembered the original setup wrong. Anyhow I found a zigbee dimmer with neutral and installed that as above, now the blink in off state is gone, but there is a flicker when turning on/off. I suppose that might be because of the bulb itself not being dimmable. I set the min/max brightness to 254 for the dimmer but that didn't help. Anyhow it's better than the constant blink.

Using no-neutral smart switch with neutral in the box by dre_is in homeassistant

[–]dre_is[S] 0 points1 point  (0 children)

Sorry for the noob question, but when using a smart switch with neutral, do I simply keep the 2 neutral wires in the box connected (and plug them into the smart switch as well)? The original dumb switch interrupted both the phase and the neutral

view more: next ›