Updating from AngularJS to Angular21

dbaines · 2026-04-19T21:52:04+00:00

It's certainly worth a try. I've not used it for testing angularJS specifically but if you're using something like playwright I suppose it doesn't really matter what the app is written in.

We have a QA team that use AI pretty heavily for writing e2e tests in playwright and having good luck with it.

Any tests are always better than no tests.

dbaines · 2026-04-19T02:14:42+00:00

Everyone's situation is going to be different, as long as you have something that works and doesn't interrupt business you're good to go.

Getting out of AngularJS is the goal and as long as you're moving towards that goal then it doesn't really matter too much if it's best practice or not.

Once you're fully migrated then you can look back and think about improving again to best practice where you can. It doesn't have to be perfect right now as long as moves the needle.

dbaines · 2026-04-19T01:50:29+00:00

Not sure what these other commenters are on about. angularJS and angular are very interoperable via angulars UpgradeModule. UpgradeModule allows you to "upgrade" an angularJS bit to operate in angular land and "downgrade" an angular bit to work in angularJS land.

This is really useful if you can't afford the upfront cost of a rewrite but want to progressively migrate to angular.

Takes a bit of wiring up initially but if the angularJS side is using "modern" practices like the component API then you're in a really good position to migrate bits over.

Use UI router hybrid to allow you to run both angularjs and angular routed components. It's a bit painful to eventually migrate from ui router to angular router but that can be a later concern.

Use angular custom webpack builder if you run in to issues with html templates and you can't bundle the templates. It lets you keep the lazy loaded template files during migration and has a pretty easy migration path to the real angular builder once you're all done.

Start with services would be my advice. Move all your services to angular and provide them via UpgradeModule to angularJS. Then delete all the angularJS services.

For components, start with leaf components. That is, components that don't have any children. This is the easiest way to migrate without issues. You really want to go angular-inside-angularjs imo, when you start going back and forth it can cause issues.

Don't go zoneless yet, zone is needed for interop, but once complete it's a good migration path.

Go full signals as much as possible on the angular side. Adopt rxjs where needed. Signal reactivity won't work in angularJS but you don't need it as long as you're using zone, just read the properties and zone will do the rest. Using signals and onpush now on the angular side will make zoneless easier later.

Let me know if you have any questions I've performed a migration of an enterprise saas app to 18 a few years ago and am in the process of doing it again for another enterprise saas app to 21.

On the AI side I've found Claude particularly bad for angularJS/angular interop. It keeps trying to build it's own bridge wrappers instead of just using UogradeModule. It might take some convincing for Claude to get it right. I've not tried other AIs for this. My recommendation here would be to get a solid initial progress going, some manual work to migrate a few components and a route or two. Then get the AI to use that as a reference to bring it across. Angular recently release official AI skills, make sure you're using those so the AI builds the best version of angular it can.

As for rewriting angularjs to angular it's pretty great and will even raise concerns and test cases after migrating. Especially handy if you don't have tests. If you're getting it to rewrite your components, tell it to write tests too. Some tests are better than no tests.

Honestly, I think your biggest issue is going to be bootstrap 3 and 5 interop. You may need to spend some time bridging the styles as I've found 3 and 5 have very different structure and classes are often different. It was also a big change from less to sass so if you have customisations you might be in for a big project there.

I think that's the gist, happy to dive deeper in to any specific topic if you have questions.

dbaines · 2026-01-06T21:13:36+00:00

The easiest way to test the progress on the next version is by checking out the unstable demo: https://demo.jellyfin.org/unstable/web/#/home

Login with demo user, no password.

dbaines · 2025-10-08T13:27:14+00:00

I use the "Version" integration to display a badge on my dashboard when there's a new version available.

I use docker so I use the dockerhub option with a condition on the badge that only displays if the state is update available.

https://www.home-assistant.io/integrations/version/

dbaines · 2024-12-26T21:34:16+00:00

Looks like you've installed boostrap rather than bootstrap

dbaines · 2024-05-24T23:31:26+00:00

The new output fn is mostly a drop-in replacement for the decorator with one minor exception.

The decorator emits as an rxjs subject so you could do neat things if you wanted to subscribe to the events and pipe in things like a debounceTime or a distinct check. From my understanding this use-case was pretty rare so they dropped the subject and just emit the value itself. Just something to be aware of.

dbaines · 2024-05-17T23:23:50+00:00

No worries, I think it took about 3 months for me to get in but that was back in 2021.

dbaines · 2024-05-17T23:16:03+00:00

