It will likely be just duplicating the services, I’ll work it through when I incorporate the PR
1 Like
Thx in advance
hey @RogTP , was testing my covers with some modified code
one question, for light i see the state displayed in json format
for switch i see it in raw format ? also for the code i added for covers i see it in raw?
why is that ?
i see you used fo light doimain, the json schema, but not for the switch domain, is there a reason for it?
elif ent_domain == "light":
del config["json_attr_t"]
config["cmd_t"] = f"{mybase}set_light"
config["schema"] = "json"
I don’t think this was my code, but I suspect that is because a switch is either on or off, whilst a light can set colours/etc
Ah ok, submitted a PR for covers , based on switch code… I tried local and it worked
I’m not a developer, but it’s a beginning 
There is state open…
But not state opening… Also set cover position is not yet included, my covers don’t support those features
Hello All, Nice to see that Home assistant interraction over mqtt is going on !
I’ve just setup Discoverystream for my warmup heater.
since i get all my value state, i can’t succeed modifying heating modes or
Temp setpoint…
Do you know what kind of command i need to send ?
Thx
We are using the MQTT discoverystream as a master->multiple slaves configuration.
However not all slaves need access to all the data we put on the discoverystream’s base topic.
Would it be possible to have subtopics that we can publish to? such that in the clients we can subscribe to “base_topic/slave_topic” instead?
I tried adding multiple discoverystream objects in my .yaml but did not have any luck.
Thank you for your time.