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.
[Z-Wave] NodOn [v 1.1.0]
Initial Post for the brand NodOn.
App Store
Github
I have the NodOn Octan Remote, and it still needed an app, so have created one.
Update: 02-09-2016:
- 1.0.0 Has been approved and is published in the app store.
- Update 1.0.1 (add support wall switch) has been accepted.
If you have a device from NodOn that you want included, just ask for it, and i will (try) to include it in the app.
App Store
Github
I have the NodOn Octan Remote, and it still needed an app, so have created one.
Update: 02-09-2016:
- 1.0.0 Has been approved and is published in the app store.
- Update 1.0.1 (add support wall switch) has been accepted.
If you have a device from NodOn that you want included, just ask for it, and i will (try) to include it in the app.
Comments
i have added the soft remote, it will be available as soon as it is accepted in the store
As far as I know the soft remote, the wall switch and the Octan remote are (almost) identical software wise. Except for things like the product ID.
Thanks in advance..
The only big change is the icons and images.
So will add the wall switch as well.
Will be added after it has been accepted in the app store, and the update for this addition has been accepted as well.
Update 1.0.1 that adds support for the wall switch has also been submitted for approval
I have one question: does somebody knows how to make the dimmer dim up or down when the button is constantly being pressed?
https://github.com/athombv/homey/issues/833
Node 5 and node 6 are everspring dimmer plugs. But this configuration doesn't work.
1,1,2;2,1,2;
Are you suggesting that the only way is to control the lights using a flow?
What do the Raw parameters mean? And why do they magically make everything work, even changing dimming level on long press!! Thanks!
In the current way I've implemented them, homey will not trigger ANY triggers anymore, besides it being in the Scene mode it's in by default.
if i had implemented the setting already, and people change it, they will definitely complain that it doesn't work anymore
the occasional someone that want to use it as a dimmer, will come here and are then being told it doesn't trigger inside homey anymore, and can do it easily with raw parameters.
cause even if i put that in the read me, they won't read it anyway
in the future i will add both other ways of triggering into homey. just too many thing to be implemented (and fixed)
all basics first, extra's later
the not being able to double click because it's in DUO mode (that's what dimming mode is called) is because that's the way the remotes work
it's either, being able to use,
single, double, hold and release
or
MONO (every button can be pressed once)
or
DUO (dimming mode)
no "and, and" possible unfortunately that is not something i can do anything about...
well maybe with a workaround, an action card ([THEN] column) that lets you switch the mode, (and then wake up the remote...) but you will have to flow trigger that on every mode you use
maybe will implemented that in the future as well
This version includes all zwave devices nodon still has left (smart plug and micro smart plug)
Fixed a core change that made the settings save button disabled, the reason has to do with the wakeup interval that should only be 0.
Added battery alarm capability to the 2 remotes and wallswitch.
to be able to use this function you will need to re-include it to homey.
But this is optional, so if you don't need /want the capability you don't have to do anything, it will keep working just fine.
Also added the settings for the remotes and wallswitch to use them better in direct associations (single and dual button control)
This includes flow triggers but is way more limited then scene control (default way) nothing I can do about that unfortunately.
Tested everything thoroughly, but if you still find something that doesn't work as you expect, don't be shy to let me know
If that does not work, on which step does it timeout
Do you have it within 2 meter of homey and are you able to delete the device from homeys settings -> z-wave?
If not, were/are you able to add more zwave devices to homey?
If you can, then there is a big chance you don't have the proper zwave frequency or the device is broken
If you can not (or don't have more zwave devices) then it can be your homey that is faulty.
I try to connect the wall swich at within a distance of 50 cm from my Homey.
I have connected two other z-wave switches from Fibaro. These work properly.
on the box there from the nod-on wall-switch is z-wave+ mark. Can that be the issue?
Frequency is talking about the mhz it is sending on, this is different for different parts of the world.
Not sure if there is a frequency on the box, or if nodon even delivers other frequencies since it's a pure French company.
But that is why I asked for the remove device in homeys settings -> zwave.
If that doesn't give the message that it successfully has been removed, but states that it couldn't find a device to remove, then your switch is dead or the wrong frequency.
If it does give the message that it was successfully removed, then it should include just fine.
Maybe try a reboot of homey before trying again.
Then I am more then happy to add it.
But both nodon and the webshop robbshop.nl cannot give me this information, but gave me the answer that the zwave version of the (big) plug does not support power metering
Only the enocean and micro support it
Remco, here are the screenshots.
1. Excluded the unit
2. Tried to include it again but got the message "Something went wrong" (or something similar)
3. Excluded it (even though it didn't include earlier)
4. Factory reset the unit ( by holding button 3 and 4 until the blinking of red and green)
5. Included it again with a successful inclusion.
It works perfectly fine for now
Shouldn't be happening thanks to the way it is implemented.
Oh well, for everything a first I guess, happy that it works for you know, let me know if it happens again, then it needs a fix in the core probably.