Found while setting up modules. Setup: MacBook Pro M4 Max, macOS 27.0.1, UltraWorkSpace 1.0.10 (the macOS beta, see my posts in [Beta Testing Invitation] UltraBARX for macOS); CoreBar LineOS 1.0.3.
1. SenseCube humidity sensor always reports 0 %
The SenseCube itself reports humidity correctly (e.g. 35.4 % in the SenseCube card and in the device list over the API), but the separate humidity sensor device the bar creates for it is always 0.0, so a humidity/temperature card shows 0 %. Temperature works.
Likely cause: in SenseCubeModule (launcher 1.0.3) the humidity update copies the value into the SenseCube attribute but sets the humidity sensor to a constant, mHumidityAtt.humidity(0.0f). It should pass the reading (f.floatValue()), like the temperature update just above it.
2. VivoCube stays blank if its Wi-Fi is set to the home network
UltraWorkSpace → VivoCube → Config → Network lets you put the cube on any Wi-Fi. But a cube Deploy always tells the cube to download its layers from the bar’s hotspot address (http://192.168.43.x:8080/tgz/<serial>.tgz), so a cube on the home Wi-Fi can’t reach it: it answers “Config download started” and its screen stays empty, while button actions still work. Moving the cube to the bar’s hotspot (AndroidAP_xxxx) fixed it.
Suggestion: serve the download on the address the cube is actually on, or warn/limit on that Network page.
Small request: a setting to turn off the chime that plays on every module button press.
If the standalone humidity card isn’t displaying, we recommend deleting it and then adding it again.
If VivoCube is unable to update its configuration file, we recommend connecting directly to CoreBar’s hotspot to configure and use it for now. I’ve reported this bug to our engineers, and we’ll also try to fix it in a future release.
I’ll also pass along your suggestion for an option to turn the sound played when pressing a module button on or off.
Please feel free to contact us if you have any other questions or suggestions. Thank you for your feedback!
I’ll try deleting and re-adding the humidity card and let you know if it still shows 0%. I’ll use the CoreBar hotspot for VivoCube in the meantime.
Also, I posted a few more issues in the macOS beta testing thread. The big one is why the Mac app won’t connect on Apple Silicon Macs (the “Offline” / API timeout errors). I tracked down the cause and listed some fixes there. I also found that all the app widgets are greyed out and can’t be added to the bar. Could you pass those along to whoever’s working on the Mac app?
Quick question though: was the beta thread the wrong place for those? I’m locked out of posting there now, I think because new accounts are capped at three replies in a row. Let me know where you’d like Mac beta bugs to go, whether that’s a new thread here, the beta thread, or straight to you, and I’ll use that from now on.
