9 trillion cloud polling integrations, but getting rid of truly local integrations. gg
I guess that’s more of a delta for my fork to inherit, ugh.
i hate it.
9 trillion cloud polling integrations, but getting rid of truly local integrations. gg
I guess that’s more of a delta for my fork to inherit, ugh.
I haven’t had to reset mine in 4 years. I would get another radio and move it to its own network.
Yes. It generates a lot of traffic. Once you get it reporting reliably, I struggle to see the benefit of a more expensive solution unless you want more channels.
I have the aeotec zwave HEM that I imagine you are talking about, and have been using it for 4 years. Mine is on its own zwave modem, separate from the one I use for everything else, but you can also try increasing the reporting intervals, and maybe disabling reporting for anything you don’t care about.
I had the benefit of pjsip set logger verbose on
to display raw SIP stanzas while I was getting it working with asterisk. You may wish to do some tcpdump
ing to see what is going on.
SIP is SIP. As I stated elsewhere, I actually have it working with asterisk initiating the call from its dialplan.
Yes, I have it actually going via my asterisk dialplan from my grandstream HT802. It should just work if SIP and RTP can pass correctly.
Yes, Plex would work much better. With Plex you can just use home assistant’s own media_player
stuff.
Good luck. Deep linking to intents that actually start playing a program, if you get it to work today, it will probably stop working next month. Intents are internal to apps, and even if the intent is static, the ID of the content most certainly is not. I had this working as a POC to start playing channels on YouTube TV but the maintenance burden made it utterly not worth it. If the content was local and available to play in Kodi it would be a different story.
The Rocket is ultrasonic.
My brother has a Rocket in his tank, it works great.
Get a Beckett Rocket and an RTL-SDR dongle. You can use rtl_433 to decode the chirps from the Rocket and do whatever you want with them. You keep the float, it screws into an unused port on the top of the tank.
it was uncontroversial and undramatic.
The horrors. This is why lemmy is so horrible!
I will say, I’ve had an old mechanical window AC trip the ZEN15’s overload detection when the thermostat short cycled and the compressor was stalled. So I would trust it for that in a pinch, and especially with a resistive load. But for an outdoor heating element application, I still would oversize the switching device (and get the 40A contactor), and put 15A circuit breakers before the contactor. Also, that 40A device can drive either a two pole 240V device (unison contacts) or two 120V devices, so you could just put each heater on its own pole and heat up your wiring a little less. Or probably just wire only one pole, I haven’t read the manual.
My guess is that they see their device controlling a heating element of unknown (to them) provenance as a liability. My zen15 manual specifically has a warning against using it with heaters.
CAUTION This is an electrical device - please use caution when installing and operating the Power Switch. Remote control of appliances may result in unintentional or automated activation of power. Do NOT use this Z-Wave device to control electric heaters or other appliances which produce the risk of fire, burns, or electrical shock when unattended.
Yeah, these days meaning either “an algorithm of any kind” or a complex bounded random number generator that draws a gigawatt to run.
I agree mostly; for example, ZW bulbs are outrageously expensive. I have a Kwikset lock, a couple Zooz ZEN15s, some dimmable lamp modules, Aeotec HEM, a Remotec IR AC controller, GE switches, and Honeywell T6 Pro thermostats.
Nothing wrong with Z-Wave. I have 3 radios (2 zw [one for Aeotec HEM since it generates tons of traffic], one zig) just so I can use whatever is cheapest or available for a particular application. All of the “energy controlling” (meaning, not light bulbs) is ZWave because it seems to have more robust state verification built into the protocol. Also, it’s 915MHz and I live in a very crowded RF environment on 2.4.
You don’t like being forced to buy a new garage door opener every time the manufacturer’s product manager takes a shit?
Lol, and the project is slowly trying to force everyone to use it. I’ll continue to use core in a venv and manage my own OS, thanks.