esphome-mitsubishiheatpump VS dscKeybusInterface

Controlling Mitsubishi mini split heat pumps instead of paying hundreds for Mitsubishis solution: https://github.com/geoffdavis/esphome-mitsubishiheatpump

DIY Plug in: this Github Project describes a way to diy a plug in connection running on ESPhome for a few $ of parts, but I'm a bit of a novice and don't know how I would connect this to Homekit.

If you Home Assistant or ESPHome, this is the jam. https://github.com/geoffdavis/esphome-mitsubishiheatpump

Highly likely you're experiencing a watchdog error on an idle core. The only way to know for sure is to enable logger, which will be a challenge here. You can see an example here., but this is a widely reported and poorly understood issue.

If you can add homeassistant, you should look at https://github.com/geoffdavis/esphome-mitsubishiheatpump -- we're using it with 5 split units. It works great, is faster than infrared, and cheaper than the wired or wireless control options from Mitsubishi.

If your Mitsubishi uses IR for it's remote, this probably would work: https://github.com/geoffdavis/esphome-mitsubishiheatpump

Or, you can use a Broadlink IR blaster to clone the remote.

If your heat pump talks to MEL cloud (Mitsubishi's cloud thingy) then this should work: https://www.home-assistant.io/integrations/melcloud/

I have yet to buy a "smart" device that I haven't been able to control through HA. The Broadlink RF/IR bridges even makes anything with a remote automatable.

Seriously, If it wasn't for Home Assistant, the "smartness" of smart devices would be next to useless.

Brought an inactive home security system onto Home Assistant using the below repository, so I can track everything from smoke alarms to motion, doors, and windows. I swear there's a niche business opportunity in retrofitting all these deactivated systems!

https://github.com/taligentx/dscKeybusInterface

The sensors themselves are relatively easy to defeat, a strong enough magnet in the right position and you can pop a door or window open without tripping the sensor. This specific DSC panel was chosen as the bus protocol was unencrypted(the only reasonable attack would be a playback attack, everything needs a user, master, or installer code), but it would be relatively easy to add an esp8266 behind the wall plate of a keypad. (take notes, this is why you should have motion detectors wired inside, and add latching tamper zones). I don't have to worry about the encryption issue, since the keybus line doesn't go outside of a locked closet, which will probably use the latching tamper preset.

Additional context for anyone that's trying to google the same thing. DSC power series pc1816, pc1832, and pc1864 main boards use this connector for the battery harness, which is difficult to source. (This sub is also relevant as there is a DSC key bus Protocol library for Arduino or espressif boards, this was one of the last boards they made before the bus line was encrypted).

Actually it's not "dated" as much as it's "timeless" :) Things get a lot easier with a serial cable and the DLS software. You can even build your own Envisalink like module that works with Home Assistant, for about $6, see: https://github.com/taligentx/dscKeybusInterface

There is a lot of work done for DSC powerseries keybus interface (not the NEO version): - https://github.com/taligentx/dscKeybusInterface - https://github.com/taligentx/dscKeybusInterface/tree/expander But I cannot find any documentation online for the NEO version.

What's the main goal here? The EnvisaLink™ EVL-4EZR module works really well with home automation like Home Assistant or, if you want a less expensive solution taligentx / dscKeybusInterface is an open source solution which can run on a Wemos D1 mini (< $10). Both of these solutions appear to the DSC panel to be a keypad so unless you exceed the maximum number of keypads for a given panel then you should be OK.

Speaking of DIY, you can build your own for under $10 in components and use opensource software like taligentx / dscKeybusInterface, then monitor yourself with Home Assistant. There is even open source software to recover the installer code. So the options for such an panel are not limited.

I'm wondering because I'm planning to run this project on the system to recover the installer code. I'm a little worried that doing so will start dialing to the old alarm company.

Did you check if https://github.com/taligentx/dscKeybusInterface would support to unlock it? It would only require an arduino and a few days maximum to run (most likely a few hours). I've done it on my panel although it was more recent.

If one doesn't like the $100 cost of Envisalink, with DSC systems there is open source software on GitHub that uses a $5 Wemos D1 mini board and another $1 worth of electronic components (couple resistors and a transistor) to interface directly to the KeyBus and then provides several methods of control.