Call for testing: new major feature - Spools Inventory Management

[yanshay]

📢 New Feature: Spool Inventory Management

I’ve just finished the first version of Spool Inventory Management — a major enhancement to the SpoolEase system that makes managing filament spools seamless and intuitive.

A few pictures

---

🚀 Highlights

• Automatic spool tracking
  SpoolEase now automatically adds/updates spool info in its internal database whenever you scan or encode a tag — no manual entry needed.

• Weight tracking made easy
  Keep spool weight updated to track how much is left or used, using one of the following methods:

  • Scan method: Scan the tag (into staging), place the spool on the scale, press the LEFT button.
  • AMS method: (requires configuring the slot with SpoolEase and showing the tag icon — the green rectangle at the top left) Remove a tagged spool from AMS — the system automatically fills the staging info. Simply place it on the scale and press LEFT button.

• Web UI for inventory
  Browse, filter, sort, and page through all your spools.
  Works well on both Desktop and Mobile

• Secure access
  Uses the same security key as the main config.
  Tip: You can set a fixed key via web-config.

• Export to CSV
  Download your spool data anytime.

---

🧭 Web UI Usage Tips

Most of it should be self-explanatory, but here are a few details that might be less intuitive:

• Data Fields:

  • Label: Advertised weight (if entered).
  • Current: Last measured total weight.
  • Left / Used: Automatically calculated based on initial data (if available).

• Filtering:

  • Click a field to filter.
  • Within a field: Comma-separated keywords (OR logic).
  • Across fields: Combined using AND logic.
  • Weights: Use ranges — e.g., set a Min value to find spools with enough filament.

---

⚙️ Technical Notes

• Requires a microSD card (FAT/FAT16 formatted) installed in the SpoolEase Console.
• Access the Web UI at:
  http://<device IP or device-name.local>/inventory
• Optional: Add your security key to the URL for one-click access:
  http://<device IP or device-name.local>/inventory#sk=<your-security-key>
  (The key is not sent over the network.)
• Data is stored under the store/ folder on the SD card.
  You can safely delete it during testing if needed to clear all data (and then scan tags again).

---

🧪 Ready to Test?

Flash both SpoolEase Console and Scale from:
🔗 https://debug.spoolease.io/inventory.html
(And make sure not to get confused between them when you flash)

---

💬 Feedback Wanted

Please try it out and let me know:

• What wasn’t clear at first glance?
• Was it easy to use?
• How does it work on your mobile? It’s currently optimized for mine, so I’d like to adjust it for other devices too.
• Suggestions for improving current features?
• Any additional capabilities you'd like to see?

Your first impressions are especially valuable — thanks for testing!

A picture is worth a thousand words

[pleasantone]

I'm doing something wrong, code updated on both Scale and Console.

Pull tagged spool from AMS, did not auto populate into staging, so scanned spool on console (also tried scale) and spool populates properly into staging.
Spool (empty weight) has already been set correctly, spool properly identified as PLA, but K was N/A (not 0.005).

Put spool on scale, wait for weight to stabilize, light turns blue, press left button, get "Technical Error. Failed to update filament weight."

I'm guessing I'm missing a step. Do I need to re-register/encode the spool as new?

Please note that when I installed the software, I did not erase the two devices, hoping to keep the spool weights and custom filaments. LMK if I need to.

Going to spoolease.local/inventory gives me an empty inventory.

[pleasantone]

Additional info:

custom filaments

P368baa0,HZST3D PETG Basic BBS2
P61fee1e,HZST3D PETG Basic
Pb4e9017,Giantarm TPU 2024-11-18
P9e57294,3D-Fuel PCTG Pro
Pa8c5a1a,SUNLU PLA Meta
P0d05c26,SUNLU PLA +20
P30ba88b,HZST3d PETG Marble BBS2
P84662d2,3D-Fuel PCTG Orca 121124
P370f475,3D-Fuel PCTG Pro Factory

