only looked like that because your reply was to Finity’s post…
Well hopefully we won’t hear any more from you then.
2 Likes
As you are leaving would you like me to disable your account and anonymise it?
6 Likes
The last driver (openzwave) was not written by HA, it was also written in c++, not python. That project has stalled. It stalled because no one has been able to maintain it, largely because it’s written in c++.
Zwave js is a new driver, with a few devs. Js is also a code base that many people use, so finding people to support it will be easier.
2 Likes
To whoever flagged @SnapETom’s post as somehow unacceptable, come on, he is entitled to his opinion.
3 Likes
Well, i understand this is somewhat frustrating and needs alot of Love, but thats why this is Free and community based, Open Source! and thats why comercial platforms cost money. because they have a team behind it always working on solving all the problems! I would totally understand your point if you had payed for this software, but its not the case. This is not for everyone… its for those that want to go after their dreams and have it just like they want it to be and not like comercial brands want YOU to be 
i can see from your profile that you have been on the forum since 2016 but only spent minimum hours here. if you took the time to understand whats happening here, and you had the mindset to understand what this community is building VERSUS what the comercial brands are doing to us… (making us slaves of their profits) you would give more credit.
But i can you something, im with you on other aspects, like construction, cars, and Babies! let them build it! ill pay for comercial!
Integration and you can find the token of the device with that integration
The article assumes the fob has been added and recognised which is the issue I’ve had from the started. In my case I coul never get the fob added and the node interview completed. But the zwave-js software has had changes, so I’ve ben trying to add the node again. Waking it up and asking for a node reinterview didn’t work, but removing the node from the control panel, adding it again eventually did. You seem to need to keep the device awake at the right point after adding it.
Thanks for everyones comments and suggestions
since this is about the z-wavejs, please beware and dont update to core add-on 0.1.11:
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: ZWaveError: The config has not been loaded yet!
Yep getting the same
19:22:06.425 DRIVER version 6.5.0
19:22:06.426 DRIVER
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
ZWaveError: The config has not been loaded yet!
at ConfigManager.lookupMeter (/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/src/ConfigManager.ts:326:10)
at ConfigManager.lookupMeterScale (/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/src/ConfigManager.ts:342:22)
at new MeterCCReport (/usr/lib/node_modules/zwave-js/src/lib/commandclass/MeterCC.ts:559:43)
at new CommandClass (/usr/lib/node_modules/zwave-js/src/lib/commandclass/CommandClass.ts:108:13)
at new MeterCC (/usr/lib/node_modules/zwave-js/src/lib/commandclass/MeterCC.ts:340:1)
at Function.from (/usr/lib/node_modules/zwave-js/src/lib/commandclass/CommandClass.ts:331:15)
at new ApplicationCommandRequest (/usr/lib/node_modules/zwave-js/src/lib/controller/ApplicationCommandRequest.ts:88:32)
at Function.from (/usr/lib/node_modules/zwave-js/src/lib/message/Message.ts:222:15)
at Driver.serialport_onData (/usr/lib/node_modules/zwave-js/src/lib/driver/Driver.ts:1395:18)
at SerialAPIParser.emit (events.js:315:20)
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
Why are you still complaining about this? Move on, it’s done.
Create a decent dashboard instead of using the auto-generated one. You will surely enjoy it far more in the long run. You can still have badges, they haven’t disappeared.
I just created an auto-generated dashboard for the sake of it, it took 5 seconds to do… and what a mess. I honestly can’t think why anyone would want to use it, unless they had maybe less than 10 devices, max.
Only to see new devices, which I subsequently add to a “proper” dashboard. And as a “catch-all” for my randomly added stuff.
The thing is, Jason was complaining about not having badges which were removed as an auto-generated item. He can still create an auto-generated dashboard, ‘take control’, then add the badges manually. It’s not hard at all.
Quite right!
No. You missed the point entirely.
It was the cover spread for a multi-page article and it looked hideous.
Also the changes will eventually allow ‘blueprints’ for the frontend.
1 Like
That sounds pretty cool
Flag away… but there is no integrity in ‘I disagree with vocalizing a different opinion, Shut Him Up!’ …why? because it’s critical and might hurt somebody’s feelings? oh noes!
Because it was a poorly made decision in a string of poorly made decisions. I’m not ready to create a dashboard. a) I’m not staying where I live. I’m not commiting to a full-build until that’s less the case. b) I’m still running Pi3/mSD because I’m not ready to commit to my pi4/SSD build. when I do that I intend to build proper. no imports, factory resets for all my devices… currently thinking about if I want to go so far as to firmware update my nortek stick… when I add new devices to my install I like to see what gets auto-added.
As far as number of devices? Yeah… sounds about right… few lights, few switches, handful of integrations… mostly media devices… I mean. I work in automation\integration and have a couple boxes of switches and outlets that I’ve collected with the intent of eventually using… but my current needs don’t justify the effort of replacing switches and outlets just to swap again when I move.
I mean… thank you for… agreeing with an apparent unpopular opinion on if there is genuine utility to it.
I’d actually like to know more? …I was under the impression that ‘taking control of Lovelace’ was irreversible and meant completely losing the auto-add feature.
It’s not about the perceived challenge. It’s about the fact that my usage is primarily geared towards being a testing platform. If I see a decent deal on a device that I can see myself using in the future I’ll buy one or three, I’ll try one out in my install, put the rest in my closet with the few dozen other devices I did the same with before. Now… aside from that… I have sensors defined in my configuration.yaml and those don’t even show up.
Hey! …who’s side you on?!
No… no, I don’t think I did and please don’t think it’s purely reactionary if I posit that you (and others) have missed my point(s). I agree. It looks hideous. No debate there what-so-ever. But it’s not a HomeAssistant problem, it’s a crap journalism problem. ‘multi-page’ moreso, an article that they had to FILL with SOMETHING and that screenshot completely did it’s job. It fills the page and it’s an active visual element that gives ‘splash’ to the page. The theme color palette adds to the effect all the same. Truth be told, if the write-up were legit they would have shown a more realistic example and having a handful of sensors at the top of the page makes for a more interesting look, same as a UI with a couple Grafana graphs or a well laid-out and feature-complete media control page. That same UI in the screenshot in the same palette without sensors would look just as ridiculous.
Also… ‘Eventually’ as in ‘Eventually™’ in the Blizzard ‘Soon™’ sense? Just saying… the rate things get roughed-in then slllloooooooowwwwly progressed on. Granted… I’m not to the point to be familiar with the nuances of the progression of the code, but the other night I took a look at the commit history and just… man… how many commits/day do y’all average?
Revolutionary thought… change things when frontend blueprints necessitate the need?
Anybody with that many devices is already due a customUI and the judgement of anybody that test drives a new controller with all their devices connected is questionable at best.
‘taking control’ is a per dashboard action so you can take control of a dashboard and within seconds create another auto generated dashboard which isn’t ‘taken control’ of. This is my point.
As for not wanting to change things due to moving house, I think you are going about it the wrong way. I started using HA while in a rental. After 1.5 years I bought a house and all I had to do was label my devices so they went into the correct locations in the new house. All my code got to remain. I’ve since expanded, but the original devices and code have stayed. Why make extra work for yourself while also holding back on using HA features?
@Sompie have you solved your issue? I’m planning an upgrade of HA to latest and greatests - but in my test lab I found that the current RFXcom doorbell push doesn’t work at all and since everything now are controlled (or restricted) through the HA GUI I’m unable to solved it (at least so far)
It is Solved