https://github.com/domoticz/domoticz/pull/5034

I'll test it as soon as the update is available.
Thanks Kiddigital!

@Jeroenkl , the group should be called ‘accel’ as that is the type that the module is looking for. But it will give you a surprise :) @kiddigital, I changed it: "accel": [ "accelerometer_3" ], 2021-11-28 12:44:48.288 Error: TESTv3MQTT client gateway Wisblocks: Error parsing message (Type is not con ...

Hi @kiddigital, I need some help as I got for the device below the log error message: 2021-11-28 08:48:48.277 Error: TESTv3MQTT client gateway Wisblocks: Error parsing message (Type is not convertible to string)!!! For device: "decoded_payload": { "accelerometer_3": { "x": 0.064, "y": -0.032, "z ...

Yes that is correct. And you should see in the logging a status message telling you that the aliasses file is found and used (or not). And in this file tou can add “temperature_2” as an entry under ‘temp’. Works! Thanks! { "temp": [ "temperature", "ambient_temperature", "temperature_2" ],

Domoticz root directory… If not (it should), you could create it your self. See GitHub repo (Beta). I'm sorry I need some help on this. I created the file in domoticz root (/home/pi/domoticz/ { "temp": [ "temperature", "ambient_temperature" ], "humidity": [ "hum" ], "baro": [ "barometer" ...

kiddigital wrote: ↑Saturday 13 November 2021 17:12 @jeroenkl , take a look at the aliases file (ttnmqtt_aliases.json). There you can fill in aliases for decodes payload values.

Example ‘’temperature_2” as “temperature”, so the module knowns how to treat ‘temperature_2’.

thxs!
Ehhh where can I find this file in my Raspberry Pi?

Second device, also Wisblock, build with: https://github.com/beegee-tokyo/RAK4631-Kit-2-RAK1910-RAK1904-RAK1906 Got this log message: 2021-11-13 16:00:55.391 Error: TESTv3MQTT client gateway Wisblocks: Error parsing message (Type is not convertible to string)!!! "decoded_payload": { "accelerometer_3 ...

For my Wisblock device, the LPP data is not accepted by domoticz: 2021-11-13 15:52:37.632 Error: TESTv3MQTT client gateway Wisblocks: Invalid data received! Unable to decode the raw payload and the decoded payload does not contain any (valid) data! Payload: "decoded_payload": { "analog_in_8": 4.38 ...

'the data entered into the OCPP SOAP node (especially url and port) needs to match the supervision settings in your box' that's I need to investigate.
I'm using Alfen eve Single Pro

Sorry, saw the postings only just now. I am using Node-Red to interface the Wallbox to Domoticz. the OCPP protokol is a bit confusing, but anyway it works for me. If you need, I can share my flow here. EDIT: additionally you may need to set up your WB to be a 'managed system' instead of standalone ...

Hi All Does someone have experience with an "Eve-Single Pro-line" Car Charging Station from Alfen, connected to Domoticz ? Mine is connected with Eneco, by mobile network, it has internal a SIM. The device does also have a Network connector. regards, Roland Same situation, any update and result ...

FunFair wrote: ↑Tuesday 29 June 2021 22:01 With DSM7 my 2 disks are located at .1.3.6.1.2.1.25.2.3.1.5.47 and .1.3.6.1.2.1.25.2.3.1.5.48

This instead of .38 or .41

On DS920+ with DSM7 it is .57

the script --[[ Virtual Okta sensor (only) from https://www.domoticz.com/forum/viewtopic.php?f=72&t=19220 from V2.4 - BakSeeDaa - dzVents version of the Solar Data Script see also http://www.ogimet.com/display_synops2.php?lang=en&lugar=07149&tipo=ALL&ord=REV&nil=SI&fmt=html&ano=2019&mes=03&day=30 ...

I've got the same behavior and didn't take any action to 'fix' it. Do you have already a solution? I made a change in SBFspot.cfg. I set SunROffset to its maximum value (3600). No more errors since then. # SunRSOffset # Offset to start before sunrise and end after sunset (0-3600 - default 900 ...

Is there a place to find the latest version ? like on github ? I shared the original LUA script in the initial post. I have no yet shared the dzVents version. Although I have a github account, I never published anything myself. The script had some little errors today, I hope they're fixed by now ...

FYI

https://github.com/Koenkk/zigbee2mqtt
Koenkk zigbee2mqtt 1.18.0

FYI,
The latest ZZH! Koenkk firmware works fine too:
v.1.17.1 (zStack3x0 20210120)

https://github.com/Koenkk...dinator/Z-S ... _3.x.0/bin

MikeF wrote: ↑Tuesday 02 February 2021 16:18 For info, Koenkk has just released v1.17.1 of zigbee2mqtt - see changelog here: https://github.com/Koenkk/zigbee2mqtt/releases
(fixes / improvements / new supported devices)

Thanks to let us know, update went fine.

Is it possible with this dzVents command to change the Icon 'text' at a custom dummy created device? Yes but you need to be on the Beta version build >= 12750. Please note tat the iconchange will only be visible when you reopen the screen or after you manually refresh [(ctrl] r in Chrome) or switch ...

Over 2 years since I asked about changing icons on the fly but never got a suggestion. Maybe now? http://<domoticz ip: domoticz port>/json.htm?type=setused&used=true&name=<name>&description=<description>&idx=<idx>&switchtype=<switchType>&customimage=<iconNumber> or in a dzVents script: domoticz ...