custom reels

Sunlu - Plastic 2.0 w/rings and chip - 202g,202
HZST3D PETG - 167g,167

[yanshay]

I'm doing something wrong, code updated on both Scale and Console.

You probably aren't, I'd bet there are bugs.

Pull tagged spool from AMS, did not auto populate into staging

Did it have the tag icon on that slot (the green square at the top left of the slot)? So was it originally populated using SpoolEase?

, so scanned spool on console (also tried scale) and spool populates properly into staging.
Spool (empty weight) has already been set correctly, spool properly identified as PLA, but K was N/A (not 0.005).

What do you mean by 'empty weight'?
K showed N/A? that's strange, was it originally encoded on the same printer? This is not related to this version, so might be a bug.

Put spool on scale, wait for weight to stabilize, light turns blue, press left button, get "Technical Error. Failed to update filament weight."

There would be more information in the logs on that one. Can you do this again and send the logs?

I'm guessing I'm missing a step? Do I need to re-register/encode the spool as new? Please note that when I installed the software, I did not erase the two devices, hoping to keep the spool weights and custom filaments. LMK if I need to.

Nothing should be erased.
You are not missing a step. The encoding as new vs. not as new would only affect the data shown.

[yanshay]

I added an update 0.4.0-alpha2, please try it out.
It should fix:

1. Error saving tag to file under repeated save
2. The Safari issue
3. Reports to the display more store errors with more details
4. Some improved logging

Note: You need to erase the store folder on the SD Card since I changed the db structure a bit

[BigDi]

I direct flash 0.4.0a2 from 0.3.4 now I have a boot loop in the console (display unit)
BTW before I started I added a new FAT32 formated 4GB SD card.
I selected every time "erase device".

Before you will asking, yes I took the console version. I have to short-circuiting two connections (pin 6 and 7 from debug port) to flash again.
2nd try console output:
[14:35:24]ESP-ROM:esp32s3-20210327
[14:35:24]Build:Mar 27 2021
[14:35:24]rst:0x15 (USB_UART_CHIP_RESET),boot:0x2 (DOWNLOAD(USB/UART0))
[14:35:24]Saved PC:0x40041a76
[14:35:24]waiting for download
Then I try to reset and same problem. Serial connection will not stay.

Now I will try 0.4.0a1
Same...

Now I will go back to 0.3.4
This works.
Try again without erasing, this works!

[yanshay]

So what's the current status?
BTW - no need to erase when upgrading. This clears all configurations you made.

Unfortunately sometimes web flashing fail to the point of causing recurring boots.
In such cases best to try https://espressif.github.io/esptool-js/ to erase the flash and then retry.

[yanshay]

I released alpha3 at the same location to upgrade (don't erase when flashing).

I decided to add a numeric running id as well that I believe would be helpful for multiple reasons, for now, until formal release I don't support backwards compatibility so need to remove the store before use.

[yanshay]

alpha4 added delete spool operation

https://debug.spoolease.io/inventory.html

[somerockenguy]

Seems to work well so far, I only have 5 spools added of the 40 something I have. But I have a few note/requests after playing with alpha4 for a half hour.

• After getting everything installed I did have to return here to learn how to add the remaining weight to the spools. Having a built in quick start guide/tutorial might be nice for new users. Such as how/where I view the inventory database and to press the left button on the scale to update the weight of the spool in staging.

• An option to remove the password from viewing inventory, but still require the password to edit or delete anything.

• Everything worked fine on my Samsung S24 and desktop/chrome.

• I have a filament which is a super dark gray, with the RGB hex code as 161616, the cards view uses black text for this which is VERY hard to read.
  

• I would like the ability to edit the fields, such as adding notes, or fixing spelling/capitalization for brands/colors/subtype.

• The ability to add custom fields, such as a field with a date range so I can keep track of the last time a spool was dried, price, storage location.

• Clicking add spool asks me if I want to deactivate my account. This does not seem like intended behavior.
  

• The ability to add untagged spools and later add/associate with a tag. I tend to keep multiple of commonly used colors but keep them in the factory packaging until before first use.

[yanshay]

• After getting everything installed I did have to return here to learn how to add the remaining weight to the spools. Having a built in quick start guide/tutorial might be nice for new users. Such as how/where I view the inventory database and to press the left button on the scale to update the weight of the spool in staging.

This will arrive, except things are still changing and maintaining correct docs would be difficult at this time.

• An option to remove the password from viewing inventory, but still require the password to edit or delete anything.

I'm trying to keep things secure with http (can't do https on internal network device w/o supporting networking that not everyone have) so the security key is necessary, however you can use add to the url #sk= (which doesn't go over network) and it will "login" automatically.

