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
I have not connected anything to the two outputs yet, I have only connected mains to the input to pair and test the switch. Neo App v1.1.20, Homey Firmware Versie: 1.2.0
- Pairing went smoothly:
The Switch shows up as node 45 in my z-wave mesh:
If I press the left or right button, I hear the switch 'clicking' and the leds on the switch change colour. So, I presume it works...
If I try to operate the switch via the web interface of Homey, sliding the switch, does not do anything with the NEO. Tried both the left and right sliders. Nothing happens. The reverse - activating the switch manually - does not update in Homey's interface either.
I made a test flow, and that returns an error:
I don't know what I am doing wrong.
Any suggestions?
Thanks!
PS
I PTP, that didn't solve the issue.
I installed the latest NEO App - version 1.1.21 - via CLI, still no luck....
UPDATE
I removed the power from the NEO switch, but the device is still available in the Homey interface and the switch sliders can be moved, without getting an error. I find that strange! I thought an offline z-wave node should not be available in the interface? I can even access the NEO settings menu and update the NEO Switch and get a confirmation. But, the Neo is not even connected to mains ???
v1.1.21 has been released to the app store: https://apps.athom.com/app/com.neo
Change Log:
v 1.1.21
fixed:
NAS-AB01ZE - Add action card for setting alarm or doorbell tune
NAS-AB01ZE - Fixed alarm state action card
On a distance of 3 meters, this should not matter, but the sensor on 7 meters might stretch it... especially if walls are in between. Adding some, non battery powered, Z-wave devices should create a strong mesh and extend this reach.
In addition, a known issue with 1.1.9 is that reports provided by the devices are not processed correctly all the time.
1.2.0 which is about to hit stable should improve this.
When I added and debugged the Neo touch switch driver, I only had one load connected to the touch switch and bot switches worked ok... I don't know what happens when no load is attached.
What is the error code mentioned when trying to activate the switch through your test flow (hoover over the red triangle to show it)? What does the Z-wave log show during this action?
Regarding the update. At the moment you remove the power of the Neo switch, all controls / settings will remain active.
This is not wrong (or right)... toggling the switch, with the device powered of, will change the state of Homey...
Updating the settings and getting a confirmation is incorrect... most likely there is only a check for battery powered devices if they are only and not for net powered devices (which are allways online)... the confirmation should however be based on feedback of the device... without a device it should not get this confirmation and provide an error.
Can you create an issue on this one?
I will take a look into the common Z-wave driver in parallel...
No load attached could also mean that a lightbulb is attached and that the actual bulk in broken. I guess (..) that the status of the NEO Switch should still be correct and that switching On/Off should be possible...
The error in the flow is: Error: invalid_type_expected_number ["Switch Value"]
The z-wave log shows these items for NODE 45 ..... when I press the buttons on the switch:
When I slide the sliders in the web interface NOTHING is logged.
PS
I am new to creating issues (hehe)... I will have a look on how to do that!
PPS
I removed and re-paired the NEO Touch Switch to see if that would solve the issue. It did not...
I guess something went wrong during pairing.
Can you try to
- remove the touch switch from Homey
- reboot Homey
- wait 15-20 minutes for Z-wave to be fully up and running (can check that at Z-wave settings, the processSendData is empty
- reset the switch to default (press the left button more than 10 seconds)
- re-add the touch switch at close distance to Homey (move Homey if needed)
Thanks for your effort!
I did what you wrote. Removed, reset, re-added. Still no luck.
The switch is added without any hick-ups and seen as Node 47 in the z-wave mesh.
I will remove the Switch again, reset it and restart Homey, but pair the switch tomorrow.
The error message (Error: invalid_type_expected_number ["Switch Value"]) you showed earlier would point to a cause that you accidentally used an older version of the app (< v1.1.19), where "Switch Value" was still used in the driver and where the Touch Switch was not working.
With the updated app, tested ok on the Touch Switch, "Switch Value" has been replaced in the driver by "Target Value".
Can you install the version now in the app store (= v1.1.21) and try if this works?
This is what Homey states as being installed (via CLI):
I have just installed via the App store:
And will re-pair NOW
UPDATE => still no luck :-(
Tomorrow I will add a load to the outputs. That is the only thing that I have not done yet.
Thanks for the confirmation!
I still get the error:
PS
I even checked the box; I do have the EU version....
apparently you have a different version of the switch, your binary switch (command class) version is 1 (confirmed by your data log: 0x142501), where the version of all the others are version 2.
is there no difference in product id's?
This is the information:
It gets added to Homey without an error and is 'update-able' too.
Would that mean that my switch needs a different driver?
@Rocodamelshe
The error in the flow is: Error: invalid_type_expected_number ["Switch Value"]
Same as before.
Well spotted!
Unfortunately, it also uses the same product ID... so a different driver would not work (due to the same product ID which is used to identify the right driver)..
Only option would be a SET and REPORT parser that is able to distinguish based on command_class version....
would need to look into that one..
PS
As I seem the only one with this odd Touch Switch, perhaps I should just sell it....
Where did you order these touch Switches? If you have two, there will be more... bumping into the same issues...
We'll look for a solution...
I won't have much time in the first half of this week.. but I can make a dedicated V1 version later this week...
A dedicated Neo Switch V1 driver would be awesome!
Would that mean a separate folder in the 'driver' folder for the V1?
Or would that mean a total new App for just the V1 switch?
I am asking this, because I also have other NEO Coolcam stuff, and it would be nice if the App would remain App store updateable. I could manually add the v1 driver into the driver folder.
I bought a set of door sensors and was getting frustrated that they didn't get recognised. In the manual is written that you can keep the button pressed for 10 seconds (until the light is red), then release the button. After that, piece of cake to connect them. App works great as well!
The Neo Touch Switch was bought about a month ago, on the 28th of March at AliExpress. Some days before that, I ordered 2 Neo Coolcam powerplugs. These have no driver issues :-)
Good to read. My other Neo stuff works great too!
The issue with my Touch Switch is known, thanks to @caseda and @TedTolboom
A solution - two different drivers for the two different Touch Switch types - is 'in the make'.
https://github.com/TedTolboom/com.neo/tree/TouchSwitch_V1
Can you check if your touch switch is working not (listening and reporting)?
We were on our way out, but I couldn't resist to give it a brief test....
I quickly installed your App, removed the NEO Switch that was still installed, re-added it again via your App.
Manually switching the switch, updates in the web interface :-)
Switching the web interface doesn't switch the Neo Switch :-(
I step forward already !
BTW no load on the outputs!
Will test again tomorrow. Also after a PTP!
Thanks so far !!!
Should not be needed to remove and re-pair the touch switch; update app and it should be working
Just checked the latest App. It's working!!
Thank you!!
PS
Can I update this version with future Neo App releases?
But will need some support from you @Eternity and @CliffBroeren to test is with both versions...