No Plejd hub needed.
I do not guarantee that this will work or even that it will not harm your system. I don't see what harm it could cause, but I promise nothing.
-
Make sure you have a working Bluetooth integration in Home Assistant (a bluetooth proxy should work too)
-
Make sure you have no other plejd custom components or add-ons running.
-
Put the
plejd
directory in your<config>/custom_components
. -
Restart Home Assistant
-
Hopefully, your Plejd mesh will be auto discovered and you should see a message popping up in your integrations page.
-
Log in with the credentials you use in the Plejd app when prompted (email address and password)
-
An alternate method for installation is to add this repo (
thomasloven/hass_plejd
) as a custom repository in HACS, add the integration from HACS, restart Home Assistant and continue as above
Add this to your Home Assistant configuration.yaml to get as much information as possible
logger:
default: warn
logs:
custom_components.plejd: debug
Here are some other Plejd integrations by some awesome people and how this is different:
I've pulled inspiration from all of them.
hassio-plejd | @icanos | Works only with Home Assistant OS. Relies on MQTT for communication. Requires exclusive access to the Bluetooth dongle. Does not support Bluetooth Proxy. |
plejd2mqtt | @thomasloven | Somewhat outdated stand-alone version of the above. Relies on MQTT for communication. Requires exclusive access to the Bluetooth dongle. Does not support Bluetooth Proxy. Does not support switches or scenes. |
ha-plejd | @klali (also check this fork by @bnordli) |
Does not communicate with the Plejd API and therefore requires you to extract the cryptokey and device data from the Plejd app somehow. No auto discovery. Requires exclusive access to the Bluetooth dongle. Does not support Bluetooth Proxy. |
homey-plejd | @emilohman | For Homey |
homebridge-plejd | @blommegard | For Homebridge |