• Everything worked fine on my Samsung S24 and desktop/chrome.
• I have a filament which is a super dark gray, with the RGB hex code as 161616, the cards view uses black text for this which is VERY hard to read.

I believe I fixed this issue - are you by any chance using dark mode? I changed all coloring now to support both dark and light mode, should be released in next alpha update. I hope it will solve this for you as well.

• I would like the ability to edit the fields, such as adding notes, or fixing spelling/capitalization for brands/colors/subtype.

First, I hope you know it is possible to edit when encoding.
Second, there's a question about editing since the tag doesn't get updated when you just edit in the inventory web application. This will create discrepancy between what's encoded on a tag (which you can scan and view) vs. what would be in the SD storage, so I'm not sure it's a good thing to do with spools that have tags. Open to ideas.

• The ability to add custom fields, such as a field with a date range so I can keep track of the last time a spool was dried, price, storage location.

Custom fields will probably come later down the road, it opens a large set of issues that I don't want to get into now before I get into another major feature I plan. But if there are fields that make sense in context of 3D printing that would benefit everyone I'm open to consider them. Last drying date for example sounds to make sense, I need it myself. Feel free to make suggestions.

• Clicking add spool asks me if I want to deactivate my account. This does not seem like intended behavior.

Heh, yeah, it just a placeholder copy/paste of code I forgot to remove before I add the ability to add untagged spool (for those close packages).

• The ability to add untagged spools and later add/associate with a tag. I tend to keep multiple of commonly used colors but keep them in the factory packaging until before first use.

That's what that button is there for, plan to add it soon.

[yanshay]

I also see the mobile sizing doesn't look good on your mobile, need to take care of that as well.

[yanshay]

Release alpha5 - same spot

Changed:

1. Proper (I hope) support for dark/light mode
2. When encoding, if there is anything on the scale (also when re-encoding, so be careful) it updates the current weight immediately. So first encode will already contain the initial current weight
3. Removed a few buttons on mobile that I don't think are needed on mobile (CSV, Backup, Add - which is not ready yet)
4. Delete accessible on mobile

[yanshay]

Released alpha6 - same spot

Including:

• Add spool - for unopened spools (will still need to build the full flow of encoding later on from an unopened spool data)
• Edit spool information
• Security-key as blocking modal - instead of at the top
• Adjust to AMS spool loading bug/changes - unrelated to inventory, it seems like Bambulab instroduced a change, maybe a feature maybe a bug, where loading a spool does not always perform Bambulab RFID reading. This prevented spoolease from configuring slot. This change make it work again, hopefully not hurting anything in any way.

On The new add/edit are not fully mobile ready though usable, this will be taken care of in the future.

Important - be aware that store format will still change so don’t invest too much work on loading information in as it might not be backwards compatible. That’s why it it in alpha/testing.

[yanshay]

Released alpha7 - same spot

Changes are mostly:

1. Fix - when taking out a tagged spool from AMS, it enters staging as 'unloaded' (previously not always took place) + other load/unload issues caused by the same underlying bug.
2. Staging timeout is reset when loading spool, so AMS reading filament will not sometimes complete after the timeout ends. So user gets the timeout (60s) to put spool in and independent of AMS reading time (up to 60seconds)
3. Fixed store issues where values would get lost when other values not filled

