-
Notifications
You must be signed in to change notification settings - Fork 3
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
[Loxone] LightControllerV2: Can't switch off with rule / Alexa #10
Comments
Thanks Daniel for the feedback. Let me try to address it.
The ID of “all off” mood.
How it works: the moods list, which includes the mappings between mood IDs
and mood names is received from the mini server dynamically. This
unfortunately means the ID assigned to the “all off” mood can’t be
predicted until miniserver sends these mappings.
For the short term, you may enable debug logs and read the ID from the log:
logger.debug("Adding mood {} (name={}, isUsed={}, t5={}, static={}", mood.id,
mood.name,
mood.isUsed, mood.isT5Controlled, mood.isStatic);
I think the ID will not change on a specific installation, but who knows
what happens after the FW update, so this is not a clean way.
There are several ways of resolving this long term.
1. I can expose its ID through some number item.
2. I can replace the mood IDs for the set mood number channel with simply
indexes - the moods will be 1,2,3... and all off can be 0. Open question:
what order of moods to assume for indexing?
3. I can create a separate switch channel to switch all moods off.
What would you suggest would work best from your perspective?
Second topic: Enabling/disabling individual moods.
It has been currently designed on purpose that way that the main number
channel is used to set single mood and channels for individual moods mix
them in/out. It kind of maps what Loxone had in mind creating this
controller.
I have not anticipated that the mood channels can be used with Alexa the
way you use them. This is actually cool.
Here again we have a number of possible solutions:
1) add a configuration parameter to define if moods mix or simply set and
disable other moods
2) add extra channel per each mood to set mood. We will have one channel to
mix and another to set. This way you can define item names in some smart
way so that you can tell Alexa to “mood A mix on” or “mood A on”
What would you suggest would be best from your perspective?
Thanks
Pawel
W dniu sob., 8.12.2018 o 04:48 Daniel Mohr <notifications@github.com>
napisał(a):
… Hi,
My goal is to be able to select individual lighting moods of a Loxone
LightControllerV2 through Alexa, without mixing them in. The channels
created for the individual moods always mix them, thus when switching to
moods with fewer outputs on, I always have to say: "Alexa, Mood A off.
Alexa Mood B on". This is not convenient at all. I only want to say "Alexa,
Mood B on" and it should switch the A-only-outputs off.
To work around this I tried creating virtual switches for the individual
moods and setting the appropriate ID in the light controller Number item
through rules, when the switch is toggled. This works fine (no mixing),
except I'm not able to switch off all outputs in a rule. It seems like,
there's no ID assigned to the "Off" mood, or at least I couldn't figure out
which.
This is my LightController item:
Number Lichtsteuerung_Wohnzimmer "Lichtsteuerung Wohnzimmer" <light>
["Lighting"]
{channel="loxone:miniserver:ac681435:126F495A-0184-E9BE-FFFFB6D057327F6C"}
It shows up in Paper UI as a dropdown with the available moods, even
including the "Off" mood. Through Paper UI everything is fine, also
switching off all lights by selecting the "Off" mood.
However, in the following rule, I didn't find the appropriate value for
the "Off" mood, yet (marked with ???). Licht_Wohnzimmer_Standard is the
virtual switch.
rule "Licht Wohnzimmer Standard"
when
Item Licht_Wohnzimmer_Standard received update
then
if (Licht_Wohnzimmer_Standard.state == ON) {
sendCommand(Lichtsteuerung_Wohnzimmer, 2)
}
if (Licht_Wohnzimmer_Standard.state == OFF) {
sendCommand(Lichtsteuerung_Wohnzimmer, ???)
}
end
```
Is there a better approach for selecting individual moods without mixing them? And if not, how to switch the LightControllerV2 off through a rule?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AJx5fn-8oyhsYbBcbJP_Bs8FbHY6pSHnks5u26cEgaJpZM4ZJmf8>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
My goal is to be able to select individual lighting moods of a Loxone LightControllerV2 through Alexa, without mixing them in. The channels created for the individual moods always mix them, thus when switching to moods with fewer outputs on, I always have to say: "Alexa, Mood A off. Alexa Mood B on". This is not convenient at all. I only want to say "Alexa, Mood B on" and it should switch the A-only-outputs off.
To work around this I tried creating virtual switches for the individual moods and setting the appropriate ID in the light controller
Number
item through rules, when the switch is toggled. This works fine (no mixing), except I'm not able to switch off all outputs in a rule. It seems like, there's no ID assigned to the "Off" mood, or at least I couldn't figure out which.This is my LightController item:
Number Lichtsteuerung_Wohnzimmer "Lichtsteuerung Wohnzimmer" <light> ["Lighting"] {channel="loxone:miniserver:ac681435:126F495A-0184-E9BE-FFFFB6D057327F6C"}
It shows up in Paper UI as a dropdown with the available moods, even including the "Off" mood. Through Paper UI everything is fine, also switching off all lights by selecting the "Off" mood.
However, in the following rule, I didn't find the appropriate value for the "Off" mood, yet (marked with
???
).Licht_Wohnzimmer_Standard
is the virtual switch.Is there a better approach for selecting individual moods without mixing them? And if not, how to switch the LightControllerV2 off through a rule?
Thanks!
The text was updated successfully, but these errors were encountered: