New device to control your blinds

[DanM]

Can either of you give a quick two minute summary / review of move please? Google isn't helping me out with any reviews and I'm tempted to get involved for the zwave one (although worried that the open wave support will take a while)

[t0mas]

The device works well, charging via solar power obviously requires a bit sunny window. The app on the other hand is horrible, slow to find the device (I don't understand why it searches for the device every time it starts), lots of features are half implemented or "coming in the future". So I can recommend the device if you have either a power source or enough sun to use the included solar panel and want to connect it to some smart home controller. If you plan to use it with the original app: Don't buy it.

[klasse]

I totally agree with t0mas. Also: you can NOT charge the batteries via USB (I've tried).

t0mas: Have you tried to use the USB serial interface? (I haven't bothered yet...)

[pvm]

They did have plans to extend the app after starting delivery of the product.... Hope they'll do this. But first focus on the zwave version (I've ordered a couple of those)

[qwerk]

hmmm, I keep getting "connect: connection refused (111)"


./bin/csrmesh-cli move --pin 1234 --dest 43:C5:5B:04:00:06 --position 254
Running: gatttool -b 43:C5:5B:04:00:06 --char-write-req -a 0x0021 -n 728bc5008070f88094c6f6bd0cbd9a23a2f9ff
connect: Connection refused (111)


python 2.7.9, pycrypto 2.6.1

from the teptron android tool it works fine.

I guess it has to do with my raspbeery/software. when I change the pin or the dest address I get the same error.


*** I solved my problem. IT WORKS ***
on my bluetooth "stack" on the raspberry LE was not enabled.
that did the trick. It was also important that the teptron move app on my phone was killed.

[guantolento]

sorry, so the movez is connected with ble and not zwave ? it's correct ?

[pvm]

It started off with move (BLE) they're now preparing to ship the movez which started as a zwave only but now will be delivered as BLE + Zwave.
Movez is not shipped to anybody as far as I know (as a backer)

[pvm]

Must be BLE according to description and zwave versions are not delivered


It started off with move (BLE) they're now preparing to ship the movez which started as a zwave only but now will be delivered as BLE + Zwave.
Movez is not shipped to anybody as far as I know (as a backer)

[bryanmcg]

This command in this post did not work for me:

Code: Select all

csrmesh-cli move --pin 1234 --dest 43:C5:5B:04:00:06 --objid 1 --position 254

However, maybe it was a change with the latest version, but according to the help, the "{lightbulb,move}" goes at the end. This works for me:

Code: Select all

csrmesh-cli --pin 1234 --dest 43:C5:5B:04:00:06 --objid 1 --position 254 move

[joostnl]

Is the z wave version already being shipped?

[pvm]

No, not for a few months

[heggink]

hmmm, I keep getting "connect: connection refused (111)"


./bin/csrmesh-cli move --pin 1234 --dest 43:C5:5B:04:00:06 --position 254
Running: gatttool -b 43:C5:5B:04:00:06 --char-write-req -a 0x0021 -n 728bc5008070f88094c6f6bd0cbd9a23a2f9ff
connect: Connection refused (111)


python 2.7.9, pycrypto 2.6.1

from the teptron android tool it works fine.

I guess it has to do with my raspbeery/software. when I change the pin or the dest address I get the same error.


*** I solved my problem. IT WORKS ***
on my bluetooth "stack" on the raspberry LE was not enabled.
that did the trick. It was also important that the teptron move app on my phone was killed.

Hey @qwerk, how did you enable LE? I use a USB dongle (BT4.0) but struggle to enable LE on it.

[heggink]

for those looking to use the csrmesh-cli library to control these devices using BLE, the move experimental branch from nkaminski does work for me (https://github.com/nkaminski/csrmesh/tr ... perimental). My devices present themselves as MOVE2 when issuing sudo hcitool lescan. This seems the only version of csrmesh that works with these for now.