My issue is similar than this one https://github.com/FlyingDomotic/domoticz-mqttmapper-plugin/issues/19 that's doesn't seem really solved....but moving the device from "computed" to "device" make it work and then back to "computed" and still working
Hope it could help others

Found the mistake: need a "~" before the 0

{
"Maison Wbis": {
"topic": "shellyemg3-b08184e81cd8/events/rpc",
"type": "243", "subtype": "29", "switchtype": "0",
"mapping": {"item": "params/em1:0/act_power;~0"},
"options": {"EnergyMeterMode": "1"}
}
}

So now the log sounds good but I don't ...

I think I need to use the following topic : "shellyemg3-b08184e81cd8/events/rpc" (was missing "rpc") but then I have error in the log (at least it receives something):
2025-09-26 20:52:55.011 ShellyEMGen3: onMQTTPublish found shellyemg3-b08184e81cd8/events/rpc, Device 'ShellyEMGen3 - Maison Wbis ...

Type 244, subtype 73, switchtype 0 is an on/off switch.

To get a kWh device, use 243/29/0

Was correct in my first message and don't know when I changed that!! :?
Sorry!
SO now the device is ok but not updated at all.
I checked with mosquito and I receive well the messages:
{"src":"shellyemg3 ...

Domoticz sometimes not so good manages changing device type.

If you change "type", "subtype" or "switchtype" in json configuration file, you may have to delete device first to let it create instead of modify device.

So I deleted the device in domoticz...and Mqttmapper created the same device ...

So I am back on it, it doesn't crash now with:

{
"Maison Wbis": {
"topic": "shellyemg3-b08184e81cd8/events",
"type": "244", "subtype": "73", "switchtype": "0",
"mapping": {"item": "params/em1:0/act_power;0"},
"options": {"EnergyMeterMode": "1"}
}
}


but it creates only one device that is ...

Sorry I mean when I created the hardware…
No other json, only this one

So if I understood correctly the result is the following:
{
"Maison Wbis": {
"topic": "shellyemg3-b08184e81cd8/events",
"type": "244", "subtype": "73", "switchtype": "0",
"mapping": {"item": "params/em1:0/act_power;0"},
"options": {"EnergyMeterMode": "1"}
}
}
But then I created the device ...

Hi there,

After Shelly_MQTT (discontinued), ShellyTeacher (discontinued), I am jumping into MqttMapper to make my Shelly EM Gen3 read by domoticz.
A bit tricky to understand everything about the settings (even if the french version is clearer for me ;) ).
I want my (new) Shelly to publish values to ...

waltervl wrote: Wednesday 24 August 2022 12:04 You mean like using a floorplan?
Rearranging devices over custom tabs is a long known wish but difficult to implement due to the current architecture of Domoticz.

Ok good to know that it is somehow a known nice to have feature

Hello,

Use case:
I create a new material that is creating : 2 temperature devices, 3 On/off devices and 1 measure device.
So I have all those 6 devices on 3 different tabs.
But it would be nice to be able to see all those 6 devices in 1 view.

Domoticz could add a "custom view" tab where you can ...

Is there any progress on this topic?

waltervl wrote: Monday 07 March 2022 16:33 @darrepac Plugin issues were on Bullseye environment not on Buster.

I just share my experience...

I had also lot of plugin problem with latest stable. I updated to latest Beta because something has been changed about python, and everything is working much better now

Hello

I have shellies and plugin working since a while flawlessly.
Yet, I realized something odd with my Shelly EM:
While the voltage device is updated everything few seconds (at each mqtt update), the watt consumption is only updated every 10 or more seconds (while through MQTT Explorer I see ...

Hello

I have shellies and plugin working since a while flawlessly.
Yet, I realized something odd with my Shelly EM:
While the voltage device is updated everything few seconds (at each mqtt update), the watt consumption is only updated every 10 or more seconds (while through MQTT Explorer I see that ...

Hello

I have updated to latest stable (2022.1) and latest zigbee2mqtt ( I should have not as everything was working well before) and I have the following error in the log:
Error: Zigbee2MQTT: 'onCommand' failed 'TypeError':''NoneType' object is not subscriptable'.
2022-02-02 22:23:04.923 Error ...

Well in fact I disconnected and reconnected and it works now.
I just have one strange thing. I have listed all the remote and one of them is:
20/01/2022 05:40:22:691= 1401030A00060101010592F6687420524658434F4D
Packettype = Interface Message
subtype = RFY remote:6 ID:01 01 01 unitnbr:5 rfu1:92 rfu2 ...

Did flash RFXrec firmware which is not correct

I have to reflash the firmware or I choose a wrong one? Here is the log:
Device found...
Loading HEX file: D:\Mes Telechargements\RFXtrx433E_Ext_firmware\RFXtrx433_Ext_1025.hex , please wait...
HEX file imported...
Erasing...
Erase: 13800

Finished ...

b_weijenberg wrote: Thursday 20 January 2022 14:36 Use the procedure in chapter 9 of the RFXtrx User Guide.

In short:
put the motor in learning mode and transmit a program command. I guess easiest is to use the same ID and unit code as used in Domoticz.

I read already the manual but as said before I cannot "transmit" any command