I think it would make sense to define a own room habridge for habridge in FHEM where the user has to add all FHEM-devices, that should be exposed to habridge. Then you could retrieve them by:
http://usr:pwd@FHEM-IP:PORT/fhem?cmd=jsonlist2%20room=habridge

What you're going to receive is a full HTML document. But inside the div with the id content you'll have a nice JSON, that lists all devices as single entities. There are going to be lots of parameters, but actually you don't need more than Name to build the controller URLs provided an hour ago.

Additionally you could use PossibleSets, which tells if there is e.g. on and off only or also dim (-> habridge ${intensity.percent}) and RGB (-> habridge ${color.rgbx}). Depending on PossibleSets you could either allow on/off only, or also dimming and coloring.

In Readings you could also read current status of devices in FHEM and refresh them in habridge, but at least in my setup this isn't important, as FHEM remains the leading smart home engine, that has logic depending on the device states.

Here's an example for a sample habridge room with two devices DeckenlameLinks (coloring + dimming supported) and Arbeitslicht (on off only). The JSON begins in line 152.

FHEM home automation integration #675

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions