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

Shelly Wave Shutter, second, seperate import, of another device same type does not list all States #2869

Open
2 tasks done
PackElend opened this issue Jan 19, 2025 · 3 comments
Assignees

Comments

@PackElend
Copy link

PackElend commented Jan 19, 2025

*Please note that you may restore an old layout via jarvis adapter configuration directly within ioBroker

Prerequisites / Voraussetzungen

  • v3.1.8
  • same type but different list of states after import

Describe the bug / Beschreibe den Fehler
My initial (wizard) setup imported a Shelly Qubino Wave Shutter—All products—Shop—Shelly completely. However, another import of a later included device shows only a fraction of the full state list.
The tree in Objects is identical.

Object Tree JSON: zwave2.0.json

Screenshots

  1. First Device
    was detected as light
    Image

  2. Device
    was detected as a sensor
    I added up_001 and down_001 manually
    Image


Please note that bug reports may be closed if the information above are not given!

Bitte beachte, dass Bug-Reports ggf. einfach geschlossen werden, wenn die oben genannten Kriterien nicht angemessen gegeben sind!

@mcuiobroker
Copy link
Collaborator

mcuiobroker commented Jan 20, 2025

Warum zwave-Adapter und nicht shelly-Adapter genutzt, ist doch ein shelly-Gerät?
Oder wird das Gerät vom Shelly nicht erkannt?

@PackElend
Copy link
Author

Warum zwave-Adapter und nicht shelly-Adapter genutzt, ist doch ein shelly-Gerät?

Da es ein z-wave Gerät ist.
Ich habe den Shelly Adapter nicht installiert, da er nur folgendes unterstützt:

The adapter communicates with Shelly devices by REST API and the CoAP or MQTT protocol.

https://github.com/iobroker-community-adapters/ioBroker.shelly?tab=readme-ov-file#versions

@mcuiobroker
Copy link
Collaborator

Für BlindeLevel benötigt man ja
ein level -DP -> zwave2.0.Node_003.Multilevel_Switch.targetValue_001
ein stop -DP -> ??
ein activity -DP -> ??

-> da wird man ein eigenes Scipt schreiben müssen, der die DPs erstellt.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants