Headworx

Whenever I come across a discussion that involves wireless communications over the Thread protocol (such as this one ), there is almost 100% chance people don't understand the underlying physics and traffic patterns. This is the result of Thread marketing since 2014, highlighting the IPv6 protocol as its key strength. And typically it goes like that: "Thread is based on IPv6 and there are more IPv6 addresses that grains of sand in the Universe". And people read this "because Thread is based on IPv6, it is a highly scalable wireless protocol". Treating the potential number of static addresses equally to the dynamic situation when these devices actually send data. If we consider the networked lighting control domain, the most prevalent pattern today is to have a motion sensor in every luminaire. The motion sensor usually has multiple functions: it is a motion sensor of course. But it also is a light level sensor enabling daylight harvesting (or dimming lights down...

Once considered the greatest thing since sliced bread, notifications have spun of of control. Meant to be the (most) important stuff, have been sliding into complete irrelevance. And have become totally distracting and annoying. The operating systems (including the flagship Android and iOS), even with their recent Artificial Intelligence (AI) features have failed to cope with the notifications' torrents. Out of box, every app wants to send notifications about everything - this is of course the fight for potential revenue through engagement and conversion. Yes this can be managed. But only theoretically, as users really drown in the ocean of options they do not understand. On top of the notifications' options there is the hierarchy - you have favorite contacts (meant to always go through), you have time - or activity - based profiles (iOS calls them focuses). Barely anyone understands the combinations. Then there are the super annoying users of (increasingly more popular) instan...