HomeGenie Forum
General Category => Troubleshooting and Support => Topic started by: pim555 on September 05, 2015, 04:12:20 PM
-
In the past I modifed the smartlights code to use the MS13 as a motion as well as light/dark sensor for switching on lights, ie when the MS13 reports it is dark (it will send an ON command for the configured X10 address + 1) and it reports motion (it will send an ON command for the configured X10 address).
I wanted to use the MS13 as light/dark sensor but it looks like the light control does not recognize the MS13 as light (luminosity) sensor anymore. When I try to enter its name in the smartlights configuration widget, the entry bar stays red, ie it is not recognized.
Has this changed over the last versions? What can I do to still use the MS13 as a light/dark sensor for smartlights?
-
I was about to buy one. In 493-p4 there was a change in the x10lib did it stop working by than? SC9000 was deprecated, too. Does the MS13 link to the SC9000 or CM15?
regards
Jens
-
I receive the MS13 commands via CM15pro connected to RPI over USB. Not sure when it stopped working. But must be one of the most recent versions.
-
As I have the CM15pro, too I gonna buy a MS13 - but shipping will take some time.
Maybe you can try downgrading X10lib to an older version
-
Btw, MS13 is working fine but the issue is that when setting up smartlights, it doesnt seem to recognize the MS13 as a light sensor. So when you use it as a trigger condition, you can still use it.
-
I originally was planning on using this approach with the Advanced Smart Lights code, but decided to use the weather AP instead. If you wanted to tweak the code to point to a sensor instead of the API, my script would work great for what you need. It also wouldn't be that difficult to modify the original Smart Lights code for this purpose and should work fine. The original code looks for a sensor with luminosity but the X10 module has a built in trigger point where it's either light or dark not a light percent.