Found indeed. Thanks.

_d.initialize('ap_table') -- Re-initialize the table
This was OK in my script ('ap-table') but the line was commented out.
Now it isn't anymore. Let's see .......

Got it all working. Very good work! There were 2 things: 1. I'm running on the latest Beta of Domoticz. Ever since mid december this is not working in the Beta: local lat = dz.settings.location.latitude local long = dz.settings.location.longitude Gives two times a zero! So I added right below: lat ...

Still waiting for someone who knows how to configure an EW11a correct so I can use TCP instead of serial.
Willem

Problem with disk-usage growing fast is solved with upgrade to Domoticz 2024-4
So it wasn't a problem of the plugin!!
Willem

Plugin is working now. Via serial.
But there is a serious problem.
The docker Domoticz container is growing in size very fast.
Only when I activate the plugin in hardware.
In a few hours the SD is full and everything stops working on my RPi.

Plugin installed OK. Got a great number of devices in Domoticz. But no real data in them. Anyone any idea about correct connecting to an Elfin EW-11? Thats the device connected to the SPRSUN and connected to 'my home WiFi and sending data to SPRSUN. Data that shows up OK in the app of SPRSUN. The EW ...

Thanks again for this part. Will add it to my knowledge base. For the part of switch (above) I decided to talk MQTT directly (because it's also MQTT-enabled) to it. And not in the strange way via domoticz/out of my other Domoticz. So now I have functioning: "TestShellyPlug": { "topic": "shellies ...

Thanks for your explanation. I understand the misconcept I tried to build (sending to domoticz/out). So I have to build something else. But still .... if I only want to read (and see) the status of the remote switch ..... "5.2 TestShellyPlug": { "topic": "domoticz/out/5.2 TestShellyPlug", "type ...

I'am trying to get a switch in a remote domoticz install to function via MQTT in an other domoticz install. So listening to the remote MQTT-messages I get these 2 json's when I switch off and on in the remote .... ============================================ { "Battery": 255, "LastUpdate": "2023-08 ...

Solution found.
ZRC-90EU has to wake up before it can properly be interviewed by ZWAVE-JS-UI.

So: press button W in the battery compartment and do a re-interview of the device.

Solved.

Forgot to add:
ZRC-90EU worked OK in OpenZwave.

I migrated from OpenZwave to Zwave-Js-UI. Using AEON Labs ZStick Gen5. Managed to get things up and running for my 8 Eurotronics Spirit Zwave Valves. Stick and Spirits detected OK. Working OK. Not the ZRC-90EU multiswitch! -- Unknown product 0xXXXX -- Buttons 1-time, 2-times and long are detected in ...

Confirm. Works! Thanks.
So ~0 is third item of svalue in DZ?
As expected by this device in DZ?

Willem

Confirm. Works! Thanks.
So ~0 is third item of svalue in DZ?
As expected by this device in DZ?

In that case both of my problems are solved.
Confirmd.
See above .....

Willem

No. Doesn't work. Alas.
Of cause it's possible to do things like this in Node Red.
But nice thing of this plugin is that maybe we can do things like this without Node Red.
I'am afraid it takes some programming effort to add this functionality.
But maybe .....
Willem

But the JSON is not flat. So I need something like: "mapping": {"item": "AM2301/Temperature;AM2301/Humidity"} to adress the values properly. I have this in domoticz log as error: 2023-07-20 00:06:16.904 Error: MQTT mapper: Can't find >Temperature< in >{'Time': '2023-07-19T23:06:16', 'AM2301 ...

What to do in mapping if the JSON read from the topic is hierachic? Like this one: { "Time": "2023-07-19T22:10:16", "AM2301": { "Temperature": 24.5, "Humidity": 77.1, "DewPoint": 20.2 }, "TempUnit": "C" }

I have to correct. The device icon doesn't show data. But the device log does! Strange.
Willem

Still playing around with this plugin. version 1.0.13 Got some created devices working in DZ. But: Found a problem. Or maybe I'am doing things wrong. It has to do with a payload in JSON format and using 2 values from that in one device ... See part of JSON-file Working: "Minisensor-1H": { "topic ...