New plugin pimatic-mesh

---

@thrusty thanks for the info.
Just checking what you posted.
The device on the remote pimatic has the id ‘my-sensor’ ?
And your remote pimatic is called ‘pimatic’ in the plugin config ?

Could you also post the variable from the variables overview in the remote pimatic.
If what you posted is right the variable should be $my-sensor.lx

I noticed something else. I took a Sonoff 4CH with a BME280 over DeviceDiscover for testing. The device didn’t show me any values, and I only see the placeholders for humidity and temperature. For pressure it doesn’t show me a placeholder.
The automatically transferred device:

{
      "class": "PimaticMeshTemperatures",
      "name": "[pimatic] 4CH Sensor",
      "id": "_pimatic_4ch-sensor"
      "remotePimatic": "pimatic",
      "remoteDeviceId": "4ch-sensor"
      "xAttributeOptions": []
    }

The MeshTemperature only maps temperature and humidity. But i can add pressure.
Im also adding device device discovery for all the variables of a remote pimatic.
That seems handy.

I added the variables discovery in version 0.1.11.
That should make all devices with their variables visible in the discovery.
If you do a discovery you should also see the 4ch-sensor as a MeshVariablesDevice with all attributes (incl pressure).
You can add and use that device and remove the MeshTemperatures device.

Really very beautiful. You got it, all readings are on the board. Thank you for your efforts.
The list when running DiscoverDevices is now almost endless.

And on the picture…
The topmost device is the Sonoff with the BH1750 direct from device via mqtt.
The second is the outdoor sensor (BH1750) via pimatic-mesh.
The third is the same sensor over mqtt (the difference is because the rule only checks every 30 seconds)
The fourth is the Sonoff with the BME280 via pimatic-mesh.

Even the water level sensor (HC-SR04, distance sensor) is displayed. (Sits on a rainwater tank, 1000l, at the moment empty of course)

Very nice 😄

Hi, as many other plugins from you I am using this as well this one. I am missing only one thing in my environment. It is the xConfirm function for switches. It would be nice if you can simply take over the config from the source switch. But a xConfirm function in the mesh device itself would do the job as well. What you think?

If it is not much effort it could be helpful to have button devices available as well.

Hello, I added the xConfirm to the MeshSwitch. It’s independent from the remote setting.
If you use the discover and add devices that way, the config of the remote device will be used (incl xConfirm, etc)
Also added the buttons device. The ‘enableActiveButton’ option is also independent from the remote setting. Only after adding via the discovery the actual remote value is used.
The version is 0.2.0

Thx for that and as usual extremely fast!

The discovery function does not work for me somehow. It is not that important for me, but is there a trick? I can already control mesh devices I add manually, but when I use the discovery many devices gets find, but no remote mesh device…

there’s no trick. do you see ‘pimatic-mesh, Searching for devices’ in the toplist of the device page after pressing ‘discover devices’ ?
And it takes some time depending on the size of the remote pimatic.

Yes there is a entry with mesh. But I found as well this in the log
Could not initialize the plugin "mesh": Cannot find module './devices/pimatic-mesh-buttons'

Could it be a problem when the ID of the remote pimatic has a @ in its name? Like pimatic@raspberry?

thats right, I forgot to add this file in the package => version 0.2.1

I’m not sure if the @ causes problems, but you can create an id with a @ in it, it should be ok.

To start freshly I delete all the mesh stuff and reinstalled the plugin. The log shows me now
error [pimatic-mesh]: [PimaticMeshConnection] connection attempt 1 to remote 'homation-gateway' failed

This is the config:

I changed the ID (no more @). Could the port (:1234) be a problem?

Hi, just use the ip number, no port. And did you set the username and password for this pi?

Username and password are set. The port is configured this way in the remote config and the api is reachable only this way. There is nothing on default port :80. But I will try…

Here the result without the port.

The message comes every 5 seconds.

Before it came once.

i’m using websockets and do not configure the port. So its using port 80.

Okay, then I have no discovery function I am fine wit this. As long as I can operate the remote devices is perfect and this works even with the port in the url.

Yes, but when the mesh works the api works and the discovery also.
They all use the same api.
The whole url (incl port) is used to create a connection. So your port can work

Is there a time limit how long the search is active? Because the Harmony plugin takes log time for searching an the list of it is huge.

The discovery ‘timer’ is default 20 seconds. But its not a timer but just a value (20000).
In the mesh plugin, the start of the discovery ‘timer’ is used to start the sync with the remotes. In my config it takes 1 minute get/prepare all the devices/variables (232/612). All this info is shown in the discovery result (for my remote 400+ lines with devices and variables!)
I don’t know how the harmony plugin is handling this. But all should go in parallel and finish at some moment (a few minutes?)