-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Motion-Sensor, Door-Sensor and Smart Plug #6
Comments
Yesterday I added these devices, not sure if it all works correct, I don't own those devices. However, you can install the alpha branch using the developer tools. If you miss some additional configuration please add it by forking and do a pull request, or just poke me :-). |
Wow great news. Will try all the devices end of this week and report back. |
re-test with correct alpha branch... EDIT: Sorry for spamming. Good News. |
No problem, Did you use the alpha branch for testing? Because I fixed the
productTypeId's for the devices on that branch.
see:
https://github.com/bramoosterhuis/com.devolo/tree/alpha
thanks for testing
Met vriendelijke groet
Bram Oosterhuis
www.bramoosterhuis.com
2017-03-09 17:22 GMT+01:00 sporca <[email protected]>:
… started testing. found mistake in app.json. "productTypeId": is wrong for
new devices.
I changed it for MT2647 to "2", for MT2646 to "1" and for MT2648 to "2".
It then finds the correct app during inclusion. Unfortunately I then get an
error "manager.vdevice.drivers.zwavebasic.pair.invalid_capability" for
MT2647 during inclusion and a warning "invalid_commandclass..." for MT2646
after inclusion.
Sorry for commenting like that I don't know much about github.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/bramoosterhuis/com.devolo/issues/6#issuecomment-285400531>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AL7H2IggpECfNSNa-ASHyClZ_NuoYlN1ks5rkCc6gaJpZM4MULpm>
.
|
Yes, last tests were with alpha branch and very promising. productTypeIDs are correct and inclusion for motion and door sensors work. I changed "id": 22, "size": 1, to "value": 0 because the sensors started spamming each change of lux. |
I set parameter 22 and 21 default to 0 (disable differential reports) now and added a checkbox to the config so you can enable it if required. The remote key fob is not working due to some issue with homey for details see: https://github.com/athombv/homey/issues/1261. But I also own a key fob (MT2653) so that will be tested with the next release of homey's firmware. I will look into the invalid_commandClass after work. |
@sporca I corrected the command classes and added the settings for the wall plugs. Let me know if this fixes the issue for the MT2646. |
Your amazing. First test with 1 motion sensor, 1 wallplug and 1 door sensor is working great. EDIT: Default mode for metering plus is "night mode" but it behaves like "normal" mode. BTW. do you have a paypal donation link. I'd like to buy you some beer. :-) |
Thank you for your work, just installed the alpha and my door contact is working. Thanks again! |
I'm still testing. Now with 3 Door-Sensors, 7 Motion Sensors and 3 Wall Plugs. So far it's working good. I changed PIR-Sensitivity to 99, otherwise it's not detecting properly. Sometimes Motion Detection is very slow or not working reliably. Sometimes getting Transmit Error, but think this is Homey Firmware problem, too. One strange issue I have is with only one wall plug that is spamming his metering data every 30 seconds. Pushing higher Watt Meter Reporting Period to the device does not change the behaviour. Maybe I have to re-include this plug, because it's working with the other 2. I'm very happy with your work, absolutely cool! |
Good to read that every think seems to work smooth again. I submitted v1.0.3 of the app to a beta release. It will become available for everyone as soon as Athom approves it. |
Do you plan to support further devices like the Devolo Motion (3-in-1) Sensor or the Door/Window (3-in-1) or the Smart Plug? I heard those are Philio Sensors with customized chip and firmware.
I managed to use the code from the philio app and change the hardware id to devolo. it works quite good, but sometimes the motion sensor hangs in alarm status, which causes a lot of problems.
EDIT: for me it was important to disable the illumination and temperatur differential report, because the sensor spammed their values to the homey and crashed the z-wave.
The text was updated successfully, but these errors were encountered: