Shelly 1PM Mini Gen3

Add-ons Bindings
,
1

Dear Shelly dev’s,

Recently I bought a couple of Shelly 1PM Mini’s, I received the Gen3 model. They’re not playing nice with the 4.1 Shelly binding release. I tried them with the most recent OH 4.2 snapshot build and as well with the 4.2 Shelly binding snapshot build. In both cases I’ve got alot of communication errors.
So, am I correct in asuming these Gen3 models aren’t supported yet?
And is there maybe a workaround to get them playing nice with the 4.1 build, or do I need to be just a littlepatient? I hope someone can help me out.

Best regards,
Jesse

2

I’m using my Shelly PM Mini Gen3 with MQTT unitl they are working fine with the newest shelly binding version.
This should also work with the 1PM Mini Gen3

1 Like
3

Ha Erik,

Thanx for the reply and the mqtt suggestion. I guess I’ll take that route for now.

Best regards, Jesse

4

Looks like the Gen 3 series support has been implemented recently. The associated pull request has been merged:
https://github.com/openhab/openhab-addons/pull/16335

Is it possible to get these changes in OH 3.1 or do I have to upgrade to the latest OH version?

5

You will need to upgrade to 4.2 m1 (as soon as it is available) or switch to snapshot

6

I was afraid someone would say that. :worried:
I checked the docs and it seems a rather cumbersome procedure to perform that upgrade with high risk of something breaking. So I might eventually do that but need to be prepared to spend some considerable amount of time. Next time I buy some new hardware I better check the compatibility with my OH version.

7

Totally worth the effort if you ask me :slight_smile:

1 Like
8

Is there a difference between the “Shell 1PM Mini Gen3” and the “Shelly Plus 1PM Mini Gen3” ?

The Pull Request only mention the PLUS Version?!?!?!

9

Hi, I am also working to implement a “Shelly Mini 3G” via MQTT, unfortunatley I am having problems to switch it via openhab.

Reading the status is already working fine with the following code:

		Thing mqtt:topic:Shelly_Mini3G_Garage "Light" @ "Garage" {
		Channels:
			Type switch : power "Power" [ 
				stateTopic="shelly1minig3-5432044f36a0/events/rpc", 
				transformationPattern="JSONPATH:$.params.switch:0.output", 
				commandTopic="shelly1minig3-5432044f36a0/events/rpc",
				on="true", 
				off="false"

But unfortunately switching it dosn’t work as the “commandTopic” is not correct.
Can somebody help me on this issue?

Thank you :slightly_smiling_face:

10

Hi, this my working UI code:

UID: mqtt:topic:a65cab3f72:4a2737b998
label: Duschlicht
thingTypeUID: mqtt:topic
configuration:
availabilityTopic: duschlicht/online
payloadAvailable: “true”
bridgeUID: mqtt:broker:a65cab3f72
channels:

  • id: Betrieb
    channelTypeUID: mqtt:switch
    label: Betrieb
    description: “”
    configuration:
    commandTopic: duschlicht/command/switch:0
    transformationPatternOut: MAP:trueToOn.map
    stateTopic: duschlicht/status/switch:0
    transformationPattern: JSONPATH:$.output
    off: “false”
    on: “true”

With trueToOn.map
true=on
false=off

Best, Ralf

11

How can I get a jar file of this binding-update?
I am on OH 4.1.1 and real OH newbie.

12

Gen3 Shelly 1PM Mini’s encounter communication errors with 4.1 Shelly binding.

13

Hi,
I installed the OH4.2.0 M1 Milestone with the latest Shelly binding updates implemented and it works properly with my Shelly1 mini G3 (not PM).

1 Like
14

I tried to implement your configuration in my setup, but wasn’t sure what to do with the last part?

With trueToOn.map
true=on
false=off

Can you help me in the right direction?

15

You need to put a file called trueToOn.map into the tranform folder in opnehab-config folder.
Content of the file is:
true=on
false=off

16

Now it works perfect. Installing the transformation service was the last I needed to get it up running. Thank you so much.

17

i can confirm that

18

Hi,

Revisiting this topic to add a post I made on the Shelly Binding thread and add some additional info.

Original post:

I got this reply:

ohuser:

I have the same issue with latest & greatest SW & HW (OH 5.0.1, Shelly Mini Gen4). My current solution is to use MQTT to get the input channel change notifications.

I tried the MQTT work around, it doesn’t actually solve the original problem but at least makes openhab receive the input/event status updates. So for anybody who has the same problem and stumbles onto this post, for your convenience; an example for a thing configuration and a map transformation.

thing config:

UID: mqtt:topic:39f845666d:d793f9da78
label: MQTT | Switch | Livingroom | 01
thingTypeUID: mqtt:topic
configuration:
  payloadNotAvailable: "false"
  availabilityTopic: shelly/shelly-switch-livingroom-01/online
  payloadAvailable: "true"
bridgeUID: mqtt:broker:39f845666d
channels:
  - id: eventTrigger
    channelTypeUID: mqtt:trigger
    label: Event Trigger
    description: "MQTT Workaround to get event status updates from Shelly 1PM Mini Gen3 into OpenHAB 4.2.2"
    configuration:
      stateTopic: shelly/shelly-switch-livingroom-01/events/rpc
      transformationPattern: JSONPATH:$.params.events[0].event∩MAP:button_push.map

button_push.map:

single_push=SHORT_PRESSED
double_push=DOUBLE_PRESSED
triple_push=TRIPLE_PRESSED
long_push=LONG_PRESSED