Page 5 of 5

Re: New 2.1.4 beta

Posted: 23 Jul 2018 20:37
by PoltoS
You can name it right in the controller. Such a feature was not announced and we don't think to implement it since only Z-Way would support such a feature.

Re: New 2.1.4 beta

Posted: 24 Jul 2018 09:17
by Zixwater
PoltoS wrote:
23 Jul 2018 20:37
You can name it right in the controller. Such a feature was not announced and we don't think to implement it since only Z-Way would support such a feature.
From my post on this thread https://forum.z-wave.me/viewtopic.php?f ... 843#p74843 and I for once would appreciate it since when the Z-uno is included in controllers and at least in razberry that such a value should be respected. I'm setting up moisture devices and it's pure pain naming it over and over when adding new devices. Thanks anyway.

Re: New 2.1.4 beta

Posted: 24 Jul 2018 10:17
by PoltoS
Basically Z-Way should name them according to sensor type. Isn't it naming them? Or you have same types of channels?

This is possible to do but this will take precious time instead of doing other cool features and this will also take code space in our part preventing other features.

Re: New 2.1.4 beta

Posted: 24 Jul 2018 12:21
by Zixwater
PoltoS wrote:
24 Jul 2018 10:17
Basically Z-Way should name them according to sensor type. Isn't it naming them? Or you have same types of channels?

This is possible to do but this will take precious time instead of doing other cool features and this will also take code space in our part preventing other features.
Basically, no. I always get the name z-way.me #1, 2,3.. and so on. This is because I have atleast 2-3 soil sensors per demos and around 5-6 windows needing measurements.

Why not just be able to tell the Z-uno during inclusion/setting up channels to use a char value? Is that really so time consuming? Sorry if my request is taking your time. I'll just try to solve it in some other way.

Re: New 2.1.4 beta

Posted: 25 Jul 2018 01:07
by PoltoS
This is not only time consuming, but also code space consuming ;) This is even more critical.

I wouls suggest to make a "postfix" in Z-Way to rename your channels.

Re: New 2.1.4 beta

Posted: 25 Jul 2018 01:36
by PoltoS
We have release a new beta (again 2.1.4 - you need to re-install it if you are already testing it). Changes compared to previous beta release:

New features
  • ADC and PWM pins can now be referenced in pinMode/digitalWrite/digitalRead as PWMx и ADCx too (like in Arduino). Before was only via pin number:

    Code: Select all

    pinMode(A0, OUTPUT);
    digitalWrite(A0, HIGH);
    ...
    pinMode(PWM1, INPUT);
    digitalRead(PWM1);
    
  • Added FastPWM on pin A0.

    Code: Select all

    pinMode(A0, OUTPUT);
    zunoFastPWMInit(0);  // Flags are same as for GPT (only divider can be changed)
    zunoFastPWMSet(100, 100); // Low and high period in timer ticks. By default 4 MHz is one tick
    zunoFastPWMEnable(1); // Start PWM0
    ...
    zunoFastPWMEnable(0);  // Stop PWM0 when not needed anymore
    
  • New types added for SensorMultilevel:
    • ZUNO_SENSOR_MULTILEVEL_TYPE_FORMALDEHYDE_CH2O_LEVEL
    • ZUNO_SENSOR_MULTILEVEL_TYPE_RADON_CONCENTRATION
    • ZUNO_SENSOR_MULTILEVEL_TYPE_METHANE_DENSITY_CH4
    • ZUNO_SENSOR_MULTILEVEL_TYPE_VOLATILE_ORGANIC_COMPOUND
    • ZUNO_SENSOR_MULTILEVEL_TYPE_CARBON_MONOXIDE_CO
Bug fixes
  • Pull Up mode was overriden by mode change on the same i/o port (8 pins).
  • ZUNO_METER was not added to channel (broken since first 2.1.4 beta)
  • S2 bootloader upload fixed
  • analogWrite(pin, 0) was not working properly (was never actually 0)
  • zunoNID() and zunoInNetwork() was not working on S0 bootloader
  • zunoBatteryHandler was not working
New libraries
  • Wire. Added clockStretching. Enabled using Wire.enableTS(true). Slows down the speed by ~25%. Usefull to support modern I2C devices that do require Clock Stretching.
  • Added library for air quality sensor CCS811 from AMS. Example:

    Code: Select all

    #define MY_SERIAL Serial0 
    #include <ZUNO_CCS811.h> 
    ZUNO_CCS811 ccs811; 
    
    // For precise values you need external temperature/humidity sensor like DHT. Here for example 50.0% humidity and 25.00 C are assumed.
    CCS811_Environment env_data = {500, 2500};
    
    void setup() { 
             MY_SERIAL.begin(115200);
             if (ccs811.begin()) {
                     MY_SERIAL.println("CCS811 found!");
                     ccs811.setEnvironmentalData(&env_data);
             }
    }
    
    void loop() {
             if (ccs811.readData() & CCS811_STATUS_DATAREADY) {
                             MY_SERIAL.print("CO2: ");
                             MY_SERIAL.print(ccs811.geteCO2());
                             MY_SERIAL.println(" ppm");
                             MY_SERIAL.print("VOC: ");
                             MY_SERIAL.print(ccs811.getTVOC());
                             MY_SERIAL.println(" ppb");
             }
             delay(5000);
    }
    
We are starting beta period and then we will make a public release.

Re: New 2.1.4 beta

Posted: 25 Jul 2018 16:27
by Riri
Hi,
A huge thank you for all these corrections and relevant additions !!!
Eric.

Re: New 2.1.4 beta

Posted: 26 Jul 2018 02:46
by PoltoS
@Riri, our pleasure to make Z-Uno useful and functional.

If possible, please check all problems you reported us and confirm us those fixes.

Re: New 2.1.4 beta

Posted: 27 Jul 2018 11:24
by Riri
Hi,
I took the time to test and check everything

For zunoNID() and zunoInNetwork() on S0 bootloader : OK
For Pull up on the same i/o port : OK
For issue of compiler with security S2 and uploading sketch : OK
For the difference of timing of the digitalRead on pin 3,4,5,6,7,8 : OK

I had a problem with the inclusion in eedomus and the new bootloader solves it.
surely a matter of delay. It suits me ! ;)

Really good work ; very effective.
Eric.

Re: New 2.1.4 beta

Posted: 28 Jul 2018 23:48
by p0lyg0n1
Thank you, Eric. You did a great work! We glad that all the reported issues was solved. Looks like we finally will be able to release 2.1.4.