This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Official Z-Wave CommunityApp
Comments
As an alternative I was thinking, why not give homey a sort of UPS... This way homey can be carried around and does not have to be restarted. I guess everyone has some kind of powerbank lying around? Would this work? I did not test yet, no idea how much power homey needs.
Other thoughts? Suggestions?
Ik heb een NEO Touch Switch en Die werkt nog niet goed met homey
The bad part is I cannot find a "white" version anywhere..... Already done a lot of searching.
Does Anyone know a store where they sell white Y-cables 1x USB-A female, 2x USB-A male?
https://nl.aliexpress.com/item/USB-2-0-Female-to-Dual-A-Male-Extra-Power-Data-Y-Extension-Cable-for-2/32739065897.html?spm=2114.010208.3.1.loqMva&ws_ab_test=searchweb0_0,searchweb201602_0_10065_10068_10136_10137_10138_10060_10062_10141_10056_10055_10054_128_10059_10099_10103_10102_10096_10052_10144_10053_10050_10107_10142_10051_10143_10084_10083_10080_10082_10081_10110_10111_10112_10113_10114_10037_10032_10078_10079_10077_10073_10070_10122_10123_10124,searchweb201603_0,afswitch_1,ppcSwitch_5,single_sort_0_default&btsid=68bd2159-89b2-40c4-b087-9775b0ab5511&algo_expid=9c75c9bc-fb10-4e8f-ba9a-6ddd88ca6bab-0&algo_pvid=9c75c9bc-fb10-4e8f-ba9a-6ddd88ca6bab
Thanks for your great work!. I can confirm Neo Touch Switch is not working. In homey it shows as 3 devices. 1 is Neo Touch switch, other two are both named right switch. How can I help? Switch is not responding.
(double post already reported but as comment in appstore but here I can upload pictures)
Lourens
https://apps.athom.com/app/com.neo
Thanks to @CliffBroeren, who provided me his touch switch, I was able to find and solve the issue. Over the weekend, I will finalize the update, including reduction to two devices and action card to disable the LED by a flow.
I am noticing that the switch has very poor Z-wave range and is not becoming a part of the mesh. Would that be solved in your new driver or do I have a defective switch?
Range is typically determined by the position and distance of the device wrt Homey, the structure of the house, contributing (other Z-wave) devices that are able to route (e.g. not battery powered) and disturbing devices (broadcasting at a similar frequency)... Can you provide more info on your setup?
Thanks!
Thanks @JBS
The Github repository has already been updated (updated driver, app and icons for the Neo touch switch): https://github.com/mruiter/com.neo
It also includes the action card to enable or disable the led of the switch.
Tested the driver and app to be ok with using the Touch Switch of @CliffBroeren
Will bug @m-ruiter to test the Siren update and push it through the app store
Lourens
But then, I'm dying to get the two devices to work properly. I have relocated Homey so it can clearly 'see' both devices. The first is 3 meters away, and works 80% of the time. But the second which is 5 meters away and in a direct lineup with the first device is only working about 10% of the time. So worthless. What can this be? I'm trying to understand what's happening, because if it sometimes works, the range is working at that moment. Homey is replaced outside of speakers, tv's etc and is sitting completely clear. Both plugs won't report more then on or off. So no load, currency etc. Both were paired with the 'other device' selected as connected to the plug.
Also I notice that in the zwave chart the decives aren't connected with a line as does the fibaro motion sensor does and they aren't connected in between. In other examples of users here I see perfectly connected webs...
First the meaning of the LED lights:
So the LED blinking yellow would mean that it is being added to the Z-wave network.
What you could try is to do the following:
1. remove the devices (power plugs) from Homey,
2. reset the devices after they have been removed from Homey:
3. install the first plug (closest to Homey) it at the intended location
4. disconnect Homey and move it to that location and turn on Homey again
5. pair the device with Homey again (and repeat as of 3 for the remain devices)
I tried to remove the device from Z-wave and add it again. I got a new node# so this worked. Adding this to a flow again, still no sound...
I'm using the card "Verander de alarm toestand" -> Alarm luiden.
In earlier app versions it worked perfectly. I only noticed this recently since my alarm does not go off to frequently
I would like to create a flow that switches a socket but also does a control run if it actually switched by checking the current or voltage. If there is Homey may assume the socket switched and vice versa. But with no readings indicated that isn't possible I'm affraid...
Will push the update to the app store, but don't expect it to be released during Easter.
For the impatient ones among us, the update is available at my Github repo and can be installed through the CLI
As bonus, I've added two additional action cards to be able to change the alarm and doorbell tune from within a flow.
See below screenshot made by @lubbertkramer during testing:
Changelog:
In about 2 hours after me reporting the issue, you guys found the issue, created a fix and tested it.....
Great work!! I will wait patiently for the update Enjoy the Easter weekend.
If you put the plug into the socket, it will blinck pink 5 times sending the node info.
If you press the button, and the devices is free of associations, it should blinck yellow 5 times.
If you want to add the power plug to Homey, my advice would be to insert the power plug in the wall socket close to homey, open the 'add a Z-wave device' window showing 'put your device in learning mode and triple press the button to put it into learning mode.
Putting the power plug into the wall socket will also send the node info (triggering the inclusion proces), but is not really reliable.
Devices working more reliable from day to day can be contributed to creating a mesh which takes some time.
It should not be necessary to add a control mechanism; this is a build in feature of Z-wave... if a command is send, the device will send a acknowledgement of receipt, directly afterwards it will send an update of its state (onoff and power state)...
if it is not sending this report (Homey updating the state), there are multiple causes..
- range too big / mesh unreliable > does it provide updates when Homey is at a closer distance?
- something went wrong during inclusion > at what distance did you include the power plug? Did you include them as advised in the first section of this comment?
- driver / app issue > would be an issue for multiple people (including myself)
What still remains is the data of the four sockets that isn't coming thru. Watt, voltage etc.
My idea of the control run was becuase of the unreliable outcomes. I have an espresso machine that needs to warm up 40 minutes. Sometimes when I go home (ad hoc) from the office I'd like to switch it on in advance. So I thought, when homey sees no power change or watt levels, it should fire again, untill it works.
Thanks for the great help here, and developing this app! I'm just trying to learn and appreciate all your work guys!
Can you check the Z-wave log (Settings > Z-wave > Stuf for geeks) and see if there is a node ID that is creating a large amount of traffic (lot of lines with the same node ID mentioned)?
Did you also do a reboot of Homey after including the devices?
Example;
The map is not updated in realtime... I also have a device floating / not connected, still it is providing the right reports / reacting to commands send by Homey.
The distance to homey is about 3 meters for the door sensor and 7 for the motion sensor. The problem is that a lot of the time the contact alarm and movement detection stay stuck on yes on the homeycards in te app. When this happens the devices won't be triggered by motion or opening the door.
As a result a lot of flows fail to be triggered. Anyone has an idea what could be the problem? I haven't changed the settings from the door sensor and changed the motion sensor to detect motion again after 5 seconds. I'm using homey version 1.1.9.
Thanks in advance.