Plug-in to retrieve Mobile Alerts data from compatible Lacrosse sensors.
! Attention, before purchase, you need either a kit with MA10001 gateway, or if you have the gateway, compatible sensors, check the compatibility page on the Mobile Alerts page ! You can also find them on the Lacrosse page in the "Connected Objects" menu *
Note: The plugin is used to install the script and one type of sensor at a time! examples:
The novelty is the joint creation, with the "24 hours slippery" sensor, of a "cumulative" rain sensor allowing compatibility with the "pluviomètre" plugin from JMVong (Store).
If you want to keep the Eedomus history of the "24 hours slippery" sensor, install the rain gauge with another name and delete the new "24 hours slippery" sensor, otherwise, remove the old one before installation.
NB: the "pluviomètre" plugin starts at 0 and does not take into account the Eedomus "24 hours slippery" history, nor the Mobile Alerts history.
** Installation chapter **
You are advised to read the prerequisites before going to the Installation Chapter
The Master Sensor
The "Cache Time" Master Sensor is the "parent" of all Mobile Alerts devices. They are therefore grouped into channels and have in common the parameters Var [1,2 & 3] and Polling (chapter Group). This Master Sensor will tell you the name of the sensor that last called the Mobile Alerts server and the time of this call: the other sensors using the cache. There is an English presentation in the installation choice !
Warning: before deleting a device, unassociate it (Attach to) otherwise you will delete all the devices in the parent/child group.
We will find, on Amazon or mainly in Germany, the same products under the TechnoLine - Mobile Alerts brands with the same references & TFA Dostmann (which produces the shell for outdoor thermometer of article MA10250) WEATHERHUB SmartHome.
For the usefulness of the gateway, the advantages of Lacrosse / Techno-Line / Conrad Connect sensors, their references, see the links provided (Mobile Alerts - Lacrosse - Discussion of the script in the Eedomus forum).
The plugin only offers the creation of one type of device at a time including for the Master Sensor which is only to be installed once and only once! (chapter Installation). Once a device of a given type has been created and its configuration completed and saved, you will have to duplicate it to install another of the same type to fill in only the personalized information concerning the latter: name, part, XPath and leave it rest of the information as is.
This is why at installation, only the value of the cache duration is requested, which will have an impact on the creation of the request frequency. Attention, it is always necessary to inform this value when creating a peripheral, contrary to the ID which will be in all cases taken over that of the Master Sensor (you can leave at 000 ... once the Master Sensor created).
You can, before purchase, see an example of HTML data by going to the page of Luc Trullemans, an exceptional meteorologist (RTL, expeditions, Solar Impulse ...) now retired, in the Observation menu (the first Huppertzberg link is a Mobile Alerts link).
You can also install the smartphone app and add the following test sensors:
|Air quality monitor||050809F04EE6|
You have a Mobile Alerts gateway and at least one compatible sensor or control unit:
the default units at installation are:
To view other units:
You must change them in the "Settings" tab of the Smartphone App, then you will indicate this in "Unit" of the configuration of the sensor concerned.
The configuration window will appear, indicate the following values:
Complete the configuration:
The "Cache Time" Master Sensor contains the name of the calling device and will be used to create the group of Mobile Alerts Sensors which will all be considered as channels of this Master Sensor, each modification of a single sensor on VAR (1 to 3) and Polling (which must always be equal to VAR2) will be passed on to all the others, to satisfy the requirement of identical data (see explanations on the cache), the sensors will therefore all have to be attached to the Master Sensor (Expert Parameters). You can change the name of the Master Sensor (default: "Cache Time"), but not its XPath!
The cache makes it possible to interrogate only one sensor to recover all of the data (this sensor and the update time are indicated in the Master Sensor), the other sensors, in the interval between the duration of the cache, interrogate the latter. NB: in the event of an acquisition error, during the query to the server, the duration of the cache is immediately increased by the current duration of the cache: all the other sensors will read the cache, unchanged, until the next acquisition . This significantly reduces error notifications, and alleviates the load on the server during return to service.
At installation, you have these choices of description of the compass (16 directions)
Please note, these are descriptions, not values, the value will always be International.
To locate the desired value, then the Tags that frame it:
// tag(usually predetermined)
// Name of sensor / tag
Do not change the Master Sensor predefined XPath.
These devices are the most suitable for weather data, extreme temperatures (-40 ° C + 60 ° C), battery savings and are 868 Mz (500mw) therefore having a theoretical range of 100 meters. They also benefit from a relatively low cost (including gateway). This plugin which takes up the script published on the eedomus forum was inspired by a publication (published in 2017) on the Jeedom forum and the basis for its programming was carried out by merguez07. All updates are from thrymartin.