[yanshay]

Released alpha8 - same place

This include meaningful changes that are prone to bugs:

1. Prevent editing in inventory of technical info of already tagged (encoded) spool - to prevent too important discrepancies between tag and inventory information. For now, only the Note is editable after tagged. Changing the others can be done only when encoding the tag.
2. Add editing of core weight to inventory when adding spools
3. Change underlying db file storage of spool extra information file naming to use id instead of tag (to support untagged spools)
4. Encode from new untagged spool inventory - this is a major change. After adding a new unopened spool to the inventory it is possible to encode it, by pressing "Use ID" and filling the spool ID (only untagged spools are allowed for now). This will fetch the information and use it when encoding and attach the tag once encoded to the inventory spool. If the same tag was already used before for another spool the tag will be striked out on the previous spool and the tag will be assigned to the new spool.

This last change is a major improvement and provides a great flow IMO from buying a spool, loading the spool into SpoolEase inventory, then later on encoding and using it.

It is also technically a bit complex and involves many use cases (like tag loaded, then unloaded, then re-encoded, etc.). The ID should follow the tag everywhere. There are probably bugs and more complex use cases I didn't think about, happy if you can think of those and let me know.

I also hope/think the DB format has not stabilized, but can't guarantee yet.

[yanshay]

Released alpha9 - same place

This include quite a few improvements and fixes (and probably some new bugs), most notably:

• Encode a tag from scratch, not based on a slot or staging. When staging is empty, press Encode and then Staging, which will display Start Clean.
• Allow setting slicer filament name in inventory, including both Bambulab default filaments and your custom filaments configured via Web Config (see upgrade note).
• Improved encode screen editing: all fields can now be set directly from mobile, using the same layout as inventory. Add/Edit is now more mobile-friendly.
• Inventory records now include Add Date/Time (currently, requires internet to fetch global time, in the future this requirement will be somewhat relaxed).
• Backup now includes all files (restore still not implemented).
• Simplified adding multiple inventory records consecutively, either continuing from previous data or starting fresh.
• Inventory now defaults to sorting by ID.
• Encoding is supported even before a printer is connected, or without configuring a printer at all — enabling inventory and weight tracking standalone, without a Bambu printer.

Upgrade Note:

• If you’ve configured custom filaments (in Web Config or in the Mobile Tag Web App), reconfigure them to include temperature settings for full functionality.

I'd be happy to hear feedback on changes/additions including criticism.
Documentation is still not available since things are still going to be updated and I don't want to chase documentation.

[yanshay]

Released alpha10 - same place - https://debug.spoolease.io/inventory

Released quickly after yesterday, as it includes two useful features:

• Added encode date to store and tag. This will be useful in the future to see if something changed that's worth reencoding.
• Added color names with the ability to set RGBA from them in inventory — making color entry easier. A small internal list of colors helps pick a general color area. Selecting a name and pressing the button to the left of the field (with arrows pointing up and left) copies the color code to the field, from which you can refine with the color picker. Pressing Enter in the color name field does the same. This applies only to untagged records or when encoding "from clean”.
• Minor fix: removing a printer in web config now enables the Apply button.

[yanshay]

Released alpha-2 for the scale for the inventory scale version at https://debug.spoolease.io/inventory.html .

The only change is the filtering out of the load-cell data that comes up once in a while and turns on the screen. Nothing major, it just annoyed me so took care of that.

[yanshay]

