No, Jeedom is fully usable without any need for any subscription whatsoever. However, there are services offered for backups or calls / SMS, but which actually remain optionnels.
No, Jeedom does not use “Cloud” type infrastructure”. Everything is done in local and you don't need our servers for your installation works. Only services like the Market, the online backup or Jeedom DNS require the use of our serveurs.
Yes it is possible, just drag and drop your orders object on its configuration.
Yes it is possible, either by going through the widget plugin, or by using the General → Display page
No it is not possible, but you can duplicate it thanks to the virtual plugin.
It is enough, on a historical curve of the order, 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 may take more than 5 minutes, that’s normal.
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 do not haven't changed), default username and password are admin / admin. At the first connection, you are strongly recommended to modify these identifiers for more security.
Yes : Either you have a power pack or more, in this case you just use the DNS Jeedom. 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 it's normal.
In SSH do :
`{.bash}
sudo su -
chmod -R 775 / var / www / html
chown -R www-data:www-data / var / www / html
‘’
They are in the / var / www / html / backup folder
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 the rights root 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 :
You have to connect in SSH to Jeedom and launch the script self-diagnosis :
`{.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 he can't no, it will tell you.
You can also look at the log /var/www/html/log/http.error. Very often this indicates 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 common cause is the use of a beta plugin and Jeedom in stable, or vice versa. To have the detail of the error, it must look at the http log.error (in / var / www / html / log).
Again this is often due to a beta plugin 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 it persists following a reinstallation, it is advisable to see with the after-sales service for a hardware concern. Here is Documentation for Smart
It is advisable to look at the commands executed by the scenario, often this comes from an order that does not end.
Check if your file system is not corrupt, in SSH the command is : “sudo dmesg | grep error” .
Often this is due to the fact that the equipment is assigned to an object which is not the child or the object itself of the first object selected at left in the tree (you can configure it in your profile).
This is due to MySQL which stopped, it is not normal, the cases currents are :
Lack of space on the file system (can be checked by doing the command “df -h”, in SSH)
File (s) corruption issue, which often happens due to Jeedom’s non-clean shutdown (power failure)
Memory worries, the system lacks memory and kills the most consuming process (often the database). This can be seen in the OS administration then dmesg, you should see a kill by “oom”. If this is the case, reduce the consumption of jeedom by deactivating plugins.
Unfortunately, there is not much solution if it is the second case, the best is to recover a backup (available in / var / www / html / backup by default), reinstall Jeedom and to restore the backup. You can also see why MySQL is not not 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 have to order visudo and at the end of the file you have to 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.
The alerts are classified 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 it is the case it is necessary 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 empty the chrome cache, the history display is calculated relative to the browser time.
Jeedom can't find or ping the gateway. In general it happens if the adsl box restarts (in particular liveboxes) and Jeeodm 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
Since Jeedom 3.2 it is no longer possible to connect with admin / admin remotely for obvious security reasons. The admin / admin identifiers 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 all that you still cannot connect you must use the password reset procedure (see in the tutorials / how to)
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
‘’
It is necessary :
