Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DIM-2 and MQTT auto discover issue? #6

Closed
mattiasjonsson opened this issue Dec 11, 2019 · 6 comments
Closed

DIM-2 and MQTT auto discover issue? #6

mattiasjonsson opened this issue Dec 11, 2019 · 6 comments

Comments

@mattiasjonsson
Copy link

MQTT auto discover does not list input 2 of DIM-2 devices. The MQTT broker does however receive topics/messages from both inputs of the device.

@icanos
Copy link
Owner

icanos commented Dec 12, 2019

Are the inputs identically named in the Plejd app? Otherwise they should appear in HA.

@mattiasjonsson
Copy link
Author

True. I checked the names and of course they had the same identical name. Sorry for bother you about this issue. I should have thought of that myself. ;)

Another question: Is it possible to add the entities by hand in the configuration.yaml? And If so, how would I go about doing that?

@icanos
Copy link
Owner

icanos commented Dec 12, 2019

Nothing to worry about :) in what scenario do you need to add devices to the config? It would need to know the Plejd device id which is fetched from the API.

@mattiasjonsson
Copy link
Author

I needed to be able to change the entity ids and have more overall control. I managed to solve it.
Turned off MQTT auto discovery and just added the Plejd devices as MQTT lights like this:

light:
  platform: mqtt
  name: "plejd_kok_kokso"
  unique_id: "light.plejd.kok_kokso"
  state_topic: "homeassistant/light/plejd/18/state"
  command_topic: "homeassistant/light/plejd/18/set"
  brightness_state_topic: "homeassistant/light/plejd/18/brightness"
  brightness_command_topic: "homeassistant/light/plejd/18/setBrightness"
  payload_on: 1
  payload_off: 0
  optimistic: false

@icanos
Copy link
Owner

icanos commented Dec 13, 2019

That's a neat solution, do you mind if I add that to the readme? :)

@mattiasjonsson
Copy link
Author

Sure, go ahead :)

@icanos icanos mentioned this issue Dec 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants