Skip to content

What are the consequences of native devices? #514

@Nele213

Description

@Nele213

I use the adapter the first time. I use iobroker v7.7.9 and devices v1.2.8. After installing the adapter I have several native devices available. Some of my devices were recognized as the wrong device type. Unfortunately, there is no way to change this or delete the native device.
What are the consequences of this native devices?

For example, I use four Hue sockets. Three of them switch on a light and one of them switches on a power strip. However, all four were created as lights. Similarly, all Hue lamps with color were created as RGB lights instead of Hue lights. The adapter indicates that Hue lights are supported by Alexa, but RGB lights are unfortunately not.

My initial idea was to use the adapter to create aliases for use in the front end and scripts, thereby reducing the amount of work involved in making changes when replacing or migrating devices. If I understand correctly, this should be done via the virtual devices.
Secondly, it would be great to import the devices from iobroker into Alexa. This step would be optional, and I haven't really looked into it yet, but I don't want to mess anything up if the wrong device type is selected.

Can I therefore simply ignore the native devices? What happens if I create a virtual device with the same name as a native device? Is there anything else I should keep in mind regarding native devices?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions