fritzbox.html 3.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  2. <html xmlns="http://www.w3.org/1999/xhtml">
  3. <head>
  4. <title>fhem on the Fritz!Box</title>
  5. <script type="text/javascript" src="fhemdoc.js"></script>
  6. <noscript>
  7. <link rel="stylesheet" type="text/css" href="../www/pgm2/style.css" />
  8. </noscript>
  9. <meta http-equiv="Content-type" content="text/html;charset=ISO-8859-1"/>
  10. </head>
  11. <body>
  12. <div id="menuScrollArea">
  13. <div id="logo"></div>
  14. <div id="menu">
  15. <h3>Fhem on the Fritz!Box</h3>
  16. </div>
  17. </div>
  18. <div id="right">
  19. <h2><a href="fhem.html">FHEM</a> on the Fritz!Box</h2>
  20. <b>
  21. As of Fritz!OS 6.20 AVM decided to remove all possibilities to start
  22. "foreign" programs automatically after a reboot, that is why
  23. I advise against deploying FHEM on the Fritz!BOX, see also <a
  24. href="http://forum.fhem.de/index.php?topic=25066.0">this</a> discussion
  25. (in german).
  26. </b>
  27. <h3>Fritz!Box 7390 / 7490</h3>
  28. <ul>
  29. After the CeBIT 2011 AVM released an image for the Fritz!Box7390 containing
  30. fhem, see <a href="http://www.avm.de/de/Service/Service-Portale/Labor/index.php"
  31. >this</a> link. This image is to be installed in <b>addition</b> to the
  32. normal firmware. You can upgrade/replace the normal firmware any time
  33. without hurting the fhem installation and vice versa. This fhem
  34. installation configures 2 CUL devices, the first one talking FS20
  35. ("SlowRF"), the second preconfigured for HomeMatic. <br><br>
  36. The AVM installation will start fhem in a chroot environment, in order to
  37. minimize security concerns, but this also prevents fhem to trigger
  38. arbitrary FritzBox functions, e.g. sending mail, enabling WLAN, etc. wont
  39. be possible from fhem.<br><br>
  40. <a href="fhem-5.8-fb7390.image">This</a> image from fhem.de contains
  41. perl from the AVM fhem-image and of course fhem, the main difference is,
  42. that fhem will be started in a normal (non-chroot) environment.
  43. When installing it, you have to confirm with an extra click that it does
  44. not have a valid AVM signature. </ul>
  45. <h3>Fritz!Box 7170/7270 (as of 2011-09-03)</h3>
  46. <ul>
  47. Due to Eyk's work there is also a <a
  48. href="fhem-5.8-fb7270.zip">ZIP</a> file for the Fritz!Box 7170 and 7270
  49. models. As the FB720/7170 has not enough internal storage to install fhem,
  50. you have to use an external USB Drive:
  51. <ul>
  52. <li>First unzip the .ZIP file in the root directory of the USB-disk/USB-stick.
  53. <li>Attach the stick to the FB
  54. <li>open a telnet window, connect to the FB.
  55. <li>With the command df check the name of the stick on the FB.
  56. <li>Execute the following command in the FB telnet window to start fhem
  57. when the FB reboots:<br>
  58. echo "&lt;path-of-the-stick&gt;/fhem/startfhem" > /var/flash/debug.cfg
  59. <li>Start fhem manually with "&lt;path-of-the-stick&gt;/fhem/startfhem"
  60. </ul>
  61. Since these devices have less memory than the FB7390, fhem may suffer from
  62. memory-shortage, esp. inspecting large logs directly in the browser my lead
  63. to a reboot.
  64. </ul>
  65. </div>
  66. </body>
  67. </html>