New Functionalities in Build 2017.02.19

[escheers]

Updated to new firmware, LED activated for CO2, no problems here

[jasp]

(02-19-2017, 10:44 AM)admin Wrote: aahhh, you can try with an earlier version, and also try opening it and check if some wire isn't gone loose. i use some jumper wires to wire up everything, so try pushing them a bit in/out

 It was the wire ... everything is ok now !

Thanks,

[admin]

yeah.. great )

[vaanja]

Sucesfully updated older CM1106 version. The only outstanding questions are regarding CO2 LED levels - How are levels/colors calculated? Is it specific for every sensor? As far as I know there are different max. levels for each sensor type so I would like to know if e.g. for 2000ppm will be set to violet LED for all types of sensors. (some of them hax max. level 2000ppm and another 10000ppm).
Also for wifi config - I'm not able to use configuration via wifi - my sensor has got IP from DHCP, but config.vair-monitor.com not working at all (tested on chrome, firefox, edge, IE). Any hint how to use wifi config?

---

After some testing I found I need to disable deep sleep if I want to have CM1106 configurable via wifi (Go to sleep time(sec):0)

[admin]

(02-19-2017, 01:31 PM)vaanja Wrote: Sucesfully updated older CM1106 version. The only outstanding questions are regarding CO2 LED levels - How are levels/colors calculated? Is it specific for every sensor? As far as I know there are different max. levels for each sensor type so I would like to know if e.g. for 2000ppm will be set to violet LED for all types of sensors. (some of them hax max. level 2000ppm and another 10000ppm).
Also for wifi config - I'm not able to use configuration via wifi - my sensor has got IP from DHCP, but config.vair-monitor.com not working at all (tested on chrome, firefox, edge, IE). Any hint how to use wifi config?

---

After some testing I found I need to disable deep sleep if I want to have CM1106 configurable via wifi (Go to sleep time(sec):0)

you shoudn't need to set this property, as the CM1106 and CM1102 do not go to sleep. But in general the WebSocket server is stopped 5 min after start, so if you did not connect to it, perhaps it had stopped.
as for the ranges - currently it is hardcoded as described on the RGB Led Page - 400-3000 ppm for co2.
If i remember correctly i haven't shipped with 2000 ppm sensors, only 5000 and 10000.
In general the ranges can be made configurable, as well as the colors

and what color you get for each level you can see when you press the Sweep Color Range (but i guess it will be more reliable over serial port,as there can be some delay in WSS communication)

[vaanja]

You are right, after 5min WSS gone.
How can I achieve situation that my CO2 Monitor is always reacheable via wifi? I have only CM1106+Wifi and sensor is powerd from USB charger so I dont want to lost ability to reset or change settings after 5 min. If something get wrong with device I need to physically re-connect te device which is the same as I unplug it from USB charger and connect it via computer usb for config.
Is there any other reason (than power saving/heat) for switching WSS off after 5min?

[admin]

well, one reason was simply to avoid having some open servers ( i still haven't implemented password protection )
but apart from this none - i will make it configurable

[admin]

there was a little bug with the devices using the SI7021 sensor (Temperature/Humidity) - the reading for the temperature was only considered 10 seconds after the start, so it often would show 0 during operation
it is now fixed with 20170221

[daybyday]

Hi,

Received it today, works great. However, LDR reports valid values (e.g ~200 currently) but MQTT state topic gets sent %LUX%:

Code:

vair/living/co2 519
vair/living/temp 20.79
vair/living/humidity 40.15
vair/living/pressure 1017.22
vair/living/pm25 %PM25%
vair/living/pm10 %PM10%
vair/living/lux %LUX%

I tried setting %LDR% instead under Generic > MQTT but when I "Set MQTT" it just overwrites it with %LUX% from homeassistant settings.

This is on 20170228; any ideas? Thanks!

Edit: managed to run:

Code:

mqtt_msg_add "4" vair/living/lux:%LDR%

Works now.

[admin]

yeah.. there is still a bit outstanding work to make this all work smoothly together
eventually once the config tools starts to be able to undestand what knds of sensors are on the device... it will be easier
just that it is written on JS and HTML5 and there i do mostly copy/paste development )