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

Support for ubisys S1? #638

Closed
felixstorm opened this issue Jun 12, 2018 · 10 comments
Closed

Support for ubisys S1? #638

felixstorm opened this issue Jun 12, 2018 · 10 comments
Labels

Comments

@felixstorm
Copy link
Contributor

Would it be possible to add support for the ubisys S1 in addition to the existing support for the S2? The S1 is already detected as a light, but the power metering sensors are not yet available through the API.

The S1 seems to be pretty much identical to the S2 with the difference being that the S1 can only switch one load up to 3600W by using a relay instead of two triacs (as in the S2). Therefore the S1 does not have the second output endpoint and the first one is of type Mains Power Outlet (0x0009).

Thanks,
Felix

@manup
Copy link
Member

manup commented Jun 15, 2018

Yes it's on the list and should arrive in the next versions.

@stale
Copy link

stale bot commented Nov 23, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the WONTFIX label Nov 23, 2018
@stale
Copy link

stale bot commented Mar 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 23, 2019
@stale stale bot closed this as completed Mar 30, 2019
@Thomas-Vos
Copy link
Contributor

The Ubisys S1 (Power Switch S1) still does not show its sensors for power measurement. It is shown in deCONZ but not in the API. Can you have this looked into, please @manup? We love to see this passed on in Hue Essentials.

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 1, 2020

@Thomas-Vos Seriously? Got the S2 (which is essentially nothing different) and that happily talks through the API... Code-wise, it's all there. Maybe you should put some juice on it and start sensor search again?

@Thomas-Vos
Copy link
Contributor

Hi @SwoopX, thanks for the suggestion. I have tried starting the sensor search again but unfortunately there are still no sensor resources created for the S1.

Here is the light resource:

{
    "etag": "f0885dedcfc1e2fb0e4c7d4cae760055",
    "hascolor": false,
    "lastseen": "2020-07-03T18:06:00.865",
    "manufacturername": "ubisys",
    "modelid": "S1 (5501)",
    "name": "Ubisys On/Off plug-in unit",
    "state": {
        "alert": "none",
        "on": false,
        "reachable": true
    },
    "swversion": "20200525-DE-FB0",
    "type": "On/Off plug-in unit",
    "uniqueid": "00:1f:ee:00:00:00:5c:04-01"
}

And here are some screenshots of the device in deCONZ:
Screenshot 2020-07-03 at 20 15 42
Screenshot 2020-07-03 at 20 15 57
Screenshot 2020-07-03 at 20 17 41
Screenshot 2020-07-03 at 20 17 56

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 3, 2020

Try the sensor search and read the basic cluster. While doing that, make sure a load is applied. Alternatively to reading the basic cluster, read the attributes of the electrical measurement and simple metering clusters.

@robertftvos
Copy link

@SwoopX Reading the clusters while doing a sensor search in Hue Essentials solved this issue. Also, the measurement value (mA) is now correct in your commit.

@7wells
Copy link

7wells commented Nov 1, 2020

Hello!

When I try to add the S1 to a new and empty group (latest stable phoscon gateway but old webGUI), I get this error message:

Warning! Could not add OG_Bad_Heizung to group. Group capacity of the device is reached.
The S1 device (named OG_Bad_Heizung) would be the first device in the new and empty group OG_Bad.

Can you please give me a hint how I can drill down the reason for this problem (and eventually resolve it)? Thank you so much!

@7wells
Copy link

7wells commented Nov 2, 2020

Well, it worked with the latest stable phoscon gateway and current webGUI. Sorry that I first tried the old webGUI and reported about a problem with it.

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

No branches or pull requests

7 participants