›
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.
Official Z-Wave CommunityApp

[APP Z-Wave] NEO Coolcam Z-Wave devices - Main discussion topic

12467…18

Comments

  • YvesGeffensYvesGeffens Member
    you can find a solution for this problem in this thread:

    Detect finished dryer or washing machine

    https://forum.athom.com/discussion/2673/detect-finished-dryer-or-washing-machine

    It's rather a long post, but it explains in detail how to tackle this problem (the repeating done-start-done messages).
  • WathLamersWathLamers Member
    thanks @YvesGeffens
    that was the place i told i was going to try anyway
  • DMKDMK Member
    @mruiter

    Just did as asked. Results <span>:smile:</span>

    com.neo running...

    [debug] ------------------------------------------

    [debug] Node: f84a970e-dc91-4158-912a-3e2ed0caabc9

    [debug] - Battery: false

    [debug] - CommandClass: COMMAND_CLASS_ZWAVEPLUS_INFO

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- ZWAVEPLUS_INFO_GET

    [debug] --- ZWAVEPLUS_INFO_REPORT

    [debug] - CommandClass: COMMAND_CLASS_SWITCH_BINARY

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- SWITCH_BINARY_GET

    [debug] --- SWITCH_BINARY_REPORT

    [debug] --- SWITCH_BINARY_SET

    [debug] - CommandClass: COMMAND_CLASS_BASIC

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- BASIC_GET

    [debug] --- BASIC_REPORT

    [debug] --- BASIC_SET

    [debug] - CommandClass: COMMAND_CLASS_ASSOCIATION

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- ASSOCIATION_GET

    [debug] --- ASSOCIATION_GROUPINGS_GET

    [debug] --- ASSOCIATION_GROUPINGS_REPORT

    [debug] --- ASSOCIATION_REMOVE

    [debug] --- ASSOCIATION_REPORT

    [debug] --- ASSOCIATION_SET

    [debug] --- ASSOCIATION_SPECIFIC_GROUP_GET

    [debug] --- ASSOCIATION_SPECIFIC_GROUP_REPORT

    [debug] - CommandClass: COMMAND_CLASS_ASSOCIATION_GRP_INFO

    [debug] -- Version: 1

    [debug] -- Commands:

    [debug] --- ASSOCIATION_GROUP_NAME_GET

    [debug] --- ASSOCIATION_GROUP_NAME_REPORT

    [debug] --- ASSOCIATION_GROUP_INFO_GET

    [debug] --- ASSOCIATION_GROUP_INFO_REPORT

    [debug] --- ASSOCIATION_GROUP_COMMAND_LIST_GET

    [debug] --- ASSOCIATION_GROUP_COMMAND_LIST_REPORT

    [debug] - CommandClass: COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION

    [debug] -- Version: 3

    [debug] -- Commands:

    [debug] --- MULTI_CHANNEL_ASSOCIATION_GET

    [debug] --- MULTI_CHANNEL_ASSOCIATION_GROUPINGS_GET

    [debug] --- MULTI_CHANNEL_ASSOCIATION_GROUPINGS_REPORT

    [debug] --- MULTI_CHANNEL_ASSOCIATION_REMOVE

    [debug] --- MULTI_CHANNEL_ASSOCIATION_REPORT

    [debug] --- MULTI_CHANNEL_ASSOCIATION_SET

    [debug] ------------------------------------------

    [debug] 

    [debug]  COMMAND_CLASS_SWITCH_BINARY->SWITCH_BINARY_GET args: {} cb: true

    [debug] ------------------------------------------

    [debug] Node: d0e7685e-ed65-49d4-8c96-e04f041fc129

    [debug] - Battery: false

    [debug] - CommandClass: COMMAND_CLASS_ZWAVEPLUS_INFO

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- ZWAVEPLUS_INFO_GET

    [debug] --- ZWAVEPLUS_INFO_REPORT

    [debug] - CommandClass: COMMAND_CLASS_SWITCH_BINARY

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- SWITCH_BINARY_GET

    [debug] --- SWITCH_BINARY_REPORT

    [debug] --- SWITCH_BINARY_SET

    [debug] - CommandClass: COMMAND_CLASS_ASSOCIATION

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- ASSOCIATION_GET

    [debug] --- ASSOCIATION_GROUPINGS_GET

    [debug] --- ASSOCIATION_GROUPINGS_REPORT

    [debug] --- ASSOCIATION_REMOVE

    [debug] --- ASSOCIATION_REPORT

    [debug] --- ASSOCIATION_SET

    [debug] --- ASSOCIATION_SPECIFIC_GROUP_GET

    [debug] --- ASSOCIATION_SPECIFIC_GROUP_REPORT

    [debug] - CommandClass: COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION

    [debug] -- Version: 3

    [debug] -- Commands:

    [debug] --- MULTI_CHANNEL_ASSOCIATION_GET

    [debug] --- MULTI_CHANNEL_ASSOCIATION_GROUPINGS_GET

    [debug] --- MULTI_CHANNEL_ASSOCIATION_GROUPINGS_REPORT

    [debug] --- MULTI_CHANNEL_ASSOCIATION_REMOVE

    [debug] --- MULTI_CHANNEL_ASSOCIATION_REPORT

    [debug] --- MULTI_CHANNEL_ASSOCIATION_SET

    [debug] - CommandClass: COMMAND_CLASS_ASSOCIATION_GRP_INFO

    [debug] -- Version: 1

    [debug] -- Commands:

    [debug] --- ASSOCIATION_GROUP_NAME_GET

    [debug] --- ASSOCIATION_GROUP_NAME_REPORT

    [debug] --- ASSOCIATION_GROUP_INFO_GET

    [debug] --- ASSOCIATION_GROUP_INFO_REPORT

    [debug] --- ASSOCIATION_GROUP_COMMAND_LIST_GET

    [debug] --- ASSOCIATION_GROUP_COMMAND_LIST_REPORT

    [debug] - CommandClass: COMMAND_CLASS_VERSION

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- VERSION_COMMAND_CLASS_GET

    [debug] --- VERSION_COMMAND_CLASS_REPORT

    [debug] --- VERSION_GET

    [debug] --- VERSION_REPORT

    [debug] - CommandClass: COMMAND_CLASS_MANUFACTURER_SPECIFIC

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- MANUFACTURER_SPECIFIC_GET

    [debug] --- MANUFACTURER_SPECIFIC_REPORT

    [debug] --- DEVICE_SPECIFIC_GET

    [debug] --- DEVICE_SPECIFIC_REPORT

    [debug] - CommandClass: COMMAND_CLASS_DEVICE_RESET_LOCALLY

    [debug] -- Version: 1

    [debug] -- Commands:

    [debug] --- DEVICE_RESET_LOCALLY_NOTIFICATION

    [debug] - CommandClass: COMMAND_CLASS_POWERLEVEL

    [debug] -- Version: 1

    [debug] -- Commands:

    [debug] --- POWERLEVEL_GET

    [debug] --- POWERLEVEL_REPORT

    [debug] --- POWERLEVEL_SET

    [debug] --- POWERLEVEL_TEST_NODE_GET

    [debug] --- POWERLEVEL_TEST_NODE_REPORT

    [debug] --- POWERLEVEL_TEST_NODE_SET

    [debug] - CommandClass: COMMAND_CLASS_MULTI_CHANNEL

    [debug] -- Version: 4

    [debug] -- Commands:

    [debug] --- MULTI_CHANNEL_CAPABILITY_GET

    [debug] --- MULTI_CHANNEL_CAPABILITY_REPORT

    [debug] --- MULTI_CHANNEL_CMD_ENCAP

    [debug] --- MULTI_CHANNEL_END_POINT_FIND

    [debug] --- MULTI_CHANNEL_END_POINT_FIND_REPORT

    [debug] --- MULTI_CHANNEL_END_POINT_GET

    [debug] --- MULTI_CHANNEL_END_POINT_REPORT

    [debug] --- MULTI_INSTANCE_CMD_ENCAP

    [debug] --- MULTI_INSTANCE_GET

    [debug] --- MULTI_INSTANCE_REPORT

    [debug] --- MULTI_CHANNEL_AGGREGATED_MEMBERS_GET

    [debug] --- MULTI_CHANNEL_AGGREGATED_MEMBERS_REPORT

    [debug] - CommandClass: COMMAND_CLASS_CONFIGURATION

    [debug] -- Version: 3

    [debug] -- Commands:

    [debug] --- CONFIGURATION_BULK_GET

    [debug] --- CONFIGURATION_BULK_REPORT

    [debug] --- CONFIGURATION_BULK_SET

    [debug] --- CONFIGURATION_GET

    [debug] --- CONFIGURATION_REPORT

    [debug] --- CONFIGURATION_SET

    [debug] --- CONFIGURATION_NAME_GET

    [debug] --- CONFIGURATION_NAME_REPORT

    [debug] --- CONFIGURATION_INFO_GET

    [debug] --- CONFIGURATION_INFO_REPORT

    [debug] --- CONFIGURATION_PROPERTIES_GET

    [debug] --- CONFIGURATION_PROPERTIES_REPORT

    [debug] - CommandClass: COMMAND_CLASS_BASIC

    [debug] -- Version: 2

    [debug] -- Commands:

    [debug] --- BASIC_GET

    [debug] --- BASIC_REPORT

    [debug] --- BASIC_SET

    [debug] - MultiChannelNode: 1

    [debug] -- CommandClass: COMMAND_CLASS_ZWAVEPLUS_INFO

    [debug] --- Version: 2

    [debug] --- Commands:

    [debug] ---- ZWAVEPLUS_INFO_GET

    [debug] ---- ZWAVEPLUS_INFO_REPORT

    [debug] -- CommandClass: COMMAND_CLASS_SWITCH_BINARY

    [debug] --- Version: 2

    [debug] --- Commands:

    [debug] ---- SWITCH_BINARY_GET

    [debug] ---- SWITCH_BINARY_REPORT

    [debug] ---- SWITCH_BINARY_SET

    [debug] -- CommandClass: COMMAND_CLASS_BASIC

    [debug] --- Version: 2

    [debug] --- Commands:

    [debug] ---- BASIC_GET

    [debug] ---- BASIC_REPORT

    [debug] ---- BASIC_SET

    [debug] -- CommandClass: COMMAND_CLASS_ASSOCIATION

    [debug] --- Version: 2

    [debug] --- Commands:

    [debug] ---- ASSOCIATION_GET

    [debug] ---- ASSOCIATION_GROUPINGS_GET

    [debug] ---- ASSOCIATION_GROUPINGS_REPORT

    [debug] ---- ASSOCIATION_REMOVE

    [debug] ---- ASSOCIATION_REPORT

    [debug] ---- ASSOCIATION_SET

    [debug] ---- ASSOCIATION_SPECIFIC_GROUP_GET

    [debug] ---- ASSOCIATION_SPECIFIC_GROUP_REPORT

    [debug] -- CommandClass: COMMAND_CLASS_ASSOCIATION_GRP_INFO

    [debug] --- Version: 1

    [debug] --- Commands:

    [debug] ---- ASSOCIATION_GROUP_NAME_GET

    [debug] ---- ASSOCIATION_GROUP_NAME_REPORT

    [debug] ---- ASSOCIATION_GROUP_INFO_GET

    [debug] ---- ASSOCIATION_GROUP_INFO_REPORT

    [debug] ---- ASSOCIATION_GROUP_COMMAND_LIST_GET

    [debug] ---- ASSOCIATION_GROUP_COMMAND_LIST_REPORT

    [debug] -- CommandClass: COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION

    [debug] --- Version: 3

    [debug] --- Commands:

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_GET

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_GROUPINGS_GET

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_GROUPINGS_REPORT

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_REMOVE

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_REPORT

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_SET

    [debug] - MultiChannelNode: 2

    [debug] -- CommandClass: COMMAND_CLASS_ZWAVEPLUS_INFO

    [debug] --- Version: 2

    [debug] --- Commands:

    [debug] ---- ZWAVEPLUS_INFO_GET

    [debug] ---- ZWAVEPLUS_INFO_REPORT

    [debug] -- CommandClass: COMMAND_CLASS_SWITCH_BINARY

    [debug] --- Version: 2

    [debug] --- Commands:

    [debug] ---- SWITCH_BINARY_GET

    [debug] ---- SWITCH_BINARY_REPORT

    [debug] ---- SWITCH_BINARY_SET

    [debug] -- CommandClass: COMMAND_CLASS_BASIC

    [debug] --- Version: 2

    [debug] --- Commands:

    [debug] ---- BASIC_GET

    [debug] ---- BASIC_REPORT

    [debug] ---- BASIC_SET

    [debug] -- CommandClass: COMMAND_CLASS_ASSOCIATION

    [debug] --- Version: 2

    [debug] --- Commands:

    [debug] ---- ASSOCIATION_GET

    [debug] ---- ASSOCIATION_GROUPINGS_GET

    [debug] ---- ASSOCIATION_GROUPINGS_REPORT

    [debug] ---- ASSOCIATION_REMOVE

    [debug] ---- ASSOCIATION_REPORT

    [debug] ---- ASSOCIATION_SET

    [debug] ---- ASSOCIATION_SPECIFIC_GROUP_GET

    [debug] ---- ASSOCIATION_SPECIFIC_GROUP_REPORT

    [debug] -- CommandClass: COMMAND_CLASS_ASSOCIATION_GRP_INFO

    [debug] --- Version: 1

    [debug] --- Commands:

    [debug] ---- ASSOCIATION_GROUP_NAME_GET

    [debug] ---- ASSOCIATION_GROUP_NAME_REPORT

    [debug] ---- ASSOCIATION_GROUP_INFO_GET

    [debug] ---- ASSOCIATION_GROUP_INFO_REPORT

    [debug] ---- ASSOCIATION_GROUP_COMMAND_LIST_GET

    [debug] ---- ASSOCIATION_GROUP_COMMAND_LIST_REPORT

    [debug] -- CommandClass: COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION

    [debug] --- Version: 3

    [debug] --- Commands:

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_GET

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_GROUPINGS_GET

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_GROUPINGS_REPORT

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_REMOVE

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_REPORT

    [debug] ---- MULTI_CHANNEL_ASSOCIATION_SET

    [debug] ------------------------------------------

    [debug] 

    [debug]  COMMAND_CLASS_SWITCH_BINARY->SWITCH_BINARY_GET args: {} cb: true

    [debug]  COMMAND_CLASS_SWITCH_BINARY SWITCH_BINARY_GET args: {} err: null result: { 'Current Value (Raw)': <Buffer 00>,

      'Current Value': 'off/disable' }

    [debug] get onoff

    [debug] get onoff

    [debug] get onoff

    [debug] get onoff

    [debug] get onoff

    [debug] get onoff

    [debug]  COMMAND_CLASS_SWITCH_BINARY SWITCH_BINARY_GET args: {} err: null result: { 'Current Value (Raw)': <Buffer 00>,

      'Current Value': 'off/disable' }

    [debug] node.MultiChannelNodes['1'].

    CommandClass['COMMAND_CLASS_SWITCH_BINARY'].on('report') arguments: { '0': { value: 3, name: 'SWITCH_BINARY_REPORT' },

      '1': 

       { 'Current Value (Raw)': <Buffer ff>,

         'Current Value': 'on/enable' },

      '2': null }

    [debug] node.MultiChannelNodes['1'].

    CommandClass['COMMAND_CLASS_SWITCH_BINARY'].on('report') arguments: { '0': { value: 3, name: 'SWITCH_BINARY_REPORT' },

      '1': 

       { 'Current Value (Raw)': <Buffer 00>,

         'Current Value': 'off/disable' },

      '2': null }

    [debug] node.CommandClass['COMMAND_CLASS_SWITCH_BINARY'].on('report') arguments: { '0': { value: 3, name: 'SWITCH_BINARY_REPORT' },

      '1': 

       { 'Current Value (Raw)': <Buffer ff>,

         'Current Value': 'on/enable' },

      '2': null }

    [debug] node.MultiChannelNodes['2'].

    CommandClass['COMMAND_CLASS_SWITCH_BINARY'].on('report') arguments: { '0': { value: 3, name: 'SWITCH_BINARY_REPORT' },

      '1': 

       { 'Current Value (Raw)': <Buffer ff>,

         'Current Value': 'on/enable' },

      '2': null }

    [debug] node.CommandClass['COMMAND_CLASS_SWITCH_BINARY'].on('report') arguments: { '0': { value: 3, name: 'SWITCH_BINARY_REPORT' },

      '1': 

       { 'Current Value (Raw)': <Buffer 00>,

         'Current Value': 'off/disable' },

      '2': null }

    [debug] node.MultiChannelNodes['2'].

    CommandClass['COMMAND_CLASS_SWITCH_BINARY'].on('report') arguments: { '0': { value: 3, name: 'SWITCH_BINARY_REPORT' },

      '1': 

       { 'Current Value (Raw)': <Buffer 00>,

         'Current Value': 'off/disable' },

      '2': null }

  • mruitermruiter Member
    Thx @DMK wil see what the problem is.
  • mruitermruiter Member
    @DMK, it actually looks good. The report shows both channels report on/enable and off/disable and also on channel 1 and channel 2.

    Did you do a re-pair of the device with the latest github ?
  • DMKDMK Member
    @mruiter did a re-pair with homey and used test flow.
    The flow works perfect as you can see.
    But when using the wall switch it is not working, but i think i know why.
    I want to use this wall switch as a "remote control" for my flow but that is not possible because this is a "switch" .
    So it does not send a signal to Homey to start or stop a flow that triggers another switch...

    Nothing lost however, will use these 2 switches on another location in the house.
  • mruitermruiter Member
    @DMK

    Just to check if i get it right....
    If you make a flow like. "When Bla then Turn On S1" and "When Bla then Turn On S2" it works ?
    But if you make a flow : "When S1 switched then "speak hoera" it doesnt ?

  • DMKDMK Member
    @mruiter not at home so short answer : when flow is tested from within Homey it runs ok and switches on lights and says text. When physically touching the switch to on nothing happens. 
    Thinking about testing it with better logic flow in the way that when S1 is switched to on start flow X or when S1 switched on set variable to light on.
    But have not much time to test the next days.
  • mruitermruiter Member
    But te main question. When you make a flow to flip a switch.. Does that work.

    So making a flow to start on a flip of a switch does not work.

    But making a flow that switches the switch does ?
  • ZperXZperX Member
    TedTolboom said:
    @ZperX thanks for the feedback. Settings are saved correctly; so that should not be the issue.

    Based on your description, I think it's an interpretation issue... where you expect that no motion alarm will be triggered if the illumination is above the specified Illumination level (39 lux)...

    The function as actually implemented into the sensors firmware (not driver or app) is that it will not send a switch on command to the associated device (e.g. power plug) if the illumination level is above the specified level.
    So if you e.g. associate a power plug to association group 2, it will only switch on if motion is detected with an illumination level below 39 lux and will automatically switch off after 181 seconds if no motion is re-triggered. 

    So this is different to the implementation used in the night mode of the Fibaro motion sensor; where also the motion alarm reports are surpressed by the sensor itself.

    I deliberately rephrased the parameters (and corresponding hints), compared to the Chinglish manual provided with the sensor, to the ones implemented in the app to avoid this misinterpretation. If you have suggestions to further improve, please let me know.
    @TedTolboom I been away. Thank you for your answer. However I don`t quite understand it. So how can achieve the same (or similar) "Night only" function with the Neo sensors? My dimmers are 433Mhz one so I can`t associate the sensors with these.
  • phil_sphil_s Member
    edited February 2017
    @mruiter have you seen this new neo pir sensor at aliexpress?
    http://s.aliexpress.com/MJjeaYvy

    seems like the new one. But where is the difference? Bad design or the higher price won't be the answer...

    do you know it?
  • TedTolboomTedTolboom Member
    @phil_s have been looking for more information on the Neo Coolcam NAS-PD02Z*.

    The only manual / more detailed description I'm able to find is at the FCC... but in fact this is the manual of the NAS-PD01Z* (no updated product ID mentioned). No registration of the NAS-PD02Z* at the Z-wave alliance.
    I've requested for additional information at Shenzhen NEO electronics.

    Based on the pictures at Aliexpress, I would guess it is (internally) the same motion sensor, with updated housing (facet style) and ability to have it ceiling mounted with the additional half-dome sphere.

    If I receive additional information, I will let you know.
  • mruitermruiter Member
    edited March 2017

     @phil_s i have one on its way. Somewhere on the train to Russia i guess.

    Info is already on https://fccid.io/Z52NAS-PD02Z
    Not yet certified by the zwave Alliance

    Dont start ordering yet, because when you order at the store you will not get a EU version but a US version.
    I got send a EU test version and there not selling the ZE version yet

    Neither does it have a temp sensor :s

    I was told its only the second revision and the new Production run.
    They did some small redesigns for better range wide angle on detection.

    Also the managed to cut down the Production costs to around 12,50 and will be selling them for 15 euro's to there distributors if they order large numbers. So we could expect a pricedrop again in the next months i hope.

  • phil_sphil_s Member
    wow thank you for your research @TedTolboom and @mruiter!
    just wondered because of its design and price at ali.

    ok, then we will see ;-)
  • fredskyfredsky Member
    Probably a stupid question.. I bought two Neo Wallswitches an installed the Neo-app, pairing went fine. In "settings" I can set "meter raportageinterval", but in the flow action-cards, I only get "turned on" and "turned off",  not the "energie changed" like shown in the washing-machine-flow. Am I missing something?
  • TedTolboomTedTolboom Member
    @fredsky stupid questions are the ones not asked...
    Dit you include the Neo wall switches with Lights connected to it or with other devices connected to it?

    Current limitation within Homey is that the Light class does not include power measuring / meter capabilities.
    The other class will provide these capabilities.
  • fredskyfredsky Member
    Thanks @TedTolboom!
    I didn't know that! Will try.
  • mruitermruiter Member
    Guess we are gonna put this in the readme, this question is popping up a lot lately .
    Other option is to put it into a custom mobile card. but then people cant add them as light anymore and homey will not include the socket in the ok homey all lights out or bla light out.

  • JulianJulian Member
    Someone from Athom replied to this exact question from me that they will change this in the not so long future (no detailed ETA, sorry) and that a wall plug can be configured as a light switch ánd that the power measuring capabilities are included. 
  • PacoSPacoS Member
    Cheap neo pir sensor at aliexpress.
    26,09 €
    https://www.aliexpress.com/item/-/32780283869.html?scm=1007.14594.75834.0&pvid=73dc459d-e799-4bdf-b4e1-72417cc4b7e4
    :-)
  • JulianJulian Member
    Question, I installed two NEO power plugs for my washer & dryer to get a notification when they are ready. The flows work without a problem, but I started to get a notification that one or the other was ready while they were off. When I checked in Insights the power spiked to more than 21 million watts (...) to -20.000 watts. Is that a known problem of NEO plugs perhaps or can it be that these readings are not being processed properly by Homey? This because it happens for both the plugs. 
  • mruitermruiter Member
    edited March 2017
    Not a known problem, guess a counter problem in homey.
    Others and myself are monitoring the washer.
    I monitor my 2 washers and 2 dryers and never had a strange reading like that. 

    But everything is possible. could also be youre washers is producing some weird feedback signal where the neo somehow gives a response to that caluclates the usage wrong. Does it happen always or just this once ?
  • WiepWiep Member
    I do observe the same strange readings as Julian , happens for me rather often, once a day.
    Can it be related that the power plug is on the edge of the Z-wave range ?
    I have ordered another power plug to put in the middle of homey and the washer.
  • JulianJulian Member
    edited March 2017
    I have two other NEO plugs, and I looked at the Insights and they also have the strange readings (+335.000watts, +42.000watts), and those are much closer to Homey. Still it is hard to tell if it is the plug that is broadcasting the wrong value or Homey itself does something to the values? My guess would be Homey (or the intermediate app?) since it would be quite a coincidence if four plugs all broadcast the same -wrong- power cinsumption. Then again, they are cheap Chinese knock-offs ;-) 
  • jimmy_zeropmjimmy_zeropm Member
    Today I received a neo socket. Installing to Homey went easy and at first everything looked great. But... when I changed it to different sockets it seemed to have an awfull range. (5 meters with no walls at best) and from all the on/off commands only 60% succeeded. That is quit bad.. 

    So is this the expected quality because it's  cheap Chinese clone? That would be a bummer, it tooked 7 weeks to get here haha. But if so, is there anybody who can confirm the Fibaro original is way better? In that case I'm done with this clone and will buy Fibaro's. But because they aren't cheap I would like to check it first.. 

  • JulianJulian Member
    I have two NEO plugs on the third floor and Homey on the first floor. No real issues here. I think they loose contact briefly at times, e.g. the status is incorrect but when I change them via Homey they respond immediately. I do have two other NEO plugs on the second floor, perhaps that helps also in the mesh? 
  • jimmy_zeropmjimmy_zeropm Member
    I have besides the neo one Fibaro motion sensor. How can I add or create a mesh? When looking in the network diagram I do see the motion connected to homey, and so the socket.

  • RuudvBRuudvB Member
    @jimmy_zeropm
    1 single NEO plug + homey is mostly (very) poor range. Several NEO plugs and other 240V powered devices makes a big difference, homey + the devices then build a mesh. 
    I had the same doubts when my 1st NEO plug arrived :)
  • jimmy_zeropmjimmy_zeropm Member
    edited March 2017
    @RuudvB, so I can try to add a fibaro one and mix things up? The battery powered fibaro motion detector won't do because it's battery powered.
  • TedTolboomTedTolboom Member
    More devices will build a stronger mesh. My advice is to add the devices at their intended position (and move Homey temporarily to that location)... a bit more cumbersome but during initiation the device will discover the nodes around him and build it's route (including direct line to Homey).

    I'm not able to do a direct comparison, but common feedback here is that the range is equal to the Fibaro's
Sign In or Register to comment.