Hello everyone!
Based on the quite useful reverse engineered schematic at https://hackaday.io/project/174308-tradfri-pir-motion-sensor-hacking the measurements were somewhat sabotaged by the 2N7002 (see Connors comment "enables voltage dividers only when triggered").
the transistor is controlled by the Elmos E931.96 PIR motion controller IC.
The latter is programmable by the IKEA TRÅDFRI ICC-1 module's EFR32MG1P132F256GM32 MCU.
E.g.
2. Blind Time
Ignores motion after the interrupt output is switched back to 0
Range: 0.5s... 8s.
The blind time is [Register Value] *0.5s
3. Programmable pulse counter
1... 4 pulses with sign change in between
Amount of pulses = [Register Value] + 1
4. Window time
For noisy environments
2s... 8s window
Window time = [Register Value] * 2s + 2s
https://github.com/basilfx/TRADFRI-Hacking gives a good overview on that.
What is the issue with tose 60s?
@Jodaille Thanx for the link to the project. I think I'll order one of those sensors this weekend. As I hope it can also send the amount of rain that is falling.
I do have to check the optical sensor. But I really like the heating in the controlli sensor
Main problem (already "quickfix" solved) is completely new and incompatibile interrupt system implemented in new (post-2016) ATtinys. More flexible, but also coming with some problems when using Arduino-like code and few libraries. Other than that, due to completely new power management these features I don't tested yet, may not work properly...
Update
Meanwhile I made progress with my project. Together with some colleagues I want to install a real-time measurement system with more than 30 channels (i.e. 30 Nano BLE 33 measuring accel. and gyro.) and one evaluation unit (another Nano BLE 33 combined with other computers). The 6 values (2*x,y,z) of 16 Bit each shall be transmitted with 10 measurements per second.
Instead of spontaneous sending beacons with new measurement values from the 30 devices (to many collisions, real-time simply not possible) I use a master-slave polling, done by the evaluation unit. And I continue using non-connectable/non-scannable BLE-Beacons, for the request messages and for the response messages.
Meanwhile, my beacons can be detected by typical BLE scanner APPs on my smartphone (Android 10). I do not know, why that did not work at the beginning. May be I corrected some mistakes incidentally in the last months.
I am working also on a channel hopping (in case of disturbances by other devices with BT and WLAN) and using more channels for higher measurement speed. But the implementation of that will start later.
8 hours later
Now I found a reason for the behavior of the Scan-APPs: My request beacons (without data, only user address of 6 bytes) are detected, but not the response beacons with data.
I do not need the smartphones now (the speed of about 500 beacons per second is to fast for them), so I am happy with my solution.
@ptr727 This chip will work for a single channel dimmer, but has trouble operating as part of a multi channel dimmer. I prototyped a one channel design and had it working but gave up as I could not get a workable design for a 4 channel unit.
@ejlane Correct. 7 nodes = 7 machines. BUT, the 7 current machines are 7 raspberry pi 4 (8gig Ram) modules. it is 1/2 of what my goal is. Eventually it will be a full 14 node cluster.
I had been doing something similar with the pi satellites. I found that if you tell it to use a UDP broadcast to localhost for the wakeword/recording then it doesn't send the audio frames to the mqtt broker.