Released alpha-11 for console (same place, https://debug.spoolease.io/inventory.html)

• Add IGMP packet support — enables console-to-scale connectivity under complex network conditions (pending user confirmation)
• Remove encoding issues when switching to terminal view
• Allow manual configuration of filament info (color/k/material) from tag only if a spool is already in the slot
• Improve slot status visualization (in both main spools view and AMS selection)
• Require label weight to be filled in inventory dialog
• Improve error handling in inventory spool editing dialog
• Change order of controls in inventory dialog — may need further mobile adjustments later
• Fix: In inventory, slicer filaments didn’t appear if custom filament list was empty
• Prevent color name changes in inventory when spool is already tagged
• Major update to console encoding logic and UX to better align with inventory record implications
• When encoding from staging, allow all fields to be changed — enables using an existing filament tag as a base
• Various other minor inventory issues addressed

[yanshay]

Released alpha-20 for console (same place https://debug.spoolease.io/inventory.html).

It includes a major new feature (at least complexity wise). If you'd like to test this new feature, please read everything carefully, especially the "IMPORTANT" section regarding the backup.

---

I've just released an early (not final) alpha version with a major new feature:
SpoolEase now tracks filament consumption during AMS prints.
(External spool support is not tested and likely doesn't work yet— might even crash SpoolEase repeatedly until print ends, but that's less critical for now.)

UI

• On the display, when a spool with a SpoolEase tag and weight data is loaded, it will show the remaining filament—just like in the inventory. (This part is unrelated to the new feature).
• Currently printing filament circle shows with thick border, and same on the small squares at the top in the AMS selection area. (Also unrelated to the new feature).
• During a print using such a spool, filament usage is tracked layer-by-layer and on filament switches, so if you cancel a print you still have an accurate reading. The display and inventory update with the remaining weight in real time.
• If there's not enough info to calculate remaining weight, the display will show a negative number, indicating how much filament has been consumed in the current session (since the spool was placed in AMS).
• The inventory app now shows two temporary columns: total filament printed, and filament printed since the last weight update. It's mostly to help with debugging.
• Weighing the spool resets the "printed since weight" counter and updates the base weight with the measured value.

Technical Notes

• The feature is enabled by default, but can be toggled per printer in the web config.
• You can configure, also in the web config, where to fetch the .3mf from—FTP or cloud. HTTP is supported on newer firmware without Dev Mode. This makes SpoolEase useful even for users who aren’t on old firmware or don’t want Dev Mode. They have a lot of value and miss only the filament configuration.
• Currently, .3mf processing is limited to one print at a time (this will be improved). You can start a new print after processing of 3mf has completed but you don't have a way of knowing when :). This limitation will be resolved soon.
• Processing happens on the console, so it supports only systems with up to ~2 printers (maybe 3, but not sure) due to memory limits. However, the code already supports offloading processing to the scale, which has enough memory for more printers.
  If you have more than 2 printers and want that version, let me know—I'll build it. Eventually, jobs will be dispatched automatically to the scale when needed.
  Good that we have a multi esp32 system to build an esp32 based super-computer :)

Current limitations

• Skip object is not supported - will not consider the skip. So worst case, weight the spool after print.
• If printer turns off and restart and continues print from where it left - not sure how it will work, never tried it. Worst case you can weight the spools.
• Print gcode directly from sdcard - probably not supported, not sure what happens in such case. May be easy to support this case.
• Printing from external spool probably won't work - likely to crash SpoolEase (even keep crashing until print finishes).

---

⚠️ IMPORTANT

• This feature is unfinished, treat it accordingly.
• It modifies the DB structure, and downgrading later if requried may not work. It might, but assume it won't.
• Therefore: before testing, take out SD card from the console and backup the entire STORE folder to your PC, then put it back.
  Until you're confident in this version, avoid adding new spools in case you need to downgrade an use your backup (which will not include the new spools if added).

---

Final Notes

• Testing I made is limited. I verified it works for small multi-color prints and that .3mf processing handles large prints (>3 days prints)—though I didn’t run those long prints, only tested the 3mf processing.
• It was only tested on P1S. X1/A1 may behave differently—I'd love your feedback there.
• Start small:
  1. Single-color print (e.g., 10mm cube)
  2. Simple multi-color print (e.g., 3 tiny cubes with different colors)
  3. Then move on to real prints.
• As you test, before you print, please write down the slicer estimates and verify the weight loss of the spools is the same. There might be slight difference since the slicer ignores a few extrusions, but it's minor difference.
• I'm interested then receiving some information on what you tried, how accurate it was, etc.

Enjoy,
Let me know if you run into any issues.

[Scharunge]

Great work. I can confirm that printing from sdcard is not tracking filament usage. I started a print via Bambu Studio and tracking was working fine. I had to stop the print and later started it again fom sdcard. Filament tracking didn't work and I was not sure why. Only after reading this it made sense.

[yanshay]

Great work. I can confirm that printing from sdcard is not tracking filament usage. I started a print via Bambu Studio and tracking was working fine. I had to stop the print and later started it again fom sdcard. Filament tracking didn't work and I was not sure why. Only after reading this it made sense.

Thanks, Please report as an issue or in Discord so this discussion will be mainly for announcing updates and explanations (no docs yet).
If it's on X1 then currently ftp doesn't work and you can use http. Printing directly from sdcard is not supported at this time. If it's something else please report as issue or on Discord.

[pmitCZ]

Great project :-) I have version 0.4.0 - alpha 38. The PA(K) parameter is not displayed on the console when I click on the AMS position. It is only displayed on the external position. I am talking about the detail, I can see PA(K) on the home screen. Just to add, I have two AMS and it is the same on both.

