Zircon3D community

Tami Liu

If you would like to cancel your Zircon3D subscription and remove your saved payment method, please follow the steps below.

Step 1 – Log in and Open the Console

Go to https://zircon3d.com
Click the Console button at the top right.
Log in to your account if prompted.

Step 2 – Go to Billing

In the left sidebar, click Billing.
You will see your current subscription plan.
Click the Update Plan button.

Step 3 – Cancel Subscription or Remove Card (Stripe Page)

After clicking Update Plan, you will be redirected to the secure Stripe Billing Portal.

From there, you can:

Cancel Subscription

Click Cancel subscription
Confirm the cancellation

Your subscription will remain active until the end of your current billing period.

Remove Payment Method

Under Payment Methods, click the ⋯ (three dots) next to your card
Select Delete

If multiple cards are saved, you can remove them individually.

Important Notes

Subscription cancellations take effect at the end of your current billing cycle.
Removing your card does not automatically cancel your subscription - please make sure to cancel first if that is your intention.
All billing operations are securely handled by Stripe.

If you encounter any issues, please contact us as support@lichr.com and we’ll be happy to assist.

chris

Hi Mitchell,

We don’t have this capability at the moment, but what you’re suggesting is a great idea.

Allowing users to add simple 3D primitives (like cubes or basic shapes) to block off areas and attach labels would be very useful in many scenarios. It also aligns well with Zircon3D’s visual philosophy, we intentionally favor simpler, abstract representations to keep data visualization clean and readable, rather than relying on detailed or decorative models.

This is something we’ve now added to our roadmap, and we do plan to implement it in a future update.

Thanks a lot for taking the time to share the idea, feedback like this really helps shape where the product goes.

Tami Liu

What happens to my projects if my subscription ends?

Short answer:
Your projects will NOT disappear.
Your data stays safe.
Your account will be downgraded to the Free plan, with some limits.

After your subscription ends, you’ll be on the Free plan, which includes:

1 editable project
Up to 1000 m² building area
Up to 25 monitored devices
Heatmap view: Temperature (Free plan feature)

*This quota is based on the Free plan limits as of January 2026.

What if I have more than the Free plan allows?

You can still view everything, but editing is limited:

Multiple projects

You can view all projects
You can edit only one project at a time
You decide which project to keep editable
If it’s not the one you want:
- Go to Project → More > → Project Settings
- Delete it
- The next project becomes editable
  This lets you choose which project fits the Free plan

Area / devices / features over quota

Projects that exceed Free limits will show warnings (like in the screenshots)
You can:
- View everything
- Remove devices, reduce area, or simplify the project
Once it fits the Free plan limits, it works normally again

Important takeaway

️ No lock-out
️ No data loss
️ No forced deletion
️ You’re always in control of what to keep

If you later re-subscribe, all advanced features and higher limits are instantly available again.

Example after downgrade

In this screenshot, the project “test” is the active project and can be viewed, edited, and deleted. All other projects are automatically switched to view-only mode. They remain fully visible, but editing is disabled until you delete projects or adjust your setup to meet the Free plan quota.

View-only projects can be opened and viewed, but not edited; they can still be deleted from Project Settings → Advanced.

Tami Liu

@keiflab Glad to hear it’s working after the update, thanks for letting us know!

Tami Liu

@keiflab Hi, just a quick update, we’ve fixed this issue in the latest release.

Please upgrade the Zircon3D Home Assistant add-on to v2.0.8 (2026-01-25), or wait for the auto-upgrade if you have it enabled.

v2.0.8 – Bug Fix
Fixed a bug that could cause an infinite loop during loading

Thanks again for your patience and for helping us identify this.

Tami Liu

@keiflab Hi, thanks a lot for sending the logs and screenshots, they really helped.

From the logs, this looks like a logic issue (a dead loop during loading) rather than anything hardware-related. We’re confident this isn’t caused by your computer or browser.

We’ll work on a quick fix for this and will let you know as soon as it’s ready.

If you’re okay with it, could you also share your email address? That way we can notify you directly once the fix is available.

Thanks again for your patience and for helping us track this down, we really appreciate it.

Tami Liu

@keiflab Hi, thanks for sending the screenshots, that’s very helpful.

From what we can see, the floorplan data appears to be present, but the floor itself isn’t being rendered or loaded. While it could be hardware-related, but it’s more likely an edge case involving the floor’s internal data or geometry state, which we’ll need to investigate more closely.

To help us dig further, could you please check the browser logs?

Press F12 to open Developer Tools
Go to the Console tab
Reload the page
If you see any errors, please copy the details and send them to us

If you don’t mind, could you also share which browser you’re using and what device/computer you’re on? That can help us check for any browser- or hardware-specific issues.

Sorry for the inconvenience, we understand how frustrating it is when a floor doesn’t load. Thanks for your patience while we look into this.

Tami Liu

Hi, thanks for reporting this.
To help us narrow this down, could you please check the following?

Home node check
In the top navigator, please click on the Home node.
Do you see the list of floors there, or does it also fail to load?
Areas list under the floor
When you select the Basement floor, please click the Areas sub-tab under the navigator.
This should show a list of all areas on that floor, does it appear correctly?
Enable debug helpers
Please open the Debug tool (see the screenshot I attached), then enable:

Debug Show Hole Helper
Debug Show Handles

After enabling these, see what happens in the scene.
If possible, please send us screenshots of what you see — that would be very helpful.

Also, is there anything special or unusual about this floor?
For example:

very large or complex geometry
many holes / cut-outs

This doesn’t look like a hardware limitation at first glance, but the answers above should help us confirm where the issue is coming from.

chris

Hi David,

This is unfortunately a known issue related to a Home Assistant API called ingress, which allows our add-on’s UI to communicate with its backend.

It appears that the ingress channel is only fully activated after the add-on UI has been opened at least once from Home Assistant. If the UI is accessed via a web card before that initial opening, Home Assistant may raise this error.

Workaround

As a workaround, our add-on also exposes port 11200, which bypasses Home Assistant’s ingress proxy entirely.

For example, instead of using this URL:

http://homeassistant.local:8123/api/hassio_ingress/ym-tlrzEEeGSTSNCz7up0Gf3uqHboBU5NGFvBfH7AMY/offline/viewer/?group=haEBrqFXAEIs&project=sLVclZKQrCvP#cam&p=0.00,0.00,0.00&h=40.11&v=39.56&z=400.00|dsp&fs=1.00&fd=tc&wc=1.00&wd=t&od=tc&thm=auto|viz&layer=rkqaX00R

You can replace:

:8123/api/hassio_ingress/ym-tlrzEEeGSTSNCz7up0Gf3uqHboBU5NGFvBfH7AMY

with:

:11200

So it becomes:

http://homeassistant.local:11200/offline/viewer/?group=haEBrqFXAEIs&project=sLVclZKQrCvP#cam&p=0.00,0.00,0.00&h=40.11&v=39.56&z=400.00|dsp&fs=1.00&fd=tc&wc=1.00&wd=t&od=tc&thm=auto|viz&layer=rkqaX00R

Additional notes

Home Assistant ingress has caused several issues beyond this one—some users have also reported unstable connections. Accessing Zircon3D directly through port 11200 is generally more stable and can help avoid these ingress-related problems.

It’s possible that the Home Assistant team will improve the ingress proxy in the future. Until then, this is currently the most reliable workaround.

Please give this a try and let us know if it works for you.

Thanks in advance,
Chris

chris

Hi David, thank you very much for reporting this issue. We’ll investigate it and get back to you as soon as possible.