[APP][Pro] HDL Smartbus

hi Andreas, my dimmer/ballast controller works 100% Thanks.
A more serious problem is that my wife is not on speaking terms with our Google Assistant, I do not quite understand, possibly the fact that I chose a sexy female voice, and the fact that in these Covid times I actually spend more time speaking with the assistant than her :wink:

There are probably others in my situation who want to be able to turn off the light with the good “old” DLP switch, instead of shouting and arguing with Google.

Is there any possibility for you to implement the DLP switch? (I’ve seen it been done in another APP)
One of the problems with DLP is that the status light on the switch does not change when you change the status of a relay, dimmer nor does it when you run “Flows” from Homey. It only changes status when you use another DLP

mvh
Tor Oskar

I would be nice to implement panels as HDL Devices directly, but for now it works ok with HDL Universal Switch.

On Homey side:
Add HDL Universal Switch (Any number lets say 1 for this)
Make flow:
When HDL Universal Switch (1.1) Turned ON
Then Light Toggel on or off

On HDL Side:
Make the button, for example Momentary (240 Is my Homey HDL Device ID)
1 1 240 Universal Switch 1(Switch no.) ON(Switch Status) N/A N/A

When you press any HDL button, it will turn on HDL Universal Switch, when you release it will turn off again. When you press again it will trigger.

This is the quickest way.

When you can start with scenes, relative dim, multiple buttons, long press double click ++

Hi Eivind
Thanks for reply. I do not quite understand what it is that I do when I use UVsws, it works fine when I test the “Flow”, seldom rarely does it work from Google Assistant, and the change is never captured by HDL. It looks like the switch is living its own life on my net / bus at the moment :slight_smile:

Are you really using the virtual Homey HDL Device to handle your UVsws? I use the logic module, is that whats wrong? How do you pick them up in Homey?
Tor Oskar

Hi all, new to homey and new to the forum. First up, great job with the app, has breathed life back into my HDL set up.

I have managed to use UV switches to solve most of my challenges, but I have to admit I don’t really understand your reference to 212 as a default, nor the setting in the app, seems to mean 212 does not appear as a device when I add universal switches to homey. I am probably missing something but anyway, have set up a bunch of UV switches which are now triggered by various events on in my sensors. Homey only finds one type of sensor, but doesn’t matter because homey acts on the UVs.

One thing I can’t work with which might be a future feature is temperature. My sensors are in the panels and switches which I can’t pickup. Not a big deal as there is no driver for the heating controls anyway and i can leave this to the HDL setup.

Thanks again for great work :slight_smile:

Thanks Robin! In general, I must say that the implementation of the Universal Switches are not my proudest moment :slight_smile: HDL is a bus, so there are a couple of short comings in how communication is done, and it shows in the UV implementation. Given that there is nothing specific device I can ask for the status of the UVs (to my knowledge), it becomes a matter of catching signals, and the state will be lost every time something happens with the Homey etc. Any ideas on this is very welcome, both in text and in code if somebody wants to contribute.

About the temperature: You mean in the DLP panels?

Andreas

Andreas, the UV switch functionality works just great for everything I have tried so far (not that much perhaps). I just use the state change I want in the UVS to start a flow, I can’t think of a problem I won’t be able to solve as yet. Only wondered if you had something cleverer in mind.

There are temperature sensors in both the DLP panels and some of the 1/2 button multi function panels. Again I don’t think I have a real need to pick up the info and could always use a UV below or above a certain value. The floor heating module itself is a complete mystery to me and seems to have a mind of its own so don’t think I will be messing with that any time soon.

and as to programming help, I am not sure my 90’s Cobol skills are going to take this thing very far forward :slight_smile:

Hi Andreas, Im buying Homey and have HDL BusPro.

I would really welcome the opportunity to control the heat in the house with Homey. I have an HDL thermal module HDL-MFH06.432. I think I will definitely be able to perform any tests and help with development, but unfortunately I am not a capable programmer enough to put my hands directly to the work.

Is it realistic to add a heating module by HDL to Homey?

