home.social

#firebrick — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #firebrick, aggregated by home.social.

fetched live
  1. Idly looking around for news of possible updated #Firebrick models, I keep stumbling across this reference to some alleged comments by @revk made in 2021.

    forum.kitz.co.uk/index.php?PHP

    5 years on, there's still no sign of a putative FB2900 replacement AFAIK. Is anyone aware of anything on the horizon?

  2. One of the most *fun* options we have in #FireBrick to be honest.

  3. @simonzerafa @ap We have evil bit in firewall rules in #FireBrick (yeh, my idea).

  4. For Colour Collective this week, a splash of #Firebrick

    MEUSE
    90x64cm acrylic & oil on canvas
    shown recently at the Society of Scottish Artists Annual Exhibition at the Royal Scottish Academy
    #Edinburgh #Scotland

    #art #painting #cityscape #infrastructure
    #firedoor #ccfirebrick

  5. Just updated 84 #tasmota at home to 14.4.1

    Some still 8266, but a lot are ESP32.

    And quite a few ESP32 ones needed a manual upgrade to 12.5, and old partition wizard, and then upgrade to 14.4.1, but at least all now use safe boot partition logic, at last.

    But every single one was success without having to faff about behind any light sockets or in the loft.

    To be honest, that is impressive.

    I also have all on #HomeAssistant now (which meant some upgrades to #FireBrick MQTT along the way).

  6. Like a bad smell I hang around on an IRC channel ostensibly for my ISP @aaisp and accidentally moused over the word "firebrick" that one of the denizens had used. A coloured square appeared.

    This ISP happens to sell routers called which are the exact colour that was popping up! I figured I'd (eventually) turn on protocol debugging to see if they were inserting some IRC voodoo, because that's just the sort of geekery I'd expect from an xkcd:806-compliant organisation.

  7. I just saw this video re #Starlink, youtu.be/izSXVgxgaF8 and I agree, it is pretty cool. And the latency is actually relay good for any satellite system to be honest.

    I have it as a backup, but with all backups you have to ensure they are used/tested incase they are not good when you need them.

    For me, Starlink is used pretty much 100% for streaming #Stargate and the like on my TV. My router (#FireBrick) has my TV set to always go via Starlink to ensure the backup is being tested.

  8. @gruff Ah, well done, did tech help with this as it is a pretty standard question... #FireBrick can do whatever you want with rules if you try :-)

  9. I know some of my followers have a #FireBrick - we have launched @firebrick now, so do follow if you need FireBrick chat/help.

    I'm going to try and get the other developers on there directly.

  10. Cool, I can ping6 my FireBrick from outside via my #Starlink (UK, Wales). Around 30ms response. I have put it in router bypass mode, and indeed, as you would expect, no filtering/firewalling (that is why I have a #FireBrick).
    I have not finished all the updates to my DHCPv6 client, so was surprised, but they seem to have switched to using SLAAC, which is way simpler, and just works.

  11. @AlisonW I was once woken up at 06:30 by Royal Mail delivering a #FireBrick from #AAISP!

  12. And one of the libraries I am using has not been touched for years and no longer works with ESP IDF v5.0. Solution is a different library that works (with a few bug fixes). But it is totally different and so my code had to have a lot of changes to work with it. And people wonder why #FireBrick code is written by us from lowest level device drivers upwards.

  13. @Bez78829056 It is just turned on. I have seen RAs for a long time advising DHCPv6, but only recently seen DHCPv6 answer for IA_NA and IA_PD. Currently #FireBrick is not happy with the lack of rapid commit but that will be fixed very soon. But most kit, even just an iPhone, gets an IPv6.

  14. @ben OK, well in this case the broker is my code, hence this coming up at all. #FireBrick

    It would be a doddle, obviously, to allow my broker to have a websocket front end connect first then send the raw MQTT packets over web sockets. I may add that anyway.

    But to be honest if I managed to do that it will only be a small extra bit of logic to make it send and receive JSON rather than raw MQTT packets.

    And that is just way simpler for an app to use with no library needed.

    I may do both.

  15. @coopernetes Ha, well, we went further and made our own routers #FireBrick from scratch - coding Ethernet, IP stack, the lot. They are really cool now. But it was hard work, and we have a really good team on it now.

  16. One of these days I'll get the hang of weekends. I have spent this morning making a web socket based MQTT "console" for the #FireBrick web interface. Quite pleased with it so far. Probably needs a few tweaks to be prettier, but will help a lot with people not used to MQTT and not having a handle MQTT command line tool. Alpha release issued.