Key Notes below – Please watch the Video below for Installation support.
Why use this integration?
- Seamless Integration of the Neo controller to the shades service with scene builds enabled.
- Blinds/curtains present in the pro app in the Shades service as a dimmer slider – 0-33% will trigger down and the slider will then snap to 0% – 34-66% will trigger stop and the slider will then snap to 50% – 67-100% will trigger open and the slider will then snap to 100%.
- Neat has only tested the Neo controller with Alpha motor blinds. One way communication only. Savant ‘thinks’ motors are two way hence scene builds are enabled.
Neo Driver Installation Notes
Watch this video:
Required files found on the Neat Savant Integration page – http://www.neatintegration.com/product/savant-neo-integration-premium/ once checkout is complete files will be accessible.
Do not edit the neo_neo smart blinds.xml – Editing this file may cause the driver to not function – Edit at own Risk
The dollar sign (‘$’) is ignored when writing the code into a terminal
Purchasing and downloading the files
Firstly purchase the driver and then download this driver and place it into your downloads folder.
- Create an account (Choose the same setup code written on the Smart Controller instructions)
- Power up your smart controller and Pair (The LED should be blinking blue, indicating the Smart Controller is in pairing mode.If it isn’t, tap on the “No” option in the app and follow the steps)
- Connect to Neo-Smart_Blinds WIFI network
- Select “Add a blind” from the upper left corner menu
- Choose the room that the blind will belong to, or add a new one, then give the blind a name. Note that you can add up to 14 blinds into a single room. When naming your blind, try to use a descriptive name (e.g. East Wall, or Bay Window)
- Use the Remote Controller (already paired with blinds) to pair
- Push the “Pair” button. The blind should again jog back and forth. If you see that happen, push “Okay it worked”, otherwise push “Retry”.
- Check the blind details information -> Blind code should be shown up at the bottom which needs to be put in the savant blueprint later (Eg. 036.000-01)
- Add Neo profile into the Savant Blueprint
– Click “Show Library”
– Search “neo”
– Drag $ Drop it into the Blueprint
– Rename -> “Neo Blind Controller”
– Right click Neocomponent & click “Show in Inspector”
- Set the state variable (if cbus has not been used, ignore any cbus settings)
– neo_application -> cbus application (eg. 56 double check in the Cbus Toolkit)
– neo_hostname -> IP Address (already shown up in the iHelp)
– neo_hostport -> 8839 (default value)
– neo_id -> ID from smart controllers section of app
– neo_network -> cbus network (eg. 254 double check in the Cbus Toolkit)
– neo_project -> CLIPSAL (double check in the Cbus Toolkit)
- Click Tools -> Settings -> Shades…
– Add new shades & Set Location, Entity (Single Motor Variable Shade) & Label
– Set Address : Modified Blind Code *For blind AAA.BBB-CC enter AAA+BBB+CC
Eg. if the blind code is 027.041-01, enter 027+041+01 as the below image shows
– Set Address : cbus button address (double check in the Cbus Toolkit)
– Set Address : time from top to the bottom
- Set the trigger which allows the system to update the driver files. Navigate to Review Triggers > Add new trigger and rename > Show the Services/Requests/States. Set the ‘Schedules’ every 5 minutes every day to check for an available update. Drag and Drop the new schedule created just now into ‘When any of these states change the value, evaluate the Rules’. Create a new request under the ‘General Programmable Service Requests’. Drag and Drop the new trigger into ‘then (request)’ and double click to open the workflow. Search ‘Run Shell Script’ and click. Copy and Paste the script into the terminal. (script attached in the download file)
- Save the configurations & Send the new profile into the savant host via Savant Application Manager
- Open a Terminal / Command Prompt
- ssh to the savant host using RPM
- ssh RPM@192.168.2.7
- Password: RPM
- Run -> zsh bin/driver2.sh restart
- After a few seconds, the driver should be started
As soon as the driver begins to run it will attempt to authenticate with neat’s server – If authentication fails and/or a licence has not been purchased (Plus processed – neat’s admin needs to confirm the order) the system will become unresponsive to commands after 24 Hours.
Anytime the host is restarted it will need to authenticate with neat’s server within 24 hours otherwise commands will become unresponsive.
The driver will try to call the neat server every 5 minutes to check for an available update.
If everything is connected and there is no feedback on the driver and blinds are not working from Savant check:
Ensure the driver is running with $ driver status
Correct Addresses in the lighting table
System Monitor > Component status, is the Neo profile getting feedback from the network
Ensure the cable is plugged incorrectly
Recheck the steps above
Email Neat Integration
Please enjoy this savant Neo integration driver to intuitively control your home from a single app