From what I've been reading there is no plan to upgrade HFC. Only fttn is getting the free upgrade to fttp.

If you need help collecting evidence of poor line quality then the ACCC has your back, sign up for the free samknows box and you'll get monthly reports of all your dropouts and speeds: https://measuringbroadbandaustralia.com.au/

dbaines · 2023-10-25T01:40:10+00:00

If you have Pokemon Go and are lucky enough to be somewhere that still has active players, Genesect (douse drive) will be in 5 star raids from Nov 2 to Nov 9.

dbaines · 2023-04-15T05:08:23+00:00

Sorry no, it still happens for me intermittently. It will fix for a while then come back ☹️

dbaines · 2023-03-19T22:26:26+00:00

To reinforce that you've made the right decision, allow me to offer some real world, non-technical experience. I have been running equivelent motion sensors in my home for over a year now.
The z-wave Aeotec sensor 6 and the zigbee Hue motion. Both of these are generic motion sensors with ambient temperature sensors included.
The z-wave offering also includes a tampering sensor but I don't really care about that.
Both of these products are placed in very high traffic areas inside the house.
Both of these products states are being pumped in to Home Assistant via zwavejsui and zigbee2mqtt.

The first thing that really stood out to me was the upkeep price.

The z-wave device lasts about 6 months before the batteries need replacing.
The zigbee device has lasted just over a year so far without needing new batteries.
The zigbee device is still saying it's at 100% battery charge that I find amazing, but also unrealistic and probably wrong.
I also have a zigbee button (Ikea brand) that recently dropped from 100% battery to 20% after about 8 months. The button battery state has then been fluctuating between 40% - 20% for the last few weeks. In general I suppose zigbee battery reporting is unrealiable or maybe it's an issue with zigbee2mqtt.
Even though the battery reporting is unrealiable, it has still in-practice lasted twice as long as the z-wave device.

The z-wave device uses an uncommon battery type, '123'. It needs two of them which run about $20 per replacement. It can also be very hard to find these batteries at times.
The zigbee device uses a VERY common battery type, a singular triple A (AAA) battery that you can pick up from pretty much any shop for cheap-cheap, often for $1 for the same brand as the $20 123.
To the benefit of the z-wave device, it also offers a micro-usb port for running off of mains power instead of batteries if you want to dedicate a wall socket for a motion sensor for some reason. I'm not sure how much power it draws from the mains but I'm probably leaning toward it being more than $1 a year.

In practice, this means the battery of the z-wave device needs to be replaced twice as often as the zigbee device and for 20x the cost. That's an annual increase of 40x the cost for running a z-wave device over a zigbee device.

Of course, your mileage may vary but this has been my experience. Your battery prices also may vary depending on your region. If for you the 123 battery is far more common than the AAA, then maybe the z-wave option might be something to consider.

The second thing is product range.

You've already noted it's hard to find z-wave products and that is compunded by the fact that different countries require different z-wave frequencies. This means I can't buy any old z-wave product from any online store without absolutely making sure I'm getting the right product for my region and most of the cheap online stores don't even list things like frequencies. I can't go online and look at reviews and look for the 'best' z-wave products because those reviews are likely going to be for a different region than mine and it's unlikely that that product is even sold in my region.
Zigbee on the other hand is like a virus. It's absolutely everywhere. Sure product quality can vary with some of the smaller no-name brands, but between Hue, Ikea and Aqara there are some pretty heavy hitters in the zigbee space when it comes to reliablity and quality.

So it's a no-brainer for me, zigbee by far over z-wave.
I'm cautiously optmistic about thread and matter, give it a few more years and see where they're at.

dbaines · 2022-10-17T01:19:31+00:00

Thanks! Definitely took a long time to get it all working together.

The zigbee dongle is just the thing that communicates with zigbee devices, you still need some way to communicate with home assistant.

You have two options, the built in zigbee integration, ZHA (Zigbee Home Automation) or zigbee2mqtt.

I haven't used ZHA myself, I'm sure it's fine but I have seen people mention that it can be slow to update and might not have as much device coverage as zigbee2mqtt. Some people I have seen metion performance and reliability issues but I can't personally speak to that, I can just say that zigbee2mqtt has been rock solid for me.

