You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -114,17 +114,6 @@ This device supports OTA updates, for more information see [OTA updates](../guid
114
114
115
115
## Exposes
116
116
117
-
### Light
118
-
This light supports the following features: `state`, `brightness`.
119
-
-`state`: To control the state publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"state": "ON"}`, `{"state": "OFF"}` or `{"state": "TOGGLE"}`. To read the state send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"state": ""}`.
120
-
-`brightness`: To control the brightness publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"brightness": VALUE}` where `VALUE` is a number between `0` and `254`. To read the brightness send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"brightness": ""}`.
121
-
122
-
#### On with timed off
123
-
When setting the state to ON, it might be possible to specify an automatic shutoff after a certain amount of time. To do this add an additional property `on_time` to the payload which is the time in seconds the state should remain on.
124
-
Additionnaly an `off_wait_time` property can be added to the payload to specify the cooldown time in seconds when the light will not answer to other on with timed off commands.
125
-
Support depend on the light firmware. Some devices might require both `on_time` and `off_wait_time` to work
Value can be found in the published state on the `ballast_minimum_level` property.
@@ -160,12 +149,51 @@ To read (`/get`) the value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME
160
149
To write (`/set`) a value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"led_if_on": NEW_VALUE}`.
161
150
If value equals `ON` led if on is ON, if `OFF` OFF.
162
151
152
+
### Light
153
+
This light supports the following features: `state`, `brightness`.
154
+
-`state`: To control the state publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"state": "ON"}`, `{"state": "OFF"}` or `{"state": "TOGGLE"}`. To read the state send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"state": ""}`.
155
+
-`brightness`: To control the brightness publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"brightness": VALUE}` where `VALUE` is a number between `0` and `254`. To read the brightness send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"brightness": ""}`.
156
+
157
+
#### On with timed off
158
+
When setting the state to ON, it might be possible to specify an automatic shutoff after a certain amount of time. To do this add an additional property `on_time` to the payload which is the time in seconds the state should remain on.
159
+
Additionnaly an `off_wait_time` property can be added to the payload to specify the cooldown time in seconds when the light will not answer to other on with timed off commands.
160
+
Support depend on the light firmware. Some devices might require both `on_time` and `off_wait_time` to work
For all of the above mentioned features it is possible to do a transition of the value over time. To do this add an additional property `transition` to the payload which is the transition time in seconds.
Instead of setting a value (e.g. brightness) directly it is also possible to:
169
+
- move: this will automatically move the value over time, to stop send value `stop` or `0`.
170
+
- step: this will increment/decrement the current value by the given one.
171
+
172
+
The direction of move and step can be either up or down, provide a negative value to move/step down, a positive value to move/step up.
173
+
To do this send a payload like below to `zigbee2mqtt/FRIENDLY_NAME/set`
174
+
175
+
**NOTE**: brightness move/step will stop at the minimum brightness and won't turn on the light when it's off. In this case use `brightness_move_onoff`/`brightness_step_onoff`
176
+
````js
177
+
{
178
+
"brightness_move":-40, // Starts moving brightness down at 40 units per second
179
+
"brightness_move":0, // Stop moving brightness
180
+
"brightness_step":40// Increases brightness by 40
181
+
}
182
+
````
183
+
184
+
### Effect (enum)
185
+
Triggers an effect on the light (e.g. make light blink for a few seconds).
186
+
Value will **not** be published in the state.
187
+
It's not possible to read (`/get`) this value.
188
+
To write (`/set`) a value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"effect": NEW_VALUE}`.
189
+
The possible values are: `blink`, `breathe`, `okay`, `channel_change`, `finish_effect`, `stop_effect`.
190
+
163
191
### Power-on behavior (enum)
164
192
Controls the behavior when the device is powered on after power loss. If you get an `UNSUPPORTED_ATTRIBUTE` error, the device does not support it..
165
193
Value can be found in the published state on the `power_on_behavior` property.
166
194
To read (`/get`) the value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"power_on_behavior": ""}`.
167
195
To write (`/set`) a value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"power_on_behavior": NEW_VALUE}`.
168
-
The possible values are: `off`, `previous`, `on`.
196
+
The possible values are: `off`, `on`, `toggle`, `previous`.
@@ -42,28 +42,6 @@ This device supports OTA updates, for more information see [OTA updates](../guid
42
42
43
43
## Exposes
44
44
45
-
### Light (left endpoint)
46
-
This light supports the following features: `state`, `brightness`.
47
-
-`state`: To control the state publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"state_left": "ON"}`, `{"state_left": "OFF"}` or `{"state_left": "TOGGLE"}`. To read the state send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"state_left": ""}`.
48
-
-`brightness`: To control the brightness publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"brightness_left": VALUE}` where `VALUE` is a number between `0` and `254`. To read the brightness send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"brightness_left": ""}`.
49
-
50
-
#### On with timed off
51
-
When setting the state to ON, it might be possible to specify an automatic shutoff after a certain amount of time. To do this add an additional property `on_time` to the payload which is the time in seconds the state should remain on.
52
-
Additionnaly an `off_wait_time` property can be added to the payload to specify the cooldown time in seconds when the light will not answer to other on with timed off commands.
53
-
Support depend on the light firmware. Some devices might require both `on_time` and `off_wait_time` to work
This light supports the following features: `state`, `brightness`.
58
-
-`state`: To control the state publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"state_right": "ON"}`, `{"state_right": "OFF"}` or `{"state_right": "TOGGLE"}`. To read the state send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"state_right": ""}`.
59
-
-`brightness`: To control the brightness publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"brightness_right": VALUE}` where `VALUE` is a number between `0` and `254`. To read the brightness send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"brightness_right": ""}`.
60
-
61
-
#### On with timed off
62
-
When setting the state to ON, it might be possible to specify an automatic shutoff after a certain amount of time. To do this add an additional property `on_time` to the payload which is the time in seconds the state should remain on.
63
-
Additionnaly an `off_wait_time` property can be added to the payload to specify the cooldown time in seconds when the light will not answer to other on with timed off commands.
64
-
Support depend on the light firmware. Some devices might require both `on_time` and `off_wait_time` to work
### Ballast minimum level (numeric, left endpoint)
68
46
Specifies the minimum brightness value.
69
47
Value can be found in the published state on the `ballast_minimum_level_left` property.
@@ -135,12 +113,83 @@ To read (`/get`) the value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME
135
113
To write (`/set`) a value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"led_if_on": NEW_VALUE}`.
136
114
If value equals `ON` led if on is ON, if `OFF` OFF.
137
115
116
+
### Light (left endpoint)
117
+
This light supports the following features: `state`, `brightness`.
118
+
-`state`: To control the state publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"state_left": "ON"}`, `{"state_left": "OFF"}` or `{"state_left": "TOGGLE"}`. To read the state send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"state_left": ""}`.
119
+
-`brightness`: To control the brightness publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"brightness_left": VALUE}` where `VALUE` is a number between `0` and `254`. To read the brightness send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"brightness_left": ""}`.
120
+
121
+
#### On with timed off
122
+
When setting the state to ON, it might be possible to specify an automatic shutoff after a certain amount of time. To do this add an additional property `on_time` to the payload which is the time in seconds the state should remain on.
123
+
Additionnaly an `off_wait_time` property can be added to the payload to specify the cooldown time in seconds when the light will not answer to other on with timed off commands.
124
+
Support depend on the light firmware. Some devices might require both `on_time` and `off_wait_time` to work
For all of the above mentioned features it is possible to do a transition of the value over time. To do this add an additional property `transition` to the payload which is the transition time in seconds.
Instead of setting a value (e.g. brightness) directly it is also possible to:
133
+
- move: this will automatically move the value over time, to stop send value `stop` or `0`.
134
+
- step: this will increment/decrement the current value by the given one.
135
+
136
+
The direction of move and step can be either up or down, provide a negative value to move/step down, a positive value to move/step up.
137
+
To do this send a payload like below to `zigbee2mqtt/FRIENDLY_NAME/set`
138
+
139
+
**NOTE**: brightness move/step will stop at the minimum brightness and won't turn on the light when it's off. In this case use `brightness_move_onoff`/`brightness_step_onoff`
140
+
````js
141
+
{
142
+
"brightness_move":-40, // Starts moving brightness down at 40 units per second
143
+
"brightness_move":0, // Stop moving brightness
144
+
"brightness_step":40// Increases brightness by 40
145
+
}
146
+
````
147
+
148
+
### Light (right endpoint)
149
+
This light supports the following features: `state`, `brightness`.
150
+
-`state`: To control the state publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"state_right": "ON"}`, `{"state_right": "OFF"}` or `{"state_right": "TOGGLE"}`. To read the state send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"state_right": ""}`.
151
+
-`brightness`: To control the brightness publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"brightness_right": VALUE}` where `VALUE` is a number between `0` and `254`. To read the brightness send a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"brightness_right": ""}`.
152
+
153
+
#### On with timed off
154
+
When setting the state to ON, it might be possible to specify an automatic shutoff after a certain amount of time. To do this add an additional property `on_time` to the payload which is the time in seconds the state should remain on.
155
+
Additionnaly an `off_wait_time` property can be added to the payload to specify the cooldown time in seconds when the light will not answer to other on with timed off commands.
156
+
Support depend on the light firmware. Some devices might require both `on_time` and `off_wait_time` to work
For all of the above mentioned features it is possible to do a transition of the value over time. To do this add an additional property `transition` to the payload which is the transition time in seconds.
Instead of setting a value (e.g. brightness) directly it is also possible to:
165
+
- move: this will automatically move the value over time, to stop send value `stop` or `0`.
166
+
- step: this will increment/decrement the current value by the given one.
167
+
168
+
The direction of move and step can be either up or down, provide a negative value to move/step down, a positive value to move/step up.
169
+
To do this send a payload like below to `zigbee2mqtt/FRIENDLY_NAME/set`
170
+
171
+
**NOTE**: brightness move/step will stop at the minimum brightness and won't turn on the light when it's off. In this case use `brightness_move_onoff`/`brightness_step_onoff`
172
+
````js
173
+
{
174
+
"brightness_move":-40, // Starts moving brightness down at 40 units per second
175
+
"brightness_move":0, // Stop moving brightness
176
+
"brightness_step":40// Increases brightness by 40
177
+
}
178
+
````
179
+
180
+
### Effect (enum)
181
+
Triggers an effect on the light (e.g. make light blink for a few seconds).
182
+
Value will **not** be published in the state.
183
+
It's not possible to read (`/get`) this value.
184
+
To write (`/set`) a value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"effect": NEW_VALUE}`.
185
+
The possible values are: `blink`, `breathe`, `okay`, `channel_change`, `finish_effect`, `stop_effect`.
186
+
138
187
### Power-on behavior (enum)
139
188
Controls the behavior when the device is powered on after power loss. If you get an `UNSUPPORTED_ATTRIBUTE` error, the device does not support it..
140
189
Value can be found in the published state on the `power_on_behavior` property.
141
190
To read (`/get`) the value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"power_on_behavior": ""}`.
142
191
To write (`/set`) a value publish a message to topic `zigbee2mqtt/FRIENDLY_NAME/set` with payload `{"power_on_behavior": NEW_VALUE}`.
143
-
The possible values are: `off`, `previous`, `on`.
192
+
The possible values are: `off`, `on`, `toggle`, `previous`.
Copy file name to clipboardexpand all lines: docs/devices/07767L.md
+51-2
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,57 @@
1
-
<!-- Notes BEGIN -->
1
+
---
2
+
title: "Immax 07767L control via MQTT"
3
+
description: "Integrate your Immax 07767L via Zigbee2MQTT with whatever smart home infrastructure you are using without the vendor's bridge or gateway."
4
+
addedAt: 2024-03-31T18:43:43
5
+
pageClass: device-page
6
+
---
7
+
8
+
<!-- !!!! -->
9
+
<!-- ATTENTION: This file is auto-generated through docgen! -->
10
+
<!-- You can only edit the "Notes"-Section between the two comment lines "Notes BEGIN" and "Notes END". -->
11
+
<!-- Do not use h1 or h2 heading within "## Notes"-Section. -->
0 commit comments