Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Hardware Request]: Gen3-devices of the Shelly Plus 1 Mini Gen. 3 #927

Closed
2 tasks done
Khazaa opened this issue Jan 6, 2024 · 13 comments
Closed
2 tasks done

[Hardware Request]: Gen3-devices of the Shelly Plus 1 Mini Gen. 3 #927

Khazaa opened this issue Jan 6, 2024 · 13 comments
Assignees
Labels
fixed Issue fixed, please test hardware request Request to integrate new devices

Comments

@Khazaa
Copy link

Khazaa commented Jan 6, 2024

I'm sure that

  • This device is still unsupported in the current beta version of this adapter
  • There is no other (open) request for the same device type (used the search)

Shelly device

Shelly Plus 1 Mini Gen. 3

Further information

Hello,
I don't know how to look in the beta version. If this device is in the the beta, sorry!

I bought the Shelly and the adapter log says:
[MQTT] Client Close: (shelly1minig3 / shelly1minig3-84fce636ca58 / undefined) (false)
[MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details)
[MQTT] (Shelly?) device unknown, configuration for client with id "shelly1minig3-84fce636ca58" does not exist! Maybe this device is not supported in this adapter version.

I didn't change the client-id.

Here are some data from the Shelly:
Shelly Mini1G3 84FCE636CA58| 1.1.0| 8372d8c8|
Firmware-ID: 20231219-134003/1.1.0-g34b5d4f

If you need some more information, just ask :)

And thank you for your help!

Copy link

github-actions bot commented Jan 6, 2024

Thanks for reporting a new issue @Khazaa!

  1. Please make sure your topic is not covered in the documentation
  2. Ensure that you use the latest beta version (not the current stable version): 6.7.0
  3. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue
  4. Search for the issue topic in other/closed issues to avoid duplicates!

Otherwise this issue will be closed.

@Khazaa
Copy link
Author

Khazaa commented Jan 6, 2024

[update] I found out, how to use the beta (6.7.0) und the device is still not usable with it.

@klein0r klein0r added the hardware request Request to integrate new devices label Jan 6, 2024
@HanSolo72
Copy link

You can close this case. I already opened it here: #915

@Khazaa
Copy link
Author

Khazaa commented Jan 19, 2024

Sure? My device is not the "PM" Version...

@HanSolo72
Copy link

Sorry, you're right. Was late last night.

BooosesThaSnipper added a commit to BooosesThaSnipper/ioBroker.shelly that referenced this issue Jan 28, 2024
@Joylancer
Copy link

i have removed "g3" from clientid in mqtt-settings, works as PMMINI
grafik

@garfield7791
Copy link

Just tested Joylancers comment. It really works if you remove "G3" from client ID. Thanks!

klein0r pushed a commit that referenced this issue Mar 18, 2024
* Add Humidity for DHT22 connected to Shelly Plus Addon

#738

* Revert "Add Humidity for DHT22 connected to Shelly Plus Addon"

This reverts commit da85a69.

* #936 - fix wrong description

* #915 / #927 - Add Gen3 Mini Devices:

#915 / #927 - Add Gen3 Mini Devices:
- #915
- #927

* Revert "#915 / #927 - Add Gen3 Mini Devices:"

This reverts commit ec72d89.

* Update shellytrv.js - nochange, just retrigger checks

---------

Co-authored-by: Martin M <mcm57@gmx.at>
@AceAutomation
Copy link

Hi - Can anyone tell me what to put in the MQTT payload and topic to activate the relay on a Shelly Plus 1 Mini Gen 3, I've tried almost everything, to no avail. I become crazy. It is connected to the broker.
For example, if MQTT prefix and Client ID is like the screenshot above.
Thanks

@SpeedyQ
Copy link

SpeedyQ commented Apr 5, 2024

Please find my yaml configuration below (to be used with mqtt and homeassistant) where you also see the payload I use to switch the mini on/off.
In the mini configuration I did not tick the setting ' RPC status notifications over MQTT', all other settings are similar as the screen dump above.

Shelly mini1 G3 bathroom

  • name: "Bathroom light"
    unique_id: "Bathroom_light"
    state_topic: "shellies/shelly1minig3-84fce63a3088/status/switch:0"
    command_topic: "shellies/shelly1minig3-84fce63a3088/rpc"
    availability_topic: "shellies/shelly1minig3-84fce63a3088/online"
    <<: &shelly_mini1_switch
    state_on: true
    state_off: false
    value_template: "{{ value_json['output'] }}"
    payload_on: '{"id": 1, "src": "homeassistant", "method": "Switch.Set", "params":{"id":0,"on":true}}'
    payload_off: '{"id": 1, "src": "homeassistant", "method": "Switch.Set", "params":{"id":0,"on":false}}'
    payload_available: "true"
    payload_not_available: "false"
    qos: 1
    retain: false

Also note that the settings below '<<: &shelly_mini1_switch' are generic and can be configured only once and you can reference these if you have more mini's.
Example:

Shelly mini1 G3 office

  • name: "Office light"
    unique_id: "Office_light"
    state_topic: "shellies/shelly1minig3-ecda3bc2f744/status/switch:0"
    command_topic: "shellies/shelly1minig3-ecda3bc2f744/rpc"
    availability_topic: "shellies/shelly1minig3-ecda3bc2f744/online"
    <<: *shelly_mini1_switch

@Pava1955
Copy link

