Hue Tap from deconz is not visible in official Hue android app but is accessible in Hue Essentials and All4Hue

[doctorjames]

Describe the bug

A Hue Tap that has successfully been added to deconz and imported into diyhue cannot be seen in the accessories settings in the official Hue android app (v4.47.0).

Steps to Reproduce

1. Add a Tap in deconz
2. Within the Hue android app, click on "Settings"
3. Click on "Accessory setup"
4. Hue tap is not visible

Expected behavior

Hue tap should be selectable in order to configure it. It is visible in All4Hue and Hue Essentials.

Logs

output of a GET on the sensors endpoint:

{
    "1": {
        "config": {
            "configured": false,
            "on": true,
            "sunriseoffset": 30,
            "sunsetoffset": -30
        },
        "manufacturername": "Philips",
        "modelid": "PHDL00",
        "name": "Daylight",
        "state": {
            "daylight": null,
            "lastupdated": "none"
        },
        "swversion": "1.0",
        "type": "Daylight"
    },
    "2": {
        "config": {
            "configured": true,
            "on": true,
            "sunriseoffset": 30,
            "sunsetoffset": -30
        },
        "etag": "a9b743b5aa5ddf0d2bd4072f6ce91f46",
        "manufacturername": "Philips",
        "modelid": "PHDL00",
        "name": "Daylight",
        "state": {
            "dark": true,
            "daylight": false,
            "lastupdated": "2021-03-11T00:19:57.795",
            "status": 100,
            "sunrise": "2021-03-11T06:33:59",
            "sunset": "2021-03-11T18:05:45"
        },
        "swversion": "1.0",
        "type": "Daylight",
        "uniqueid": "00:21:2e:ff:ff:01:ba:79-01"
    },
    "3": {
        "config": {
            "on": true,
            "reachable": true
        },
        "etag": "646af10d0f28a4f2d11e8ed86b9b8369",
        "manufacturername": "Phoscon",
        "modelid": "PHOSCON_FSM_FLAG",
        "name": "CLIP-Sensor TOOGLE-COLORLOOP",
        "state": {
            "flag": true,
            "lastupdated": "2021-03-10T23:07:38.564"
        },
        "swversion": "1.0",
        "type": "CLIPGenericFlag",
        "uniqueid": "00:00:00:00:00:43:b5:1e-f2-toogle-colorloop-2"
    },
    "4": {
        "config": {
            "on": true
        },
        "ep": 242,
        "etag": "772caa4139f5b0ef7223319e3dd061c4",
        "lastseen": "2021-03-10T23:43Z",
        "manufacturername": "Philips",
        "modelid": "ZGPSWITCH",
        "name": "Tap",
        "state": {
            "buttonevent": 34,
            "lastupdated": "2021-03-11T00:07:35.556"
        },
        "type": "ZGPSwitch",
        "uniqueid": "00:00:00:00:00:43:b5:1e-f2"
    }
}

Docker Info (please complete the following information):

• Architecture (Ex: x86, ARM): armv7l
• Docker image version (Ex: latest, arm-05f043b, 128): diyhue/core:latest
• OS (Ex: Windows 10, Ubuntu Buster): Debian 10 (Raspbian)
• Hardware (Ex: PC, Raspberry Pi 1/2/3/Zero): Pi 2

Checklist

• I confirm that this is a bug report
• I confirm that I have completed this template to the best of my ability

Additional context

Extract from config:

from deconz section:

 "deconz": {
        "sensors": {
            "7": {
                "bridgeid": "4",
                "modelid": "ZGPSWITCH",
                "type": "ZGPSwitch"
            }
        }
    }

and from the sensors section:

    "sensors": {
        "4": {
            "config": {
                "on": true
            },
            "ep": 242,
            "etag": "772caa4139f5b0ef7223319e3dd061c4",
            "lastseen": "2021-03-10T23:43Z",
            "manufacturername": "Philips",
            "modelid": "ZGPSWITCH",
            "name": "Tap",
            "state": {
                "buttonevent": 17,
                "lastupdated": "2021-03-11T00:06:08.159"
            },
            "type": "ZGPSwitch",
            "uniqueid": "00:00:00:00:00:43:b5:1e-f2"
        }
    }

[mariusmotea]

This sensors was "raw" imported from Deconz. All these values you posted where imported from Deconz. The good news is that now you can edit config.json file and add the missing keys (added recently in the hue api). Also you can configure this sensor now from Hue Essentials.

[doctorjames]

Cool, I'll try editing it. Should I have added the switch in a different way or is it mostly a deconz issue? (This is just me testing before adding six.) I looked but couldn't find any guidance around this.

[mariusmotea]

Unfortunatelly you need output from an original bridge with this switch connected and i was unable to find on google.

I recommend to add/update the following values in config.json for this sensor (stop the emulator service first):

"capabilities":{"certified":true}
"manufacturername": "Signify Netherlands B.V."
"swupdate": {"state": "noupdates","lastinstall": "2021-03-10T21:16:40" }

[doctorjames]

I'll experiment this evening (I have a real hue hub). I'll write a simple python script to update the config. I'll post it here if it's successful and you can incorporate it into the service if you wish, or at least other people can find it here.

I've not tried a dimmer switch yet in deconz, but I presume that will likely need the same thing?

[mariusmotea]

Will be great if you can provide these.

[doctorjames]

Here's the script in this gist that will update the config file adding the missing keys.

It's extremely basic and assumes the config.json is in the current directory. After running it a config.json.new is produced.

On restarting diyHue with the new config, both the Tap and the Dimmer v1 are then visible in the Hue Android app. The tap appears to configure OK, but configuring the dimmer hung the app part way through. The accessories page also hung subsequently when going back to it.

Within the dimmer's sensor definition "group": "2" had appeared:

"config":{
  "battery": 100,
  "group": "2",
  "on": true,
  "reachable": true
}

This had been inserted at some point and I've not seen it in the real Hue hub's json. Manually deleting this line stopped the hanging and I could return to the accessories page in the app. I haven't investigated any further.

[stale]

This issue has been automatically marked as stale because it has not been verified. If this is still an issue, please provide the more information so that we are able to understand the issue. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed as it has not had any recent activity. Thank you for your contributions.