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

[Bug]: Shelly Mini1PMG3 not recognised by Iobroker shelly adapter #1106

Closed
3 tasks done
marian-t-web-de opened this issue Dec 29, 2024 · 3 comments
Closed
3 tasks done
Labels
Not reproducible Unable to reproduce this issue on other systems not-latest-version Beta version not found in issue

Comments

@marian-t-web-de
Copy link

I'm sure that

  • This issue is still present in the current beta version of this adapter
  • There is no other (open) issue with the same topic (use the search!)
  • This issue is not described in the adapter documentation / FAQ (read the docs!)

Shelly device

Shelly Mini1PMG3 5432046BEDFC| 1.1.99-minig3prod1| aad9cbe1|

Shelly firmware version

1.4.4 dated 20241011 (newest)

Protocol

MQTT

The problem

Shelly Mini1PMG3 is not recognised by Iobroker Shelly adapter. 0. Instance is using "HTTP oder COAP", 1. Instance is using "HTTP oder MQTT". This one Gen3 Shelly will be shown neither in 0. Instance nor in 1. Instance objects. It's IP is 192.168.178.84.
Questionable is the Log entry with Wrong MQTT authentification of client "shelly1pmminig3-5432046bedfc". I've set MQTT (not HTTP) user/pass several times in shelly and iOb Adapter and got the same error. Are the Buffer Data in log representative for password, is the first buffer wrong (pass has 8 signs).

Also Log entry with "nodered_5890defa8c52768e" MQTT client. On my installation Node-Red is using port 1880, different as MQTT 1883 (?).
Shelly-MQTT settings:
image

Moreover, all other shellys are Gen1 with COAP and MQTT deactivated. 0. Instance shows 8 from 9 devices, 1. Instance only 5 of 9.

Running the Shelly Adapter Version 8.2.1 on a Docker Container (official from buanet) on a Raspi4 NAS.
Nodejs: 20.18.0
js-conmtroller 6.0.11

iobroker.current.log (in debug mode!)

shelly.1 2024-12-29 15:02:04.925 debug [MQTT Server] Close for 192.168.178.84 ((undefined / undefined / undefined))
shelly.1 2024-12-29 15:02:04.925 debug [MQTT] Destroying
shelly.1 2024-12-29 15:02:04.924 debug [deviceStatusUpdate] shelly1pmminig3#5432046bedfc#1: false
shelly.1 2024-12-29 15:02:04.924 debug [BaseClient] Destroying (shelly1pmminig3 / shelly1pmminig3-5432046bedfc / shelly1pmminig3#5432046bedfc#1)
shelly.1 2024-12-29 15:02:04.923 info [MQTT] Client Close: (shelly1pmminig3 / shelly1pmminig3-5432046bedfc / shelly1pmminig3#5432046bedfc#1) (false)
shelly.1 2024-12-29 15:02:04.922 debug [MQTT Server] End for 192.168.178.84 ((shelly1pmminig3 / shelly1pmminig3-5432046bedfc / shelly1pmminig3#5432046bedfc#1))
shelly.1 2024-12-29 15:02:04.901 error [MQTT] Wrong MQTT authentification of client "shelly1pmminig3-5432046bedfc"
shelly.1 2024-12-29 15:02:04.901 debug [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":106,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shelly1pmminig3-5432046bedfc/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shelly1pmminig3-5432046bedfc","username":"mqttclient","password":{"type":"Buffer","data":[109,48,49,116,107,48,99,122]}}
shelly.1 2024-12-29 15:02:04.898 debug [MQTT Server] New connection from 192.168.178.84
shelly.1 2024-12-29 15:02:01.207 debug [deviceStatusUpdate] SHSW-PM#D8BFC01A0756#1: false
shelly.1 2024-12-29 15:02:01.118 debug [deviceStatusUpdate] SHSW-PM#840D8EB1E1C5#1: false
shelly.1 2024-12-29 15:01:58.079 debug [onlineCheck] Checking SHSW-PM#D8BFC01A0756#1 on 192.168.178.39:80
shelly.1 2024-12-29 15:01:58.077 debug [deviceStatusUpdate] SHSW-PM#84CCA8AC6BAF#1: true
shelly.1 2024-12-29 15:01:58.067 debug [onlineCheck] Checking SHSW-PM#84CCA8AC6BAF#1 on 192.168.178.33:80
shelly.1 2024-12-29 15:01:57.996 debug [onlineCheck] Checking SHSW-PM#840D8EB1E1C5#1 on 192.168.178.34:80
shelly.1 2024-12-29 15:01:57.873 debug [deviceStatusUpdate] SHSW-25#10521C07A733#1: true
shelly.1 2024-12-29 15:01:57.869 debug [deviceStatusUpdate] SHSW-1#98CDAC0D2544#1: true
shelly.1 2024-12-29 15:01:57.867 debug [onlineCheck] Checking SHSW-25#10521C07A733#1 on 192.168.178.29:80
shelly.1 2024-12-29 15:01:57.863 debug [onlineCheck] Checking SHSW-1#98CDAC0D2544#1 on 192.168.178.38:80

Version of nodejs

20.18.0

Version of ioBroker js-controller

6.0.11

Version of adapter

8.2.1

@marian-t-web-de marian-t-web-de added the bug Something isn't working label Dec 29, 2024
Copy link

Thanks for reporting a new issue @marian-t-web-de!

Important: Ensure that you use the latest available beta version of this adapter (not the current stable version!): 8.5.1

  1. Please ensure your topic is not covered in the documentation
  2. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue.
  3. Search for the issue topic in other/closed issues to avoid duplicates!
  4. Check the changelog if the issue has already been covered in a previous release

Otherwise this issue will be closed!

@github-actions github-actions bot added the not-latest-version Beta version not found in issue label Dec 29, 2024
@marian-t-web-de
Copy link
Author

marian-t-web-de commented Dec 29, 2024

Hi,
the MQTT connection to Shelly Mini1PMG3 is working, was really letter turner in MQT name.

But the problem with recognising of all devices is still present.
Using 0. Instance "HTTP and COAP" gives only 8 Gen1 from 9 devices (no gen3), 1. Instance "HTTP and MQTT" only 5 Gen1 and 1 Gen3 (via MQTT) of 9.
As I'm using cloud values in some gen1 devices I don't wont to disclaim them, gen3 device in iOb is connectable via MQTT only.
How is to get it with one instance?

With the current 8.5.1 ver. the same problem.

@marian-t-web-de
Copy link
Author

I've found out that the change of instance settings from COAP to MQTT is not working properly.

Workaround: deleting the instance and resp. statepoints and creating it again using MQTT works: only the MQTT (gen3) shellys will be recognised.

For me - paying attention to the restriction reg. settings changing - is it acceptable.

@klein0r klein0r added Not reproducible Unable to reproduce this issue on other systems and removed bug Something isn't working labels Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Not reproducible Unable to reproduce this issue on other systems not-latest-version Beta version not found in issue
Projects
None yet
Development

No branches or pull requests

2 participants