[yanshay]

Can you open a separate issue about that to keep this discussion for alpha announcements?

Please include there also what printer you use and any extra configuration + what exactly are you doing and the symptom.

[yanshay]

🚀 Released SpoolEase alpha50 for both Console and Scale!
It's available at https://debug.spoolease.io/inventory.html

This version focuses on easing the complexity of encoding as SpoolEase has eveolved over time and what was good in the past doesn't fit best now with the inclusion of inventory, better encode web app, and more.
While bigger simplifications are planned (but will take more time), based on user feedback I’ve made a few small but meaningful changes to make the basic flow easier to use.
I also tackled one of the most annoying tasks: writing documentation 📖. Far from being exhaustive but covers the basic flow.

👉 Flashing is in the usual place.
👉 Documentation starts here: https://docs.spoolease.io/docs/quickstart/basic-usage-flows

✨ Also in this release:

• AMS HT support (experimental — still waiting on feedback from users who can print with HT, which seems rare these days).

⚠️ Note: I had to revisit many older, delicate parts of the code. Bugs are expected.
If you hit something that doesn’t make sense, please report it — it might be intentional, or just a bug.

[racerman76]

Hat die Version versucht zu flashen , Gerät ist immer in Neustart gegangen und Bildschirm blieb schwarz .

[yanshay]

Check out the troubleshooting page in the docs

[racerman76]

Laden und Entladen gibt es beim HT keine Probleme .
Wäre schön wenn man die Daten der Spulen im Inventar auch alle anpassen könnte .
Warum werden nach dem Aktualisierung des Spulengewichts auf Scale ( linke Taste) , beim Laden im AMS dies nicht wieder auf Spool Ease angezeigt ?

[Pedro-Newbie]

After some hesitations i jumped the bandwagon and ordered the parts for the scale. The assembly went very well but I had some problems with flashing, the process kept hanging on "preparing instalation".
Lucky me I found the solution as described bij user Drolax in this post: #44 (reply in thread)
Now I'm entering all my filament rolls into the inventory, a tedious task but giving me plenty of experience. For now I take a break after 57 rolls (after entering, weighing, encoding etc. I also have to pack them again in the vacuumbags.
I will post my findings in the next weeks but all looking very good. Only have to enter again the pressure Advance settings.
Thanks for the very good work!

[Pedro-Newbie]

Is there any news on the development? My version console alpha 77 and scale alpha 51 are working fine except the fact that the scale often disconnects, even with the scale and console placed ~1.5 meter distance from each other.

