# Application default device type

**URL:** <https://forums.balena.io/t/application-default-device-type/147515>\
**Category:** Product support\
**Created:** [July 1, 2020, 4:09pm UTC](https://forums.balena.io/t/application-default-device-type/147515 "2020-07-01T16:09:47Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![thgreasi](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/thgreasi/32/454_2.png) [@thgreasi](https://forums.balena.io/u/thgreasi)\
**Post date:** [July 5, 2020, 8:43pm UTC](https://forums.balena.io/t/application-default-device-type/147515/17 "2020-07-05T20:43:40Z")

</div>

That makes things clear.  
The issue is that the device is pre-registered with `balena device register` and you can see that after that point the device shows up in the dashboard with a device type matching the default device type of the application.  
As a result, when you later use `balena config generate` you change the device type of the already registered device.  
Perhaps it might be better to have the CLI error when `---device` and `--device-type` are used together, so that it’s clear which option is respected.  
It also seem that in order to be able to cover your use case, we should also add a `--device-type` parameter to the `belana device register` command.

We will let you know once these get implemented and released.

Kind regards,  
Thodoris

---

_[View the full topic](https://forums.balena.io/t/application-default-device-type/147515)._