forum

Is it possible to set the Z-Uno as a non-battery powered device?

It shows up as 0% and this triggers my low battery alerts.

Yes, your Z-Uno supports all power modes defined in Z-Wave. I think there are 2 things to check:

First, check if the sketch contains the correct definition:

https://z-uno.z-wave.me/Reference/ZUNO_ ... PING_MODE/

And the other thing: if you change channel definitions or power, it is best to exclude and include the device.

Does this help?

I have it set to always awake. This seems to work. However I still get a battery indicator on the controller which is at 0%. This means the device has the parameter "battery operated" set. I don't think it has any other impact than being in the "battery operated" category. If it at least was on 100% instead of 0%.

Please try this:

Exclude your Z-Uno from your controller.
Upload the sketch to your Z-Uno.
Include your Z-Uno.

I've done this multiple times already. It still is listed as a battery operated device.

I have it excluded in my low battery script, but I think this should be fixed.

If you post your script, I can try it on my Z-Uno this evening.

The battery script is in python.

The only setup for the Z-Uno ist this line:
ZUNO_SETUP_SLEEPING_MODE(ZUNO_SLEEPING_MODE_ALWAYS_AWAKE);

Which I think is correct, right?

I have an Aeon Multisensor which I power by USB, the same applies there with the exception that the battery shows 100%.

Btw. can I "manually" set the battery level?

If you change your MultiSensor from battery power to usb power, you have to exclude and include it! This is true for 99% of all devices that support batteries and another power source. If you do not do this, your MultiSensor does not work as expected. Both the conroller an the device will think it is battery operated. It will always say 100% because it thinks the battery is good. An exampe of what is wrong, in your case: it will not route messages for other devices, because battery devices do not do that.

Your setup line seems correct. I wonder if anything else might override this.

You cannot set the level, but you can tell the voltage range.

You can see this in my FLiRS example, near the end:

https://github.com/petergebruers/Z-Uno-FLiRS-LED-DEMO

From my multi sensor:
Class Name: Binary Sensor (routing)
Features: routing, battery, beaming, waking

From Z-Uno
Class Name: Multilevel Sensor (routing)
Features: routing, beaming

Maybe it's and Indigo-thing. I included the multi sensor when on USB already.