I'm trying to implement action.devices.types.AC_UNIT in google home.
My hub is the IR transmitter, it saves previous states and commands with a packet.
As you might understand the device does not know anything about room temperature.
It seems like thermostatTemperatureAmbient is required for setTemperature execution.
I can report the desired temperature as the ambient one, but then google reports this value when I ask for the temperature at home.
You should be using thermostatTemperatureSetpoint for your desired temperature setting. Ambient temperature should be the actual temp reading from the device. However, since your device does not actually read the temperature, you may consider using the TemperatureControl trait instead.
Related
I'm working with Movesense 2.0.0 on a HR+ sensor and I have to minimize the power consumption when device is not worn.
I can't turn it completely off since I need it to keep the correct time so, to reduce the battery usage, when I don't receive a HR notification for a certain amount of time I unsubscribe from all sensors.
What's the most power efficient way to determine when device is worn again? I was thinking about subscribing to accelerometer (as I understand it is the sensor with the lowest power consuption) and when I detect movement I resubscribe to HR and check for incoming data.
Is it a valid approach?
I also noticed that when device isn't worn but still connected to the strap I sometimes receive incorrect HR notifications, like the strap is acting as an antenna for electromagnetic noise. Is there a way to detect when the device is in that status except for looking at HR data to see if they make sense?
Your question is a bit vague in what you mean by "wear a sensor" (I'm assuming you mean HR-strap on chest). In that case if you look at the power consumption documentation (see the PowerOff measurements compared to no-wakeup) you'll notice that
HR wakeup (/System/States/2 (=Connector)) is ~0.2 uA
Movement wakeup (/System/States/0 (=Movement)) is ~4 uA
All other measurements are much higher starting from 10 uA for Acc # 13 Hz.
So the easiest and lowest power determination is to SUBSCRIBE the /System/States/2.
If you base your firmware on version >=2.1 and you measure HR or ECG you also get updates during measurement when the connection is lost (so called Leads-Off detection), so this should help to filter out the spurious HR detections. For firmware 2.0 and earlier you get Connector state 2 (=Unknown) when measuring.
Note: the leads on detection (/System/State/2 when no HR measurement is ongoing) is very sensitive and can give "connected" state when the HR-strap is sweaty.
Full disclosure: I work for the Movesense team
I am trying to drive EPD(ED060SD1) using STM32F429ZGT, and got datasheet from display vendor. But there is no specific explanation of how to drive EPD display or details of pin.
So I want to know what those pin does.. and any hint how to run this display..
Thank you
ED060SD1 Pin List
The stm32 series of microcontrollers do not support EPD displays directly. I think you would need a EPD controller in between to make it work.
You night be able to generate just the digital inputs, then use an external HV supply from a chip like HV850 and then step it down with inline Zener diodes. I used this approach to make a microflyer based on a piezo speaker!
The HV850 has on/off via digital line and needs +4.2V minimum, max Vout is +/-59V on alternate outputs which is ideal for this purpose.
Simply add a high value resistor on the output side to let it discharge when the panel isn't being driven.
I'd put it in extclk mode and run it at 10Hz to reduce power usage.
I test my code with mlx90614 but with mlx90616 the ambient and object temperature almost same. anybody have this problem. what's the solution?
i test these code on lpc1768 with smbus protocol.
excuse for my english
I have had the same problem. After carefully reading the datasheet it is clear it needs to be calibrated (how, I'm not sure just yet). It's frustrating because Melexis will not provide technical support unless you're buying 10k+, and are very vague about their "calibration software".
The ambient temperature sensor in the MLX90616 is calibrated in the
factory... The sensor-lens combination temperature measurement has to
be calibrated by the customer.
I spent a couple weeks before I realized the reason it was not working, was because it was not calibrated. The output appears to simply be the ambient temperature!
If you read the calibration coefficient register 0x0F you'll see that it is 0x0020.
I have designed a GUI to calibrate my sound card using MATLAB, I am able to record my input signal. I would like to calibrate my input.
How do I do that?
My GUI should be capable to adapt to different sound cards and get the dBV values, hence the Calibration is required. Any help would be appreciated.
A: This is a task from a Metrology, rather than from a programming area
To get the job done, you need a fully-controlled-environment to re-run a defined-input/known-output experiment.
In principle,
your both all your devices and your setup, has to be controlled - i.e.
your MIC-Input-accoustic/electric converter, while [dBa] -> [V] conversion is
"readable" down the cable path, it is not a principally important value per-se,
your CABLE-wire-path, which shall not be either neglected or forgotten,
your SND-Card-A/D converter,
your AUDIO-pre-Calibration Sound-Sample,
your TEST-pre-Calibration Environment
so as to be able to pre-Calibrate your devices for measurments.
The calibration itself can be achieved right by using the same AUDIO Sound-Sample in the same TEST Environment and be that measured / calibrated / by another device, that was certified at a locally recognised reference Authority to have a certain level of precision ( a guarantee that it's readings will not be outside a natl./intl. recognised precision class' envelope from correct/exact values ).
Note: you may want to pre-Calibrate your MIC+SND-A/D setup inside your in-vitro controlled environment specifically across a wide range of frequencies, so as to avoid frequency-dependent variation of the measurement-conversion path. Thus your pre-Calibration would have sort of Calibration-curve as an input for your further tests to be performed in-vivo
My question is very similar to this one: iPhone Proximity Sensor. There's clearly some manner of thermometer within the iPhone that's readable by the OS. Has anyone uncovered the super-secret undocumented APIs to read this sensor?
I doubt this sensor is for ambient temperature - rather I suspect it is for overheating of the circuits. If that is all you want then great, but again, I think it would be useless for ambient temperature.
just my opinion.
All i could find was CTGetTemperature in CoreTelephony of all places.
I don't know about previous models, but my iPhone4 goes from cool-ish to very warm in a matter of minutes depending on the various radio usages. So unless "good enough" = "within 20 degrees F or so", then probably not good for ambient measurement.
Unless (maybe you meant this) you could also track radio usage and subtract a temperature variable depending on radio usages. phew. complicated. Easier to just query NWS.
command to get all super-secret names which related with temperature in CoreTelephony framework
nm "/Applications/Xcode463.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/6.1 (10B141)/Symbols/System/Library/Frameworks/CoreTelephony.framework/CoreTelephony" | grep empera