Everything posted by Panda88
-
Yolink Motion Sensor
What function is it you need? - I think you can set the motion sensor to only send on Motion, and when it exists motion (that is the new field) The 2 buttons are to force a motion event - you can do the same in a program by running the then event
-
Yolink Motion Sensor
OK - I can take a look - you are correct They no-longer work - do you want me to remove them? Probably no real use
-
Yolink Motion Sensor
They are supposed to send trigger (DON / DOF) like the motion sensor would do - allowing you to trigger a scene/program - you can look in PG3 log to see if a cmd('DON" .. ) is sent I thought it works but I could be wrong It may not be of much use - I am not personally using them
-
Yolink Motion Sensor
Erasing the node in the node server (PG3) does are bigger reset that from the AC - You need to find it in the list there I doubt it helps when a new node does not work - but may be worth a try
-
Yolink Motion Sensor
I meant to erase from the node - not the AC
-
Yolink Motion Sensor
Can you send me a log file with debug enabled and trigger the motion sensor a few times You can also try to erase the motion sensor and restart the node
-
Yolink Motion Sensor
I think something is wrong with your version Mine looks like this - you can select if only DON (motion) DOF (no-motion), both and none can be selected My understanding is that this is want triggers the AC integration outside programs - I believe this is what you are looking for. The motion and NoMotion buttons are to send a DON/DOF from the device (even if there is no motion) Does yours look different?
-
Yolink Motion Sensor
Can you specify exactly what you need and I can talk a look - I have not looked at the motion sensors for a while so I may be able to improve on them
-
Yolink Motion Sensor
I think it may be filtered at a higher level I think you can test on Motion under control - it should only trigger when turned on
-
Yolink Motion Sensor
Let me think about it - It should be possible to have it send only DON (or DFO for that matter)
-
won't update....
Try now - I did forget to update the version number in the code - you should be running the latest already but update message should disappear now
-
won't update....
Let me check if I forgot to update the version in the code - it is a manual process
-
Release History
0.1.22 available - fixes issues related to cloud only operation as well as a fix for a change in keywords in the Tesla_API
-
Instant solar not updating
I did find a bug - I am testing now - I'll release a little later - it also fixes the instant solar power
-
Tesla Node Stopped Working
We have not managed to get the control working yet - effort with UDI - we are still looking but not sure what is not working correctly - sorry
-
Instant solar not updating
Can you send a log file with debug enabled - my guess it is it not connected to the local IP Christian
-
Tesla Node Stopped Working
We are working on getting a updated node server working. Tesla is slowly moving to a new API I have released a new node server for Tesla power wall. UdiTeslaPW2 that uses the new API Still working on teslaEV. Tesla added an additional layer of security when controlling the car and this needs to get implemented
-
Blink NS: cannot authenticate
it is the intend, but 98 represents the No Support The older cameras shows DONE once installed but they remain the same when you take the camera off-line
-
Blink NS: cannot authenticate
I have not found a way to know if the camera is on line or not ( the older cameras) So i reply there is no support. Any suggestion is appreciated
-
Blink NS: cannot authenticate
thanks - you log shows your network name already - so it does not excercise the portion of the code that is supposed to add the possible networks I have access to my system again so I can experiment a little to figure out what is going on - I tried it once and it worked, so I did not test more
-
Blink NS: cannot authenticate
the code is supposed to populate the network names automatically - can you send me a log file (debug enabled) and I'll try to understand what is happening Yes - entering the key manually should work as well . if there is more than 1 network create a key per network
-
Blink NS: cannot authenticate
They should be shown in the configuration. Maybe try a page refresh or restart.
-
Blink NS: cannot authenticate
New node released 0.4.8 Note, the structure is changed so reinstall is likely required
-
Tesla Node Stopped Working
Still working on getting the control portion working. There is a 2nd layer of security added and Michel is looking at how to help support this
-
Release Info
You can update now - it should work with the current release but you can also wait. My understanding is the bigger will get updated automatically when the new PG3x released I personally would wait