Hello @adizanni – first off, let me say this is a pretty awesome implementation and I’ve loved experimenting with it over the last few days. At present I have two issues confounding me:
Object IDs and how to obtain them. The only documentation I’ve found says to obtain the object ID by double-clicking on the object in the floor3d card – this works great, however it only works for visible objects. I have some “incandescent light sources” in my model, but I do not know where to click to obtain the model. I also tried adding a lamp to my model instead of a generic “light source” but the problem there is the base of the floor lamp – not the top part where the bulb is – acts like the source of the light which means it doesn’t look right. I can levitate the floor lamp 4 feet off the floor and that fixes the light, but it looks funny having a lamp floating above the floor!
Cached models. It seems that if I export my model to a file called “home.obj” and import it into HA, it renders. If I then make some changes in Sweet Home 3D and re-export to a file called home.obj (same name), these changes do not take effect. I have to change the name (to home2.obj or some other file) for it to show the changes. How do I clear the cached models?
Concerning your first point, you should be able to find non visible objects IDs if you open the json or the mtl file in any text editor. Note that I don’t know in general how this tool works with invisible light sources (I seem to remember @adizanni mentioning something about them in the tutorial videos though).
Thank you. On the Sweet Home forums I found a hack to force light sources to be present in the OBJ file. I will explore this.
Which just leaves me with the cached model issue and one other thing that I’m struggling with: light sources bleed through walls. Is there a way to prevent this? if I have a small room with a light source in it, when that light is enabled I don’t want illumination outside of the room.
Which seems strange since there is only one ceiling lamp.
It also seems that if I don’t give each instance of an item a unique name they all wind up having the same ID in Home Assistant (the JSON file). This means if I have ceiling lights scattered throughout the home, there’s no way for me to tie a device to some of the ceiling lights unless I manually give them a unique name. Is that the intended behavior (or am I doing something wrong)?
This is normal the objects that you see as one in SweetHome, are, in reality, composed by several parts and my plugin cannot change this. When you export, each component of each object is exporte independently. If you want to have only one object you need to name it Ceiling_Lamp# (with the sharp character at the end); this way, you will have only one object exported. Be advised that when you do that your entities will be bound to the full object, this may create some side effect on the scene (with lights doors, etc.)
Hi @adizanni, I get an uncaught error when my card tries to load up my model. I think my house model is too complex…
On browser debugging console:
at floor3d-card.js?hacstag=361776538153:2356:4523
at Object.onLoad (floor3d-card.js?hacstag=361776538153:2231:531795)
at XMLHttpRequest.<anonymous> (floor3d-card.js?hacstag=361776538153:2231:435962)
and in HA log:
Uncaught error from Chrome 119.0.0.0 on Windows 10 Error /hacsfiles/floor3d-card/floor3d-card.js:2356:4523 Object.onLoad (/hacsfiles/floor3d-card/floor3d-card.js:2231:531795) XMLHttpRequest.<anonymous> (/hacsfiles/floor3d-card/floor3d-card.js:2231:435962)
I just used the Export object to HASS plug-in to create the zip file. I extracted the zip file to my HA’s www directory under home (so homeassistant/www/home/) and pointed the card to look at the home.obj, home.mtl, and home.json files. After doing that the card takes a while to go to 100% then errors out as described above.
Any ideas?
EDIT
I got it working! The card had stuff defined in the other drop-downs, like object groups and entities and I think they were pointing to things that didn’t exist or something. I removed all that stuff and then it rendered. My obj file after exporting was like 400MB so it took like 20-30 seconds to load on my computer but then rendered it and I could turn on and off levels of the house.
Works pretty well there so I tried it on my phone and after waiting for about a minute of loading while the progress counter walked up to 100%, it sat there for about 10 seconds and then the HA app crashed to the Android desktop. I guess I don’t know what I expected… Pretty cool that it works on my PC though. I probably need to put my house model on a diet.
Hello @SpikeyGG, I feel sorry that you had to spend time to troubleshoot, since I introduced the sample modle loaded after the “add card” this is the most common issue and I should find a way to remediate.
Yes big models tend to consume too many resources (CPU, GPU, Memory), on an average device a model above 100mb will not work smoothly.
Hi
I find this card very interesting.
So i am going to make a dashboard with it.
I want to make a dashboard with whole building in main display.
Then there should be a chip card to select camera position.
I have already tried two ways to do this.
One is to have several dashboards.
The other was to use conditional cards with several floorplan cards.
Booth works fine but this is not so optimal solutions.
I know that there is zoom area function but i don’t think this look nice.
I want to select this outside the floorplan view.
So my question is.
Is there a way to set camera position with a variable that is set outside the card ?
Or can zoom areas be hidden in floorplan view and selected in a call outside the card ?
Hello @Kernal69, since a few months now I’ve stopped doing enhancement to the card (I have some time constraints). Anyway if you can post some images to better understand what you have managed to achieve with the existing functionality. This will help me better understand your final goal.
Ok
This is only on test level so far.
But here is a example.
Here i have used conditional cards.
It works very well but if you look at the code below you can see that it will be very large and hard to manage with many views.
So if a other way exist it is preferred.
I had to use helpers so i can set them on and off with the chipcards.
And then use the helpers as a condition.
A cool effect with using this is that if i want to zoom in to a room if for an example a varning appear i could set this helper from a automation.
That is a creative solution, I need to think how to better make the card interact with other UI components and states but as already stated I stopped doing enhancement, I only work in maintenance mode and only when blocking problems arise. It is time consuming and the user community is still limited. I thought that the card had more potential to become an official integration, but I have to admit that there are several unsolved issues (or even unsolvable issues, like the max number of lights, or the fact that a nicely defined 3d model is too heavy for the card)
Yes i understand.
I will use the way like i showed you , it works.
But i must say that this card is the best that has happened in Home assistant to creat a 3D floor plan.
It is so easy.
And if i change the floor plan or add something it is also easy.
So i hope you will continue to develope this card when you have time.
Maybe you should try to involve other to help you.
I think that the other way that exists to do floor plans is to complicated and is nothing i will use.
Hello, I was wondering if it is possible to add “type: state-badge”
the same thing as on 2D floor plans, but on the crad rather than having to display my variables on the walls. I’ve been stuck for a while and if anyone can help me, here is my program:
@TonAlternantDePocket , it is not yet possible to add badges in the model, nevertheless, the things that most people do, is to create a frame instide your model in sweethome3d and then bind your text tempeartute entity to the frame. If you want the temperature to be always visible and facing the viewer of the card, you need to explore the room entity which allows to show the temperature on top of the rectangle representing the room. Everything is explained in the documentation. Try and put here a comment if you still can’t do what you have in mind.
Bit late to the party and you probably already figured it out yourself, but you don’t have to repeat the input_select part at the service line…mine is working when it looks like this:
I have a 20mb GLB with a few lights and it works great on desktop browsers, but when using an iOS device with the homeassist app or browser the model appears to be in software rendering mode and incredibly laggy & unusable, kind of like how it is if you don’t enable hardware acceleration in chrome or firefox. Is this a known limitation and should I just get a Samsung tablet?
20 mb GLB should not be a big problem for the card in a recent iOS device. There is nothing I can do to improve, the WebGL based library I’m using (three.js) does HW acceleration whenever the device supports it. Have you tried to use the same model in obj format ? The support of GLB is really experimental in the card and there might be some collateral effects. Obj format is slower to load though (even when cached)