It is definitely realistic to add it, and from what I can see the underlying library I’m using to communicate with the bus supports the heating modules. I can give it a shot and publish the app as a test/beta, and you can try it out in your home.

Andreas

It will be perfect! Let me know after you add it and i will test it. My Homey will be arrived tomorrow.
Many thanks!

Hi Andreas, can you help me with setup? I have homey now at home. Im installing HDL app and trying to set up. IP address, subnet no problem but what do you mean with: THIS APPS ID IN HDL SUBNET? What this apps? I have no homey apps id in HDL…Cannot find more info :frowning:

EDIT: Ahh, its new ID… understnad now… :slight_smile:

1 Like

Hi Andreas, how are you? Did you try to include HDL heating module into Homey?
I have another wish :slight_smile: what about HDL-MSD08.40 4 Zone Dry Contact Module and HDL-MSC06.432 6CH input & output Module. Is it possible to add to Homey?

Hi there! I’m having a bit of trouble understanding how the floor heating unit works (I don’t have one myself). From what I can see in the protocol, it seems like you don’t actually turn anything off or on, but rather set a temperature for the unit to keep. You can specify different temperatures for day/night/away etc. Is my understanding correct?

I don’t know how protocol looks inside, but you can trun on and of in GUI - look at images from APP.



Language is Czech if you want translate… :slight_smile:

P.S.: Temperatures are for testing… :slight_smile:

OK, so basically we are talking about 6 thermostats. Do you turn them all to the same mode at the same time? So all to day/night/normal/away, etc?

Hello, sorry, I missed your message! :frowning:

So, basicly I want but cannot. For now I can set mode for every thermostat separately. Cannot set it for all together now.

I can switch every of them to status ON and OFF. But when status is on, valve can be closed in depend on teperature. For example in the image - Status of thermostat is ON but status of valve is CLOSED. Mode si set to NORMAL.

If it helps at all here is what the configuration screen looks like in the buspro setup tool. As I understand it in Full Control mode (top middle) it receives target temperatures (right hand side) from a DLP (mine only uses normal and away, there is a setting else where that allows all 4). It picks the ambient temperature from one of the sensors or switches with a sensor as specified in the by device id and channel (in this case 26, 1). It then controls the valve (bottom right) open or close. In slave mode it just acts as an on/off switch (open/close valve) and needs to be controlled by a DLP (not tried this)

1 Like

Hi Andreas, do you have any progress? Can I help you with anything?

Andreas if you need some components, let me know. I have some you can have and some you can borrow. I have almost everyting!

@horakmar and @Eivind_Bo: I’m pretty much stuck with this as I haven’t got one of these units myself. I’ve started a branch for the code, and found the part of the library that addresses the communication (smart-bus/commands.js at d783e67ffbe372217f9598547831a82fa13439c4 · caligo-mentis/smart-bus · GitHub), but I can’t figure out what the “work” part of the message is without a unit. Either, this needs to be tested by someone who has a unit or I need a unit to test with. Basically, we need the controls from the link above to be mapped with the controls for a Homey Thermostat (that is basically just thermostat_mode (auto/heat/cool/off) and target_temperature.

As this is a spare time project, and I haven’t had any spare time or the need for a floor heating unit myself, this hasn’t been on the top of my list of priorities. I’m hopeful that some more time is going to appear together with the sun as spring approaches.

Hi Andreas. I will try to build branch on my local. In the meanwhile… Can you look to the code at dry contact?

https://b2b.hdl-automation.cz/en/products/buspro/dry-contact-inputs/hdl-msd08-40

DOCS: https://b2b.hdl-automation.cz/en/downloads/products/manuals/buspro/dry-contact-inputs/m_hdl-msd04-40(dry-contact)

I have full house of those swtichers. It is simply switcher with 8 inputs. I can set target for every input. For exaple: With one module, I can switch lights with 8 swtichers.

Here is setting from HDL app.


I NEED ONLY THING - GET CLICK EVENT TO HOMEY. Not settings targets etc… I want set targets by flows in Homey. For exaple - When ID 4 on module clicked, then start another flow… If you understand :slight_smile: