# Device/Turned on not available after migration to Homey Pro 2023

**URL:** <https://community.homey.app/t/device-turned-on-not-available-after-migration-to-homey-pro-2023/143264>\
**Category:** Questions & Help\
**Created:** [September 21, 2025, 12:42pm UTC](https://community.homey.app/t/device-turned-on-not-available-after-migration-to-homey-pro-2023/143264 "2025-09-21T12:42:55Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [September 23, 2025, 3:13pm UTC](https://community.homey.app/t/device-turned-on-not-available-after-migration-to-homey-pro-2023/143264/14 "2025-09-23T15:13:41Z")

</div>

That’s what [this thread](https://community.homey.app/t/homey-does-replace-true-with/98850) is all about.

Between HP2019 and HP2023, Athom has changed the value that represents `true` and `false` in Boolean variables from the _strings_ `true/false` to the _symbols_ `✓/⨯`, breaking scripts and flows that depend on these values.

I asked about this inconsistency on Slack in December 2023 and was told it was already mentioned to Athom in August 2023, but since then it hasn’t been fixed and we can probably conclude that Athom simply doesn’t care about this.

---

_[View the full topic](https://community.homey.app/t/device-turned-on-not-available-after-migration-to-homey-pro-2023/143264)._