- Ability to make table columns resizable (only the list of variables for the moment, this will be extended to other tables if necessary)) LINK
- Added an alert if jeedom disk space is too low (the check is done once a day) LINK
- Added a button to the order configuration window at the value calculation field to fetch an order LINK
- Ability to hide certain menus for users with limited rights LINK
- Charts update automatically when new values arrive LINK
- Jeedom automatically adds the height of the image when creating widgets to avoid overlapping issues on mobile LINK
- Redesign of the cloud backup part LINK
- DEV Setting up a queue system for executing actions LINK
- Scenario tags are now specific to the scenario instance (if you have two scenario launches very close together, the tags of the last one no longer overwrite the first one)) LINK
- Change to the trigger part of the scenarios : LINK
triggerId() is now deprecated and will be removed in future core updates. If you have triggerId() == 587 it must be replaced by #trigger_id# == 587triggerValue() is now deprecated and will be removed in future core updates. If you have triggerValue() == 10 it must be replaced by #trigger_value# == 10#trigger# : Maybe :
api if the launch was triggered by the API,TYPEcmd if the launch was triggered by a command, with TYPE replaced by the plugin id (eg virtualCmd),schedule if it was launched by programming,user if it was started manually,start for a launch at Jeedom startup.
#trigger_id# : If it is a command that triggered the scenario then this tag takes the value of the id of the command that triggered it#trigger_name# : If it is a command that triggered the scenario then this tag takes the value of the name of the command (in the form [object][equipment][command])#trigger_value# : If it is a command that triggered the scenario then this tag takes the value of the command that triggered the scenario#trigger_message# : Message indicating the origin of the scenario launch
- Improved plugin management on github (no more dependencies on a third-party library) LINK
- Removing the old cache system. LINK
- Possibility of deleting the IN and A blocks pending another scenario LINK
- Fixed a bug in Safari on filters with accents LINK
- Fixed bug on information generation generic type in the scenarios LINK
- Added confirmation when opening support access from the user management page LINK
- Improved cron system to avoid some launch glitches LINK
- Added in the condition wizard of the scenarios of the conditions greater than or equal to And less than or equal to LINK
- Ability to exclude orders from dead order analysis LINK
- Fixed a bug on numbering of the number of rows of tables LINK
- Added openstreetmap.org in external domains allowed by default LINK
- Automatically update apache security file when updating core LINK
- Fixed a warning on views LINK
- Fixed bug on default widget select value LINK
- Fixed a bug if a command exceeded its min or max the value would go to 0 (instead of min/max) LINK
- Fixed a bug with the settings menu displaying in some languages LINK
- Possibility in the programmed triggers of the scenarios to use calculations/commands/tags/formulas giving as a result the launch time in the form Gi (hours without initial zero and minutes, example for 09:15 => 915 or for 23:40 => 2340) LINK
- Ability to put a custom image for equipment in plugins (if the plugin supports it), this is done in the advanced configuration of the equipment LINK LINK
- Added the name of the user who launched the scenario in the tag
#trigger_value# LINK
- Fixed an error that could occur when exiting the dashboard before it had finished loading LINK
- Fixed a bug on the replacement page when filtering on objects LINK
- Improved opening of the core changelog under ios (no longer in a popup)) LINK
- Improved advanced widget creation window LINK
- Improved advanced command configuration window LINK
- Fixed bug on widget creation LINK
- Fixed a bug on the scenario page and the add actions window that could no longer work LINK
- Fixed a bug that could change the order of commands when editing the dashboard LINK
- Fixed a javascript error on histories LINK
- Added security on json encoding in ajax to avoid errors due to invalid characters LINK
- If a command of a device is of generic type “Battery” and has unit “%” then the core will automatically assign the battery level of the device to the value of the command LINK
- Improving texts and correcting mistakes LINK
- When installing npm dependencies the cache is cleaned before LINK
- Fixed a bug on 3D plans that could completely block the configuration LINK
- Fixed a bug on the history display window LINK
- Ability to choose Apache listening port in docker mode LINK
- Fixed a warning when saving to the event table LINK
- Added display name for objects LINK
- Added a button to delete timeline history and events in the future LINK
- Fixed an issue with select type commands in designs LINK
- Possibility to indicate that a piece of equipment has no battery (in case of poor feedback)) LINK
- Rework of writing in logs, removal of the monolog library (note that the option to send logs in syslog is no longer available at the moment, if demand is high we will see about putting it back) LINK
- Better management of plugin sub-log log level LINK
- Removed vendor folder (using composer normally), reduces core size LINK
- Widget specific settings can now be translated LINK
- Fixed a bug on mac on designs when right clicking LINK
- Improved the system for launching programmed scenarios LINK
- Improved exception error messages if log level is debug LINK
- On the replacement page, it is possible to request the deactivation of the equipment LINK
- When updating, the backup before now takes into account plugin exclusions LINK
- If a plugin is in beta but does not have a beta changelog then the update center will link to the stable changelog LINK
- Added alert if debian version is 10 or lower LINK
- Fix DB update error on cache table LINK
- If the equipment page has an img_device element (img type tag) then the core can itself configure the url to display the correct equipment image (using the one from the presentation page of all the plugin’s equipment) LINK
- Fixed bug with time_diff function LINK
- Bug fix on composer dependency management LINK
- In case of empty command Jeedom forces the return according to the subtype of the command (therefore 0 for numeric and binary) LINK
- Support for custom events of type #pluginClass::*# Or #pluginClass::customId# LINK
- Added an update button on the “core” line in addition to the one on the top right LINK
- Fixed “package” screen at python2 packages level LINK
- Fixed a bug when updating equipment on the battery page LINK
- La vérification de la connexion réseau est désormais effectuée de manière aléatoire toutes les 10 minutes afin d’éviter que toutes les box Jeedom ne tentent de se reconnecter simultanément en cas de microcoupure.
IMPORTANT
Due to the rework of logs and the re-internalization of libraries, when updating you may have an error type PHP Fatal error (nothing serious) just restart the update.
IMPORTANT
Restoring a backup 4.4 may in some cases end up with errors in the web interface. Rien de grave cela peut facilement se corriger il suffit de faire : cd /tmp;wgAnd https://github.com/jeedom/core/archive/refs/tags/4.4.19.zip;unzip 4.4.19.zip;cd core-4.4.19;cp -rf * /var/www/html/;rm -rf /tmp/master.zip;rm -rf /tmp/core-4.4.19;. You can launch this command from the jeedom rescue interface (add &rescue=1 in the url), or directly in ssh.