Hi ho provato i comandi che hai scritto sopra per gestire accensione e spegniamento della caldai (mini1Gen3) purtroppo non riesco a farlo funzionare. di seguito quello che "vedo" con MQTT Explorer:

V shelly1minig3-84fce63ba33c**
V status
switch:0 = {"id":0,"source":"init", "output":false, "temperature":{"tC":57.7,"tF":135.9}}
ble = 0
cloud = {"connected":true}
input:0 = {"id":0,"state":false}
mqtt = {"connected":true}
script: 1 = {"id":1,"running":true, "mem_used":462,"mem_peak":1302,"mem_free":24738}
sys = {"mac":"84FCE63BA33C", "restart_required":false,"time":null, "unixtime":null,"uptime":2,"ram_size":259400,"ram_free":96416,"fs_size": 1048576,"fs_free":712704,"cfg_rev":13,"kvs_rev":3,"schedule_rev":0,"webhook_rev":0,"available_updates":0,"reset_reason":3}
wifi = {"sta_ip":"192.168.1.14","status":"got ip","ssid":"Vodafone-A41357753","rssi" :- 79}
ws = {"connected":false}
V events
rpc = {"src":"shelly1minig3-84fce63ba33c","dst":"shelly1minig3-84fce63ba33c/events","method":"NotifyStatus","params":{"ts": 1713278915.28,"cloud":{"connected":true}}}
online = true

e questo è il file yaml riferito allo switch:

  • name: "CaldaiaiSwitch"
    unique_id: "CaldaiaiSwitch"
    state_topic: "shelly1minig3-84fce63ba33c/status/switch:0"
    command_topic: "shelly1minig3-84fce63ba33c/events/rpc"
    availability_topic: "shelly1minig3-84fce63ba33c/online"

<<: &shelly_mini1_switch

state_on: "true"
state_off: "false"
value_template: "{{ value_json.output }}"
payload_on: '{"id": 1, "src": "homeassistant", "method": "Switch.Set", "params":{"id":0,"on":true}}'
payload_off: '{"id": 1, "src": "homeassistant", "method": "Switch.Set", "params":{"id":0,"on":false}}'
payload_available: "true"
payload_not_available: "false"
qos: 1
retain: false

dove sbaglio ??
Grazie a chi vorrà darmi una mano !

@SpeedyQ
Copy link

SpeedyQ commented Apr 16, 2024

Hi ho provato i comandi che hai scritto sopra per gestire accensione e spegniamento della caldai (mini1Gen3) purtroppo non riesco a farlo funzionare. di seguito quello che "vedo" con MQTT Explorer:

V shelly1minig3-84fce63ba33c**

V status
switch:0 = {"id":0,"source":"init", "output":false, "temperature":{"tC":57.7,"tF":135.9}}
ble = 0
cloud = {"connected":true}
input:0 = {"id":0,"state":false}
mqtt = {"connected":true}
script: 1 = {"id":1,"running":true, "mem_used":462,"mem_peak":1302,"mem_free":24738}
sys = {"mac":"84FCE63BA33C", "restart_required":false,"time":null, "unixtime":null,"uptime":2,"ram_size":259400,"ram_free":96416,"fs_size": 1048576,"fs_free":712704,"cfg_rev":13,"kvs_rev":3,"schedule_rev":0,"webhook_rev":0,"available_updates":0,"reset_reason":3}
wifi = {"sta_ip":"192.168.1.14","status":"got ip","ssid":"Vodafone-A41357753","rssi" :- 79}
ws = {"connected":false}
V events
rpc = {"src":"shelly1minig3-84fce63ba33c","dst":"shelly1minig3-84fce63ba33c/events","method":"NotifyStatus","params":{"ts": 1713278915.28,"cloud":{"connected":true}}}
online = true

e questo è il file yaml riferito allo switch:

* name: "CaldaiaiSwitch"
  unique_id: "CaldaiaiSwitch"
  state_topic: "shelly1minig3-84fce63ba33c/status/switch:0"
  command_topic: "shelly1minig3-84fce63ba33c/events/rpc"
  availability_topic: "shelly1minig3-84fce63ba33c/online"

<<: &shelly_mini1_switch

state_on: "true"

state_off: "false"
value_template: "{{ value_json.output }}"
payload_on: '{"id": 1, "src": "homeassistant", "method": "Switch.Set", "params":{"id":0,"on":true}}'
payload_off: '{"id": 1, "src": "homeassistant", "method": "Switch.Set", "params":{"id":0,"on":false}}'
payload_available: "true"
payload_not_available: "false"
qos: 1
retain: false

dove sbaglio ?? Grazie a chi vorrà darmi una mano !

I am not sure what your setup is, but it looks like you have cloud services enabled, so a lot of items shown in MQTT explorer is not what I see in my setup. To be clear, I am not using Shelly cloud. Instead I use everything locally; my MQTT server, Home Assistant and the Shelly. If I switch on my bathroom light shelly, it only displays few properties in MQTT explorer. See picture.
MQTTExplorer

@mcm1957
Copy link
Member

mcm1957 commented Apr 16, 2024

Please use ENGLISH or GERMAN language,

@AceAutomation

This comment was marked as off-topic.

@klein0r klein0r added the fixed Issue fixed, please test label Apr 29, 2024
@klein0r klein0r closed this as completed Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed Issue fixed, please test hardware request Request to integrate new devices
Projects
None yet
Development

No branches or pull requests

9 participants