NetatmoSecurity

Ch. Damsky

Connection of the devices that are summarized by Netatmo under the term "Security":

  • Outdoor camera ("Outdoor" or "Presence")
  • Indoor camera ("Indoor" or "Welcome")
  • Video doorbell
  • Smoke detector
  • Carbon monoxide detector
    Note: there is no implementation for the smoke detector yet due to a lack of testing opportunities.

Depending on the product type, the module includes the following functions:

  • Calling up the status
  • Storage of events for a definable period of time
  • Receiving messages from WebHook
  • Determination of URLs for retrieving videos and snapshots (live and historical)
  • Integration of videos optionally transferred from Netatmo via FTP
  • Control (camera off/on, light)

Included Modules

  • NetatmoSecurity Kamera
  • NetatmoSecurity Konfigurator
  • NetatmoSecurity Melder
  • NetatmoSecurity I/O
  • NetatmoSecurity Person

Version History

  • 1.48.1 @ 04.08.2025 11:03

    • Fix: old hostname ‘app.netatmo.net’ overlooked (addendum to v1.48)

  • 1.48 @ 17.07.2025 11:16

    • Change: API servers have been changed (api.netatmo.net -> api.netatmo.com)
    • Improvement: Handling of the local URL, especially if the camera does not have a local IP address

  • 1.47 @ 12.04.2025 11:42

    • Improvement: a failed HTTP request due to the server not being available is repeated several times.
      The timeout of the request and the number of attempts and the delay between attempts can now be set.
      Attention: Note the information about these settings in the README.md

  • 1.46 @ 16.03.2025 09:21

    • Improvement: Checking the IP of the camera reported by Netatmo as the local address against the specified “local CIDR's”.
      Background: when the camera is restarted, a local IP address is sometimes recorded in the Netatmo cloud (typically 169.254.190.x for me), but this is not the local address of the camera.
      As a result, the module tries to get images (e.g. for the timeline) from this address, which fails with a timeout. This can cause a long-running thread.
      In case of doubt, the images are now fetched via the “vpn_url”.

  • 1.45 @ 03.01.2025 14:17

    • internal changes

  • 1.44 @ 23.10.2024 17:06

    • Change: after omission of the password-based login (see v1.38) a login via OAuth login is now possible; the manual entry of the "RefreshToken" is no longer necessary if Symcon-Connect is active.

  • 1.43 @ 01.08.2024 14:28

    • Change: after omission of the password-based login (see v1.38) now the configuration of user ID and password cleaned up

  • 1.42.2 @ 21.02.2024 11:07

    • Fix: Securing access to the content of media objects
    • Fix: Access to media object 'Person' adjusted again

  • 1.42.1 @ 16.02.2024 17:34

    • Fix: Access to media objects was still partly by name

  • 1.42 @ 07.02.2024 17:59

    • Fix: Securing access to other instances in configurators

  • 1.41 @ 29.01.2024 11:11

    • Change: Media objects now also have an ident for unique identification

  • 1.40 @ 25.01.2024 15:23

    • New: Switch to collect data on API calls
      The API call data is now available in a media object

The complete version history can be found in the documentation

To Documentation

Author: Ch. Damsky

IP-Symcon >= 6.2

Version: 1.48.1

In Categories:

Any questions?