homebridge-easy-mqtt 1.4.0-beta.3 → 1.4.0-beta.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,15 +2,15 @@
2
2
 
3
3
  All notable changes to homebridge-dummy will be documented in this file.
4
4
 
5
- ## 1.4.0-beta.3 (2025-09-18)
5
+ ## 1.4.0-beta.5 (2025-09-18)
6
6
 
7
7
  ### Added
8
- - Support for HeaterCooler
9
- - Support for LightSensor
8
+ - Support for HeaterCooler, LightSensor, and Valve
10
9
 
11
10
  ### Changed
12
11
  - Optimized MQTT connections by sharing across multiple accessories when possible
13
12
  - Previously, every accessory had its own connection
13
+ - Better field validation in config UI (Thank you, [@justjam2013](https://github.com/sponsors/justjam2013) for teaching me this!)
14
14
 
15
15
  ### Fixed
16
16
  - Config UI rendering issue when migrating deprecated fields
package/README.md CHANGED
@@ -163,14 +163,14 @@ As with topics, you will also need to populate the appropriate values based on t
163
163
  - `valueContactDetected*` - Accessory has detected contact
164
164
 
165
165
  ### HumiditySensor
166
- - `topicGetCurrentRelativeHumidity` - The current relatively humidity
166
+ - `topicGetCurrentRelativeHumidity*` - The current relatively humidity
167
167
 
168
168
  #### LeakSensor
169
169
  - `topicGetLeakDetected*` - Whether or not sensor has detected a leak
170
170
  - `valueLeakDetected*` - Accessory has detected a leak
171
171
 
172
172
  #### LightSensor
173
- - `topicGetCurrentAmbientLightLevel` - The current light level in lux units
173
+ - `topicGetCurrentAmbientLightLevel*` - The current light level in lux units
174
174
 
175
175
  #### MotionSensor
176
176
  - `topicGetMotionDetected*` - Whether or not sensor has detected motion
@@ -190,14 +190,15 @@ As with topics, you will also need to populate the appropriate values based on t
190
190
 
191
191
  ### Climate Controllers
192
192
  - `temperatureUnits` - The temperature units of the incoming value supplied by the thermostat, `C` for Celsius (default) `F` for Fahrenheit
193
+ - `topicGetCurrentTemperature*` - Get the current temperature
193
194
  - `topicGetCoolingThresholdTemperature` - Get the cooling threshold temperature
194
195
  - `topicSetCoolingThresholdTemperature` - Set the cooling threshold temparture
195
196
  - `topicGetHeatingThresholdTemperature` - Get the heating threshold temperature
196
197
  - `topicSetHeatingThresholdTemperature` - Set the heating threshold temperature
197
198
 
198
199
  #### HeaterCooler
199
- - `topicGetActive*` - Get whether or not the accessory is currently active
200
- - `topicSetActive*` - Set whether or not the accessory is currently active
200
+ - `topicGetHeaterCoolerActive*` - Get whether or not the accessory is currently active
201
+ - `topicSetHeaterCoolerActive*` - Set whether or not the accessory is currently active
201
202
  - `topicGetCurrentHeaterCoolerState*` - Get the current mode (i.e. inactive, idle, heating, cooling)
202
203
  - `topicGetTargetHeaterCoolerState*` - Get the target mode (i.e. auto, heat, cool)
203
204
  - `topicSetTargetHeaterCoolerState*` - Set the target mode (i.e. auto, heat, cool)
@@ -223,7 +224,6 @@ As with topics, you will also need to populate the appropriate values based on t
223
224
  - `topicGetCurrentHeatingCoolingState*` - Get the current mode (i.e. cooling, heating, off)
224
225
  - `topicGetTargetHeatingCoolingState*` - Get the target mode (i.e. auto, cooling, heating, off)
225
226
  - `topicSetTargetHeatingCoolingState*` - Set the target mode (i.e. auto, cooling, heating, off)
226
- - `topicGetCurrentTemperature*` - Get the current temperature
227
227
  - `topicGetTargetTemperature*` - Get the target temperature
228
228
  - `topicSetTargetTemperature*` - Set the target temperature
229
229
  - `topicGetCurrentRelativeHumidity` - Get the current humidity
@@ -258,6 +258,24 @@ As with topics, you will also need to populate the appropriate values based on t
258
258
  - `valueFault` - Accessory has a fault
259
259
  - `valueTampered` - Accessory has been tampered with
260
260
 
261
+ #### Valve
262
+ - `valveType` - One of `GENERIC_VALVE` (default), `IRRIGATION`, `SHOWER_HEAD`, or `WATER_FAUCET`
263
+ - `topicGetValveActive*` - For getting whether or not the valve is active
264
+ - `topicSetValveActive*` - For setting whether or not the valve is active
265
+ - `topicGetValveInUse*` - For getting whether or not the valve is in use
266
+ - `topicGetStatusFault` - For getting whether or not there is a fault
267
+ - `topicGetValveIsConfigured` - For getting wether or not valve is configured
268
+ - `topicSetValveIsConfigured` - For setting wether or not valve is configured
269
+ - `topicGetValveSetDuration` - For getting the set duration in seconds
270
+ - `topicSetValveSetDuration` - For setting the set duration in seconds
271
+ - `topicGetValveRemainingDuration` - For getting the time remaining in seconds
272
+ - `valueActive*` - Valve is active, e.g. "true", or "1", or "active"
273
+ - `valueInactive*` - Valve is not active e.g. "false", or "0", or "active"
274
+ - `valueInUse*` - Valve is in use, e.g. "true", or "1", or "used"
275
+ - `valueConfigured` - Valve is configured, e.g. "true", or "1", or "configured"
276
+ - `valueNotConfigured` - Valve is not configured, e.g. "false", or "0", or "unconfigured"
277
+ - `valueFault` - Valve has a fault, e.g. "error", or "-1"
278
+
261
279
  ## Logging/Debugging:
262
280
 
263
281
  By default, devices will log activity, for example when a Switch is turned on or a LockMechanism is unlocked.