Bah here it is, we’re waiting for the PR with zwavejs ![]()
I will first try to see what’s wrong with openzwave and why the information from my « fibaro notion Sensor » only reports temperature and brightness. (Especially since this sensor seems to be a flagship product in Z-Wave…)
And then I’ll tackle the zwavejs service, which seems to be well-stocked as of today, at least from what I’ve tested with HA, which even had the ability to configure the different parameters of the device like with the fibaro home center box, and that’s a big plus that zwavejs seems to add compared to openzwave.
PS: we can close this post.
With the installation of node.js using both methods, it now works on its own.
@tagcash Great
Keep us updated on your research (you can create a dedicated topic just to talk about Z-Wave?), and above all, if you have any questions, don’t hesitate, it’s a pleasure!
I agree with your approach, in the short term, you might as well try to see what’s wrong with open-zwave in your case, I’m sure it’s something simple.
And to switch to ZwaveJS, as I told you on Twitter, it’s the direction we’re heading!
I had a nodemon bug and had to restart my installation ![]()
And unfortunately, I no longer have access to my Z-Wave USB key.
I did an NPM Install in Service/USB and Service/Zwave but the installation works without errors.
And here’s why:
When gladys calls http://localhost:1443/api/v1/service/usb/port I have an empty array []
Then http://localhost:1443/api/v1/service/zwave/info I have a nice 400 {"status":400,"code":"BAD_REQUEST","message":"SERVICE_NOT_CONFIGURED"}
And to finish: http://localhost:1443/api/v1/service/zwave/variable/ZWAVE_DRIVER_PATH a 404 {"status":404,"code":"NOT_FOUND","message":"VARIABLE_NOT_FOUND"}
Has anyone else had this bug? I haven’t found any topics on this ![]()
I don’t understand why you have to reinstall.
If nodemon doesn’t kill the process, you can kill it via htop for example.
And these errors are normal since the dongle is not found, the service is not configured.
The kill command isn’t working for me, I don’t know why ![]()
Even in sudo htop??
Personally, I display in tree mode and I kill the node process (without root)
Yes, it’s even the first thing I tried, the magic of Windows and every configuration probably ![]()
You don’t want to use your Mac
?
I think that’s what I’m going to do even if it’s old and slow ![]()
I think when there’s a need for hardware resources, it’s a mess with Windows.
Or I’ll use a Linux VM because I want to keep a quick setup since the Mac is really slow ![]()
You will have the same problem accessing the serial dongle. I’ve never tried ![]()
With VMs, it’s maybe easier to have the bridge to serial ports. I’ll test it, and otherwise… I switch to Mac
But if someone finds a solution to my problem, that’s cool. It might help others who don’t have a Mac on hand.
Too much hassle with the VM, it’s not simpler to access the key and when it finally appears in the list it doesn’t work.
Tomorrow I’m going to do a dual boot Linux on my PC ^^ that way I still keep the power of this PC because developing on my Mac is really a pain, it’s from 2008 the thing ^^ it’s retirement age ^^
Good decision
don’t mess up during the grub installation ![]()
No worries, I dual boot all the time, I just hadn’t thought about it before ![]()
these days you have to try hard to mess it up ![]()
![]()
Well … Dual boot works better … But the z-wave and Gladys … It’s not compatible or not very well compatible.
It crashes the server when I connect the key systematically on Linux (strange thing I still managed to make the z-wave key work 1 time but on Windows …)
Then … I have another bug on the Dashboard with the weather, it can’t save the selected house anymore. I don’t know if there was an update of Gladys in the meantime that causes all these problems or if it’s because I’m on dual boot Linux ![]()
![]()
I rarely had so much trouble starting a development ![]()
OpenZwave is a nightmare to run, at least now you understand why no one wants to work on it ![]()
After making the server crash, it’s supposed to work anyway.
For the weather, it’s also supposed to work.
Do you have any specific errors to show us?