official forum

It is not you... wake up is tricky! I see at least one issue... In setup, you have to read NZRAM and set the pins according to that. So, after the devices wakes up, first the pins "flap" as you said, but then in setup you set them to output and also on or off, as indicated by the NZRAM. In my sketch...

Good luck. I did a quick test, and I have found 2 issues, not related to that solution. The first is you have to use "long", not DWORD for the getter. Otherwise Z-Uno reports only lower 16 bits. The second, I was unable to solve: I have reasons to believe HC2 does not display values above 32767... I...

I'll do some more tests but here is a quick result, wake up tested on pin 9. I use the test sketch at the end of this post. To wake up the device, I pull INT1 to ground. - When the Z-Uno goes to sleep, state is preserved. - When the Z-Uno wakes up, the pin goes to weak pull-up mode after some time. ...

Because the developers haven't answered yet, I decided to do some measurements myself: During reset (press and hold reset), all pins pull-up about 66uA, except: 23 = service (184 uA) 18 = INT1 (97 uA) Service has a 100 k resistor to the 3V regulator plus some additional circuitry. INT1 has a 100 k r...

Thanks for the update... I have not tried this yet, but I have found how to get 0.11 Lux in the lowest range and 100.000 Lux high range. The trick is, to modify the "measurement time registers" of the BH1750 https://gist.github.com/Koepel/b70f81c71a52d8d6d3da86b9fe56d50e Since you mentioned the high...

Quick update... A bit more detail in the ZM5202 datasheet... But this does not explain the "flapping"...

"Some reset methods deliberately leave the state of GPIO pins unchanged, while other GPIO pins are set to high impedance with an internal
pull-up."

Ah, yes, I see what you mean! I wasn't clear when I said "default to weak pull up". My bad. That is assuming only the hardware reset! I fully agree with you, Either the Z-Uno or the framework does extra initialisation, I observed what you said when I wrote my sketch, but I do not remember the detail...

(...) The interrupt handler seems to stop the Z-Uno from executing some time consuming instructions, like the Serial.print command for instance. Some background info... According to the official docs : "The duration of an application interrupt routine must be below 80us." (See INS13954 Z-Wave 500 S...

Almost all MCUs based on 8051 default to "weak pull up" and I think the Z-Uno is no exception to that rule. I occasionally program STC MCUs and they exhibit the same behaviour. In any case, one of the guys of Z-Uno confirmed there is no workaround. I have build an RGBW and the gates of the LED drive...

By gateway you mean "controller", like Z-Way or Fibaro HomeCenter? Z-Uno is for developing devices, not controllers. Though, for sake of completeness, you might be able to turn a Z-Uno into a controller by flashing it with the published generic image (in the Silabs SDK), but there might be no way ba...