Hue / emulation issue after oh4 upgrade

KenkiCK · July 31, 2023, 10:25am

Another issue which I fugure out is that it looks like after the upgrade most of all Items has HUEEMU in the metadata.

No clue if it is necessary or can be removed. The example here is an Item switch which is defined by myself. It is also strange that this tag is separated from the others.

Lolodomo · August 1, 2023, 9:04am

This is probably in link with the hue emulation binding. Are you sure that you are or were not using this IO service?
I am not emough aware of hue emulation service to explain what is the need of this tag.

Hoerli · August 1, 2023, 2:53pm

Hi!
Have the same phenomenon.
All items now have HUEEMU and each has been given a different number.
I have not installed the Hue binding.

Deleting this info goes without a hitch and I don’t think it triggers any further problems.

laursen · August 1, 2023, 3:02pm

As @Lolodomo mentioned, this is from the Hue emulation:

github.com

openhab/openhab-addons/blob/846e9aa2060f8a0707923a7378887da98187805b/bundles/org.openhab.io.hueemulation/src/main/java/org/openhab/io/hueemulation/internal/ConfigStore.java#L80


      
          * This is a central component and required by all other components and may not
          * depend on anything in this bundle.
          *
          * @author David Graeff - Initial contribution
          */
          @Component(immediate = false, service = ConfigStore.class, configurationPid = HueEmulationService.CONFIG_PID)
          @ConfigurableService(category = "io", label = "Hue Emulation", description_uri = "io:hueemulation")
          @NonNullByDefault
          public class ConfigStore {
          
             public static final String METAKEY = "HUEEMU";
             public static final String EVENT_ADDRESS_CHANGED = "HUE_EMU_CONFIG_ADDR_CHANGED";
          
             private final Logger logger = LoggerFactory.getLogger(ConfigStore.class);
          
             public HueDataStore ds = new HueDataStore();
          
             protected @NonNullByDefault({}) ScheduledExecutorService scheduler;
             private @Nullable ScheduledFuture<?> pairingOffFuture;
             private @Nullable ScheduledFuture<?> writeUUIDFuture;

and:

github.com

openhab/openhab-addons/blob/846e9aa2060f8a0707923a7378887da98187805b/bundles/org.openhab.io.hueemulation/src/main/java/org/openhab/io/hueemulation/internal/ConfigStore.java#L319-L345


      
          /**
           * Although hue IDs are strings, a lot of implementations out there assume them to be numbers. Therefore
           * we map each item to a number and store that in the meta data provider.
           *
           * @param item The item to map
           * @return A stringified integer number
           */
          public String mapItemUIDtoHueID(Item item) {
              MetadataKey key = new MetadataKey(METAKEY, item.getUID());
              Metadata metadata = metadataRegistry.get(key);
              int hueId = 0;
              if (metadata != null) {
                  try {
                      hueId = Integer.parseInt(metadata.getValue());
                  } catch (NumberFormatException e) {
                      logger.warn("A non numeric hue ID '{}' was assigned. Ignore and reassign a different id now!",
                              metadata.getValue());
                  }
              }
              if (hueId == 0) {

This file has been truncated. show original

I don’t know if there was a change in the UI that could change anything here, maybe this was not visible before? There doesn’t seem to be any changes in the emulation itself regarding this.

J-N-K · August 1, 2023, 6:28pm

Maybe it is this change: Show custom namespaces for items in metadata menu by stefan-hoehn · Pull Request #1623 · openhab/openhab-webui · GitHub

KenkiCK · August 2, 2023, 7:36am

OK, I use the HUE Binding and I guess this includes the HUE Emulation. I would understand if the all HUE devices has the tag but why every device (or better most of all) ? I think it has no impact regarding the performance but I will remove it step by step. It could be aso that it was a bug in an older version and now visible.

Thanks all for your support.

Lolodomo · August 2, 2023, 7:46am

Hue binding and hue emulation binding ate 2 different things.
Please update your issue title to rather mention hue emulation as your problem has absolutely no link with the hue binding.

MikeJMajor · August 2, 2023, 8:11am

The hue emulation has tagged items with the HUEEMU metadata for a very long time and the only difference in OH 4.0 is that this is now visible in the UI.

If you have items tagged with HUEEMU then you must have the Hue Emulation addon installed or previously had it installed. If you are actually relying on the hue emulation then removing that metadata will break it.

AndrewFG · August 2, 2023, 9:10am

If I read it right, this is not a bug. The metadata has always been present. But new in OH 4.0 the metadata is now displayed in the UI.

KenkiCK · August 2, 2023, 9:35am

@AndrewFG Yes, this is what I understood too.
@Lolodomo I add with a slash the emulation in the header of this topic. I have not installed the HUE Emulation binding actual but I can’t say if it was installed in a previous version.
@MikeJMajor I never have tagged any item with HUEEMU - thats the reason why I wondering - this must be done automatically and is now visible. I would understand that this tag is assigned to items which are relvant for the HUE Emulation but not for every item.

But like we say, never change a running system …

system · September 13, 2023, 1:36am

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.