- Updated icons
- New homeeLogNode: Query the logfile from your homee and select between three different output formats.
- Bugfix: Infinity and NaN are now not longer valid id or values when sending a message to a homee device
- Current and target value can now be set seperately from each other.
- The access token of your virtual homee can now be renewed from the Node-RED editor.
- Some input fields have been replaced by typed inputs to allow the use of environment variables. Thus, subflows can now be used for device definition.
- In the Api Node it is now possible to filter for messages about plans and homeegrams. In addition, plans and homeegrams are now also stored in the global context if configured.
- Bugfix for Node-RED >= v. 1.3.0
- Since version 2.31.0 homee allows only one connection per device. For the use of multiple Node-RED instances, a unique device name can now be specified.
- Attributes can now be sorted. Ids will be automatically adjusted when sorting.
- Added
name
param to new attributes. - Validation for instances on attributes with the same type
- The
data
attribute can now be updated without specifying avalue
. - The attribute type can now be set individually using the expert mode.
- Removed deprecated syntax for changing attributes
- Fixed some typos
- Fixed broken api urls when node-red does not run at root path
- Disabled export of the homee-api configuration node
- Added german translation
- homeeApi node: added filter options for outgoing messages
- homeeDevice node: allow a custom template for the nodes status text
- homeeDevice node: New attribute list for easier attribute definition
- homeeDevice node: Attribute templates
- Fixed: For attribute types FirmwareRevision, SoftwareRevision and DeviceProgramm the data attribute is used instead of the current value.
- fixed icon size and switched from png to svg
- homeeApi node: Changed icon for configuration node
- Added relationships (node <--> group) to global context
- Added option to disable the distribution to the global context
- Add option to change data in device-attribute (PR #10)
- Bugfix: Prevent crashing due missing contextStorage configuration
- catch invalid units in attributes (#9)
- store and load attribute data only if the
homeeStore
is configured - wait until the context is set before closing the node
- readded
data
key to attributes since this affects the status shown in homee - fixed
last_value
- Added Changelog. All notable changes to this project will be documented in this file
- Messages for updating an attribute value can now be arrays. This allows multiple attribute values to be changed at once.
- Optionally persist attribute values in a new homeeStore. Locale file system must be enabled in
settings.js
- Option to display the Node-ID at the title of the node
- The node status now shows the current values of its attributes instead of
registered
- Messages are not longer ignored if they are sent within 10 seconds
- Shortened the virtual homee label at the device configuration page
- Removed
data
from attribute update messages to prevent changes during runtime