[yanshay]

Yes, lots of updates — time to share them here.

Version 0.5 (currently a pre-release) replaces the 0.4 alpha. It’s a major update — backward compatible but with a new approach (encoding the tags is not required any more, just optional for a certain feature), added features, improvements, and bug fixes.

(Among the fixes is better communication between Scale and Console under not best WiFi conditions. It’s still new, so feedback will show if it fully resolves previous issues.)

Important: Review the documentation BEFORE upgrading and perform the folders copy as described there:
🔗 https://docs.spoolease.io/docs/next/Technicalities/upgrading

Read it fully, then go through the updated docs to understand the new flow.

Flashing can be done as usual here:
🔗 https://debug.spoolease.io/0.5/alpha.html

Be sure to flash both Console and Scale.

[Pedro-Newbie]

Updated both items and I like the system very much but.....
the scale keeps disconnecting a lot and sometimes SpoolEase Console crashes/freezing. I don't think the disconnecting issues are the result of a bad wifi connection

[yanshay]

What version did you update to?
Regarding disconnect - version 0.5 should be better (need both console and scale).
Regarding crash - I’ve seen it myself once or twice. If you can have the system collecting logs as it happens it will help, otherwise, no solutions at this time.

as for wifi, the Esp32 is sensitive to various WiFi conditions. Also other devices. So if you are on 0.5 and it still is an issue, try for some time reposition the devices and see if issues continue.

also, don’t position them too close one to another. This has also seen to cause issues.

[Pedro-Newbie]

I updated from alpha 77 and 51 to console 0.5.0-b13 and scale 0.5.0.-b6.
Both units are about 1.20 meter distance from each other.
I will reposition both devices and go on further testing.
Thank!

[Pedro-Newbie]

I updated OTA the console to 0.5.0-b.16, that went all well, but when I tried to update the scale in Chrome this didn't work anymore, there was no longer u pop-up to choose the USB port. Updating via Edge works fine.
I have no idea if this is a chrome issue or the website

[yanshay]

It looks like a browser issue or USB issue.

[Pedro-Newbie]

Already solved, I had an extension installed named: Toggle JavaScript. This was enabled to bypass a certain javascript.

[Techeternal]

Considering getting involved with your project. This really looks promising! Any ideas why this has not been picked up by more people yet being there is not a good inventory system out there?

[yanshay]

Interesting question, I think:

1. I am not really trying to push it so it is not widely known - that’s probably the main reason. Actually it was never published anywhere as an inventory management system.
2. Build requires people to be a bit technical, even minimal soldering is a barrier to many.
3. When it comes to simple inventory management (so no NFC, no scale, limited printer integration) there are other options including just maintaining a spreadsheet.

[Pedro-Newbie]

I just want to say that since the last update(s) to 0.5.0-b.16 for the console and 0.5.0-b.7 for the scale I didn't have any disconnects so far.
It looks very promissing so far!

[yanshay]

That’s important and good to know. Thanks

[Pedro-Newbie]

Unfortunately, I cheered too soon. The scale now refuses to connect at all. The console doesn't display a message that the scale is disconnected, but when I look under 2 Scale(s) information, I see the following:
Scale not available

Scales on network (close & reopen to update)
192.168.2.19 - scale.
After powering up the scale starts and the red LED flashes a few times red and green and finally the red LED lights up brightly and stays this way.

So the system recognizes the scale but won't connect.
I've now installed console B.18 and reinstalled Scale B.7.

[yanshay]

Flashing red means not connected to WiFi.
Constant red means not connected to console.
If console doesn’t see the scale on that screen that shows scale and also after restart it means some network issues. It simply doesn’t see the ssdp packets sent by the scale so seems like networking issue. If console does connect to printer but doesn’t see scale it seems like scale is somehow masked.
Try to connect to the scale web config from a desktop that can also see the console.