Hello @FortranFour, thanks for your words, it helps me to stay motivated in maintining and evolving the project.
I’ve tried with Blender myself but, unfortunately, it was a dead end. Why ? You can solve the axis flipping by unchecking the option I have highlighted in the picture below.
Nevertheless the export to glb breaks a number of other things that cannot be fixed by parameters. One critical problem is the object_ids. They are not preserved and they are not following the Sweethome naming from the .obj export. So, it is unusable for me. I reckon that the current way to export to glb I have recommended (nodejs routine) is a little complicated, but I’m surprised it is not working on MacOS (flipped axis): are you clearing the cache after you tried the blender and the nodejs version of the file ? Another option is to add a version in the card (ex. home.glb?ver=1 then 2,3 etc) or change the name of the file (ex. homeblender.glb and homenodejs.glb) ?.
I’m trying to include a glb exporter in my ExportToHASS plugin, but this is not an easy one and it will take time.