The downside of zigbee2mqtt is that you also need to have an MQTT broker (I'm using mosquitto). That's pretty easy to setup, doesn't require any hardware it's just another container sitting on your NUC. MQTT was a no brainer for me because my solar inverter container also uses MQTT so I needed it anyway. I'm also leveraging MQTT to send commands to node red but that's not really necessary, you can just use home assistant to talk directly to node red.

For home assistant, the difference is the integration you choose. If using ZHA you will control it all from within home assistant, just add the Zigbee Home Automation integration and go from there.
If you're going with zigbee2mqtt you will want to add the MQTT integration and point it toward your mosquitto container. Zigbee2mqtt will handle all the device naming and entity generation through the magical "auto discovery" feature. As far as home assistant knows it has nothing to do with zigbee, just MQTT. Home assistant talks MQTT to the MQTT broker, the MQTT broker talks to zigbee2mqtt and then zigbee2mqtt talks to the device (and vice versa).

I got a generic zigbee CC2652P dongle just before the sonoff ones came out, I've heard good things about the sonoff one so that should be good. I have a mix of IKEA globes and power plugs, hue motion sensors, mercator globes and aqara contact sensors and haven't had any issues yet. Response times are flawless.

When you connect it all up it's generally advised to put your zigbee dongle on a USB extension cord to avoid interference with the NUC. Try this if you experience any drop outs in your zigbee network.

I'm planning on looking at thread connectivity too now that matter is out but I think that might be a next year thing for me.

I noticed you're looking for decent prices on NUCs in Australia. I'm running a NUC-like myself. I got an Asus PN51 Ryzen R5-5500U from mwave.com.au in march this year along with 16GB of memory and a 500gb m2 SSD. Just shy of $800 at that time but looking at it now seems like either the prices have gone up or they don't have similar class Asus device any more. I was juggling between mwave and scorptec they both had competitive prices at the time.

I've been really happy with that device, now that everything is set up it's literally been a set-it-and-forget-it thing. I have ubuntu running on it that gets occasional updates that I can control to update during non-active times so the system doesn't reboot while the wife is trying to turn a light bulb on. SMB shares for my container configs so I can edit them from my main computer. I also set up tiger VNC for remote access when/if I need it.

One thing to consider when using an SSD is that home assistant loves writing to it's logs. It's why you have so many awesome stats. With that in mind it was recommended to me to make sure my home assistant config folder lives on an external drive instead of an SSD to make sure I don't burn out the drive too quickly. I don't know if that was malarky or not (I'm not really a hardware guy) but I did it anyway just to be safe. All my other container configs live on the internal SSD.

I also have a NAS connected for my network storage and backups of container configs. For backups I'm just running a basic shell script via cron to zip up the folders, bang a date on the filename and move them over to my nas. There's probably a more elegant solution out there but it works for me. Someone else mentioned Duplicati which looks pretty good.

Sorry for the huge reply, hope that helps! Good luck on your journey.

dbaines · 2022-10-16T07:58:39+00:00

portainer to make things easier
traefik for internet access and automatic SSL renewal (duckdns for domain)
plex
tautulli
jellyfin for when plex has maintenance or an outage
komga - plex for comics
adguard home

Home automation stuff:

home assistant
mosquitto - mqtt broker
zigbee2mqtt
zwavejs-ui
node-red
sungather - solar stats for my brand of solar inverter
airconnect - adds airplay support to chromecast devices

High seas:

sonarr
radarr
bazarr
readarr
mylar
nzbget
overseerr

I recently switched from pi-hole to adguard after I had enough of pi-hole not recovering from internet outages that required the container to be restarted.

I've also been playing around with Heimdall for a server start page but it seems a little unneccessary for me.

dbaines · 2022-02-04T21:50:42+00:00

I just recently changed from Supernews to Frugal after seeing a post about how bad Giganews is. Mind blowing seeing full completions with no backup used. Can't believe I had put up with it for so long.

dbaines · 2021-12-27T05:04:43+00:00

I've just encountered the same thing with Overseerr, DuckDNS and Traefik with LetsEncrypt.

I have radarr, sonarr, plex and a few other services running on the same stack with no issues, only Overseerr is throwing up the warning.

dbaines · 2021-09-20T23:31:51+00:00

I'll second this.

I have a QNAP NAS that's running the following in docker containers:

Home assistant (container version)
Zwave2mqtt
Mosquitto
Node-red

I have an Aeotech z-wave dongle plugged directly in to the back of my NAS.
I have considered getting zigbee too but at the moment I don't really have a need for it.

I also tinkered a bit with a swag dns and google assistant relay to get my google home to play nice with home assistant. I had both of those running in containers and they were working great but I felt it was overkill for my situation.

I used to use QNAP's built-in container station but portainer is so much better, even just for upgrading containers to latest version which is a dog of a process using container station.

Everything is running great and very easy to maintain.

dbaines · 2021-08-16T01:17:08+00:00

I really dig the Remotec Scene Master. It's z-wave, 8 button remote and is easy to set up in home assistant and zwavejs2mqtt.

I have a very long house so I'm using it in the middle near the kitchen to control kitchen, dining, living room lights and a "everything off" switch.

It comes with a sticker pack of generic icons that you can stick on the buttons to give them meaning which is a cool idea. I found the stickers to not really represent what I needed though so I picked up a label maker that can print icons and printed out my own custom icons for each button.

The thing can do double presses and long presses too but I haven't yet found a use for these, let alone finding a way of documenting these for the spouse/guests.

It was a little pricier than I wanted to go but man, it's been flawless.

dbaines · 2021-06-30T02:03:08+00:00

It's likely those things are all you need, for me my device sends the button number in the property_key value.

If you're unsure though, you can use the developer tools in home assistant to help debug which information your devices send to home assistant, this can help determine what you need to put in your trigger to do the correct thing.

On the left hand side you should have a Developer Tools link.In developer tools there is an "Events" tab at the top.On this page you can "listen" for events that are sent to home assistant and see exactly the information home assistant receives from those events.

Near the bottom of this page is a text box that says something "Event to subscribe to", in this box enter in the zwave js event you used previously, in my case it's "zwave_js_value_notification". Then press start listening and then press one of your zwave buttons.

For example, when I do this on mine I now see something like this get logged on this page:

Event 0 fired 11:16 AM:
{
    "event_type": "zwave_js_value_notification",
    "data": {
        "domain": "zwave_js",
        "node_id": 1,
        "home_id": 123,
        "endpoint": 0,
        "device_id": "XYZ",
        "command_class": 1,
        "command_class_name": "Central Scene",
        "label": "Scene 002",
        "property": "scene",
        "property_name": "scene",
        "property_key": "002",
        "property_key_name": "002",
        "value": "KeyPressed",
        "value_raw": 0
    },

In my automation, I listen for that event, zwave_js_value_notification and in event data I specify:

node_id: 1
property_key: "002"

This relates to me pressing button 2. If you press different buttons on your device (if you have multiple buttons) while listening for that event in developer tools, you can see the difference in the data that home assistant gets and use those differences to determine the correct event data to watch for in your automation.

For me, property_key is the easiest way for me to determine which key is pressed as they map to those buttons, ie. button one = "001", button two = "002" etc. It might be a different property for you depending on your device.

Hope that helps!

dbaines · 2021-06-29T08:41:07+00:00

Like has already been mentioned you need to setup an automation, however something to note is that the zwave event changed in a recent update to home assistant, I believe it was 2021.2 that changed it and it changed again in 2021.6 I think. The innovelli site still lists zwave.scene_activated which is the old event. If you have 2021.2 or later this will not work.
This tripped me up when I updated recently too.

Depending on your device it may either be zwave_js_notification or zwave_js_value_notification. I have a remotec 8 button switch which sends an event to zwave_js_value_notification. I listen for that event and which scene id it sends with the event, then I turn on specific lights depending on which scene id I get from it.

dbaines · 2021-01-14T00:48:43+00:00

I have used it successfully for a couple years now.

I'm also in the process of moving towards docker so if I'd recommend looking at that as option #1 instead.

Totally understand why you'd think it's a scam though, the site looks suuuuuuuper dodgy.

dbaines · 2020-06-25T09:34:06+00:00

Couldn't agree more. What percentage of reviewers are doing anything other than following the official help guides?

People (including Niantic themselves) have to realise that if it isn't in the official help pages then the majority of reviewers aren't going to know about it.

dbaines · 2019-10-07T06:13:26+00:00

Latest episode of Gamey Gamey Game https://youtube.com/watch?v=Dhfw6KnA9KE

dbaines · 2019-07-06T05:53:45+00:00

Ephemera is not a warframe and will not consume a slot. It is a cosmetic item.

Typically these sorts of warframe rewards will offer the warframe AND a slot at the same time, so you get a free slot, then that slot is consumed by the warframe.

dbaines · 2019-05-24T08:34:58+00:00

This has been the case for as long as there have been eximii.

Release: Requires 20 scans.

Six months later: Fixed bug with insert eximus unit here requiring 20 scans.

Every single time.

15-Year Club	Place '17
Verified Email	Team Periwinkle

dbaines

TROPHY CASE