Settings → Version : FAQs
No, Jeedom is fully usable without any need for any subscription. However, there are services offered for backups or calls / SMS, but which are really optional.
No, Jeedom does not use “Cloud” type infrastructure”. Everything is done locally and you do not need our servers for your installation to work. Only services like Market, online backup or Jeedom DNS require the use of our servers.
Jeedom has a mobile version suitable for use on mobile and tablet. There is also a native app for Android and iOS.
When you log in to Jeedom for the first time (and even afterwards if you haven't changed them), the default username and password are admin / admin. At the first connection, you are strongly recommended to modify these identifiers for more security.
Since Jeedom 3.2 it is no longer possible to connect with admin / admin remotely for obvious security reasons. Admin / admin credentials only work locally. Attention if you go through the DNS even locally you are necessarily identified as remote. Other default point only IP on 192.168.. or 127.0.0.1 are recognized as local. It is configured in the administration of Jeedom security part then IP “white”. If, despite everything, you still cannot connect, you must use the password reset procedure, see here.
Often this is due to the fact that the equipment is assigned to an object which is not the son or the object itself of the first object selected on the left in the tree (you can configure this one in your profile).
Yes, the list of keyboard / mouse shortcuts is here.
Yes it is possible, just drag and drop the commands of your object on its configuration.
For each command you can choose its display between different Core widgets, or create one with Tools → Widgets.
No it's not possible, but you can duplicate it thanks to the virtual plugin.
It is enough, on a historical curve of the command, to click on the point in question. If you leave the field blank, then the value will be deleted.
There is no standard duration, it depends on the system and the volume of data to be backed up, but it can take more than 5 minutes, this is normal.
They are in the / var / www / html / backup folder
Yes : Either you have a power pack or more, in this case you just use the Jeedom DNS. Either with a DNS and you know how to set up a valid certificate, in this case it is a standard installation of a certificate.
Here’s one documentation, “Windows : Putty”. The "hostname" being the ip of your Jeedom, the identifiers being :
Note that when you write the password you will not see anything written on the screen, this is normal.
In SSH do :
`{.bash}
sudo su -
chmod -R 775 / var / www / html
chown -R www-data:www-data / var / www / html
‘’
In SSH do :
`{.bash}
sudo su -
php /var/www/html/install/update.php
chmod -R 775 / var / www / html
chown -R www-data:www-data / var / www / html
‘’
The webapp requires a smartphone supporting HTML5 and CSS3. It is therefore unfortunately not Symbian compatible.
For Jeedom to work, you need a linux platform with root rights or a docker type system. It therefore does not work on a pure android platform.
This can be due to several things, :
It is necessary to connect in SSH to Jeedom and launch the self-diagnostic script :
`{.bash}
sudo chmod + x / var / www / html / health.sh; sudo /var/www/html/health.sh
‘’
If there is a problem, the script will try to correct it. If it can't, it will tell you.
You can also look at the log /var/www/html/log/http.error. Very often, this indicates the concern.
These must be reset :
`{.bash}
bdd_password = $ (cat / dev / urandom | tr -cd 'a-f0-9' | head -c 15)
echo "DROP USER 'jeedom' @ 'localhost'" | mysql -uroot -p
echo "CREATE USER 'jeedom' @ 'localhost' IDENTIFIED BY '$ {bdd_password}';" | mysql -uroot -p
echo "GRANT ALL PRIVILEGES ON jeedom.* TO 'jeedom' @ 'localhost';" | mysql -uroot -p
cd / usr / share / nginx / www / jeedom
sudo cp core / config / common.config.sample.php core / config / common.config.php
sudo sed -i -e "s /#PASSWORD#/ $ {bdd_password} / g "core / config / common.config.php
sudo chown www-data:www-data core / config / common.config.php
‘’
The most frequent cause is the use of a plugin in beta version and Jeedom in stable, or the reverse. To get the details of the error, you have to look at the http log.error (in / var / www / html / log).
Again this is often due to a plugin in beta while Jeedom is in stable. To see the error, you must do F12 then console.
This error is not due to Jeedom, but to a problem with the system. If this persists following a reinstallation, it is advisable to check with the after-sales service for hardware concerns. Here is documentation for Smart
It is advisable to look at the commands executed by the scenario, often it comes from a command that does not end.
Check if your file system is not corrupt, in SSH the command is : ''sudo dmesg | grep error ‘’.
This is due to MySQL which stopped, it is not normal, the common cases are :
Unfortunately, there is not much solution if it is the second case, the best being to recover a backup (available in / var / www / html / backup by default), reinstall Jeedom and restore the backup. You can also see why MySQL doesn't want to boot from an SSH console :
`{.bash}
sudo su -
mysql stop service
mysqld --verbose
‘’
Or consult the log : /var/log/mysql/error.log
On a DIY installation it's normal. In SSH, you must make the visudo command and at the end of the file you must add : www-data ALL = (ALL) NOPASSWD: ALL.
`{.bash}
sudo service apache2 restart
‘’
This kind of case happens if your Jeedom is not compatible with the plugin. In general, a Jeedom update fixes the problem.
Alerts are ranked by priority, from the least important to the most important : timeout, battery warning, battery danger, warning alert, danger alert
If you are in DIY and under Debian 9 or more, check that there has not been an update of Apache and therefore the return of privateTmp (visible by doing ls / tmp and see if there is a private * Apache folder). If that's the case, you have to do :
''
mkdir /etc/systemd/system/apache2.service.d
echo "[Service]"> /etc/systemd/system/apache2.service.d/privatetmp.conf
echo "PrivateTmp = no" >> /etc/systemd/system/apache2.service.d/privatetmp.conf
‘’
Try to clear the chrome cache, the display of histories is calculated relative to the browser time.
Jeedom can't find or can't ping the gateway. In general it happens if the adsl box restarts (in particular liveboxes) and Jeedom has not restarted or has restarted faster than the box. For security he tells you that he has found a problem and relaunches the network connection process. You can deactivate this mechanism by going to the Jeedom configuration and by deactivating the network management by Jeedom.
It means that Jeedom cannot back up the database which can suggest a problem with database and filesystem corruption. There is unfortunately no miracle command to correct. The best is to launch a backup and analyze the log of it. In known cases of concerns we have:
It is a fairly serious error, the simplest is to make
''
mkdir -p / root / tmp /
cd / root / tmp
wget https://github.com/jeedom/core/archive/master.zip
unzip master.zip
cp -R / root / tmp / core-master / * / var / www / html
rm -rf / root / tmp / core-master
‘’
In the administration of Jeedom part OS / DB then in the system console it is necessary to make :
''
yes | sudo apt install -y php-mysql php-curl php-gd php-imap php-xml php-opcache php-soap php-xmlrpc php-common php-dev php-zip php-ssh2 php-mbstring php-ldap
‘’
It is necessary :
It is necessary in the system console of Jeedom or in ssh to make
''
sudo easy_install pip
sudo easy_install3 pip
''
Then relaunch the dependencies
Core 4.2 greatly enhances Jeedom’s security. If you really (knowingly) need to revert to an insecure version of your Jeedom : Go to Settings -> System -> Configuration then in OS / DB, launch the system administration console and click Apache not secure. A restart of Jeedom is recommended following this change.
This is due to the security of Apache which requires plugin developers to put the right files in the right directories to limit Jeedom’s attack surface. This security is done in the file .htaccess (overwritten each time the core is updated). You can make a file .htaccess_custom with your own rules which if it exists will be used instead of the file .htaccess from Core.
