Hello Chris
Please excuse me for being so ignorant when it comes to Smarthome, Homey, Slack etc. And what certainly doesn’t make it any easier is the fact that my English is rather poor.
Because if I’m interpreting your answer correctly, you’ve completely misunderstood me, otherwise I can’t explain your anger.
Please understand that not everyone can be equally gifted when it comes to technology, and from my point of view you also have to take into account that the Homey system is intended to appeal to a wide audience. In any case, this is how it is advertised by Athom. In other words, people like me come along and ask questions that are probably nonsense for you as a long-time Homey user and talented programmer. But if you’ve only been doing this as a hobby for about 1.5 years, then there’s more uncertainty than certainty.
It would be desirable for less technically experienced people to be allowed to ask the relevant questions. Because I am convinced that there are also topics where you do not know your way around and would like fair support.
My intention was never to attack you in any way, but my ignorance of the context, combined with my poor English, has probably led to this.
Now I would like to make the following factual comments on your answers.
If I am technically ignorant, then I can’t find a bug in the source code, apart from the fact that I don’t even know where I would find it.
I didn’t know what Slack was until today…
I have now checked this, the movement messages appear both in the device timeline and in the Heimdall app. I didn’t realize that I could conclude from this that the fault lies with Athom.
Thank you again for the great app and I hope to be able to count on your support in the future.
Hello Chris
I really hope that I don’t bother you too much with my question. But unfortunately I can’t get any further on my own.
I have a thing whose motor and light as well as LED and buttons I can’t get into the Homey. I got every other Dingz switch in Homey without any problems.
When selecting the Dingz switch, I can select the Dingz switch in question. can then also open the web UI from the import process. But when I go further it always says that there are no new devices. I checked and these devices are nowhere in Homey.
What could be the reason?
On the switch there is a light at output 2, at outputs 3 and 4 there is a motor. I have set that on the base with the switches. The firmware on the switch is 2.1.1. In the Homey I have the app 1.3.1
I don’t know, I don’t have enough information from you. The only thing I can help you with is, have you read the notes, because everything should be documented there ?
BDW: I would recommend you to use the test version either way. Because it supports more dingz device types, is more stable and you will have to update to it after the next firmware release.
Hi Winch. I have the same Problem. If the Dingz Button controls local. I can turn a connectef light on and the homey app reacts and shows that the light is on. As soon as i turn it off homey says still light is on, but its turned off. How could you solve this Problem? I tried everything. Happy to hear. Regards Jan
Just a minor detail I realized earlier this week. In my installation (using the latest test version 2.0.6) I don’t see the temperature in the “climate” overview of the devices.
I assume that’s the same root cause as the already lengthy discussed activity of the zones which somehow homey cannot map correctly. Same as with the activity, I see the status and history within the device itself without problems.
For classification: I don’t see much of a use case for myself which is limited because of it. Just wanted to share the finding (or verify if it may work for other users)
I initially used the app version V1.3.1. Everything worked perfectly with this, except that the blinds are shown as closed in the Homey app when they are open and vice versa. So I removed everything and restarted completely according to your instructions with V.2.0.6. Unfortunately, I can’t get the dingz to work.
Strange, but you have changed the user/password (no longer the default dingzNet/dingzNet), because it looks like you have no authorization in the broker.
BDW: I noticed that the user in the broker is called “dingzNET”, is that correct?
Now it works. I had to adjust the IP according to your printscreen. Localhost does not work and under Notes you wrote the following IP:
If you use the Homey MQTT-Broker, then it is sufficient to enter the URL “localhost” or “127.0.0.1” at MQTT-Broker settings, because the rest is done automatically by dingzNet.
The original problem I had with V1.3.1 is unfortunately still there. The blinds display in the Homey Dingz app does not match the Dingz app. Dingz shows that the blinds are up, Homey shows that they are down and vice versa.
Thank you very much for your support and maybe you can solve the display problem with a fix?
About your other problem, but I’m not an electrician, but I suspect the cables are connected incorrectly.
Try the following, in the switch config of the motor, you can negate the running direction, that should help in my opinion.
I have already tried your tip about inverting. I have redone the wiring myself. It’s always the same in the Homey, it’s different to the Dingz. But maybe it’s because I still don’t have 100% access to Dingz via Homey.
@Adrian_Schmid
In my case, the DingzID was not the correct MAC address for the Dingz. This caused me problems with 2.0.6.
ev mal in den Einstellungen kontrollieren
!
