Gladys 4 Beta is available! 🚀

[VonOx]

Versioning will arrive with the RC if I’m not mistaken.

To check if you’re up to date, it’s as simple as this: « Gladys is up to date »

[pierre-gilles]

@VonOx

To check if you are up to date, nothing simpler. “Gladys is up to date”

Not yet, it will only work when Gladys is versioned (when we are out of beta)! For now, it only displays « Gladys is up to date ».

[pierre-gilles]

Hello everyone!

I just published my work on MQTT (still building, it will be available in about 1 hour for you)

This brings new features, but it also changes the API. We are still in beta, so I allow myself to « break the API » in the middle, and ask you to make the necessary changes on your side, so that we can move forward and move more and more towards the RC

The API now looks like this:

Among the new features, the ability to see when the last value was received on each device:

A small UX detail but which is so practical, the ability to copy and paste with one click the MQTT topic on which the device listens/publishes:

I hope you like it, in any case I spent time doing it well on my side!

I am always open to any feedback

[Will9]

Hello everyone

I’m following up on my Z-Wave issue. I see that updates have been released, but my modules are still not being managed. Any news? The Z-Wave library is still not up to date?

For information, adding peripherals is fine, but no values are received.

[pierre-gilles]

@Will9

I’m following up on my zwave issue. I see that updates have been released, but my modules are still not managed.

It should work normally!

Given what you’ve shown us, there doesn’t seem to be any issues with the library (your sensors appear to be well configured).

Are you sure your Z-Wave USB stick is properly connected? That it’s working properly?

[Will9]

Hello

Are you sure your Z-Wave USB stick is properly connected? That it works well?

Well, it is well recognized in gladys and yes it is well on a USB port of the raspberry
It has never worked alone only the pairing works so the key is OK but once done no data except the battery of the opening sensor at the first sync
What do you need as debug info? No problem for ssh on the raspberry in case

[Albenss]

Hi, I have the same problem as @Will9. My Z-Wave key is well recognized without any issues, and I am trying to display the data from my Fibaro multi-sensor, but only the temperature is reported from time to time and the battery only during pairing…

For information, the key I am using is as follows:

[link39]

Same problem as you with the neo coolcam. The zwave class reported must not match the one declared in the standard. I’ll check tonight if I see anything.

[Will9]

We have exactly the same Z-Wave key

The view on the interface

Otherwise, the logs (if it can help)

docker logs gladys

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

Initialising OpenZWave 1.6.974 binary addon for Node.JS.
    OpenZWave Security API is ENABLED
    ZWave device db    : /etc/openzwave
    User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
    Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2020-04-13T14:44:32+0400 <info> index.js:19 (Object.start) Starting telegram service
2020-04-13T14:44:32+0400 <info> index.js:13 (Object.start) Starting usb service
2020-04-13T14:44:32+0400 <info> index.js:16 (Object.start) Starting zwave service
2020-04-13T14:44:32+0400 <info> index.js:20 (Object.start) Starting Dark Sky service
2020-04-13T14:44:32+0400 <info> service.start.js:16 (Service.start) Service darksky is not configured, so it was not started.
2020-04-13T14:44:36+0400 <info> service.start.js:16 (Service.start) Service telegram is not configured, so it was not started.
2020-04-13T14:44:36+0400 <info> service.start.js:16 (Service.start) Service mqtt is not configured, so it was not started.
2020-04-13T14:44:36+0400 <info> index.js:63 (Server.<anonymous>) Server listening on port 1080
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gladys-server@ start:prod: `cross-env NODE_ENV=production node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the gladys-server@ start:prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-04-13T11_14_37_527Z-debug.log

docker exec -it gladys cat /root/.npm/_logs/2020-04-13T11_14_37_527Z-debug.log

docker exec -it gladys cat /root/.npm/_logs/2020-04-13T11_14_37_527Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ ‹ /usr/local/bin/node ›, ‹ /usr/local/bin/npm ›, ‹ run ›, ‹ start:prod › ]
2 info using npm@6.13.4
3 info using node@v12.16.1
4 verbose run-script [ ‹ prestart:prod ›, ‹ start:prod ›, ‹ poststart:prod › ]
5 info lifecycle gladys-server@~prestart:prod: gladys-server@
6 info lifecycle gladys-server@~start:prod: gladys-server@
7 verbose lifecycle gladys-server@~start:prod: unsafe-perm in lifecycle true
8 verbose lifecycle gladys-server@~start:prod: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/src/server/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle gladys-server@~start:prod: CWD: /src/server
10 silly lifecycle gladys-server@~start:prod: Args: [ ‹ -c ›, ‹ cross-env NODE_ENV=production node index.js › ]
11 silly lifecycle gladys-server@~start:prod: Returned: code: 1 signal: null
12 info lifecycle gladys-server@~start:prod: Failed to exec start:prod script
13 verbose stack Error: gladys-server@ start:prod: cross-env NODE_ENV=production node index.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:311:20)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:311:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid gladys-server@
15 verbose cwd /src/server
16 verbose Linux 4.19.97-v7+
17 verbose argv « /usr/local/bin/node » « /usr/local/bin/npm » « run » « start:prod »
18 verbose node v12.16.1
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error gladys-server@ start:prod: cross-env NODE_ENV=production node index.js
22 error Exit status 1
23 error Failed at the gladys-server@ start:prod script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

[link39]

I’ve looked into the neo coolcam and here’s the result, I think it should meet your needs:

@pierre-gilles, I noticed that two comClass are used to report Watts… Moreover, some interesting class indexes were not mapped. I added them and now we have more information. Namely: Watt / Volt / A / KWh.

However, it is clear that there are two features reporting the same information: « Power Consumption » so Watts. It’s not great, because I have the impression that some information is not reported: « No value recorded ». I will let it run tonight to see. Otherwise, it would be necessary to filter by productCode in order to eliminate the comClass not used for certain products.

I take this opportunity to report a few bugs:

• The On/Off button does not appear on my Fibaro dimmer 212 as shown in the first capture (Bedroom). → Probably because it’s a dimmer switch and not a classic On/Off.
• The On/Off of the fibaro FGS213 (Outside) no longer works. I say no longer works because I am convinced it worked in an old version. I do have an http return: 200 but nothing happens.
• Sometimes the On/Off toggle of the Wall Plug or the neo coolcam no longer wants to work, I have to change tabs for it to work again.
• The fibaro Roller Shutter is not usable as is. I will check if it comes from openZwave or Gladys.

[guim31]

On my end, for some reason I don’t know, my Neo Coolcam plug is detected with only the switch function…

[link39]

This is the current behavior. I have modified the zwave service to get the other information. It is therefore only on my dev instance for the moment.

[guim31]

Okay, I understand I can’t wait for everything to go back up, I want to know the power consumption of my computer equipment!! Lol

[link39]

@pierre-gilles, I have the impression that part of the work we did together last summer on Z-Wave is missing. In particular, it seems that the bindValue() function is not used anywhere. We created it for my Zipato keypad if you remember. The comClass also seem less refined than what we had done. I will look into this point.

I suggest creating a dedicated topic for Z-Wave to centralize bugs and data not reported in the interface.

[pierre-gilles]

@link39

@pierre-gilles, I noticed that two comClass are used to report the Watts… Moreover, some interesting class indexes were not mapped. I added them and now we have more information. Namely: Watt / Volt / A / KWh.

Ah great! That’s cool!

Is this an issue on Gladys’ side or open-zwave? Updating openzwave doesn’t change anything?

@link39

• The On/Off button does not appear on my Fibaro dimmer 212 as shown in the first screenshot (Bedroom). → Probably because it’s a dimmer switch and not a classic On/Off.
• The On/Off of the fibaro FGS213 (Exterior) no longer works. I say it no longer works because I am convinced it worked in an old version. I do have an http return: 200 but nothing happens.
• The fibaro Roller Shutter is not usable as is. I will check if it’s from openZwave or Gladys.

Keep me updated on your investigation. If it’s a Gladys bug, don’t hesitate to create a GitHub issue + a PR if you have the solution

@link39

Sometimes the On/Off toggle of the Wall Plug or the neo coolcam no longer wants to work, I have to change tabs for it to work again.

Is this only on the toggles of these integrations, or any integration in general? In short: is this a Z-Wave bug or is it a general Gladys UI bug?

@link39

@pierre-gilles, I have the impression that part of the work we did together last summer on zwave is missing. It seems to me in particular that the bindValue() function is not used anywhere.

Hmm maybe we didn’t have time to finish everything? Indeed, « bindValue » is not used, that’s weird!

@link39

I suggest creating a dedicated topic for zwave to centralize bugs and data not reported in the interface.

Good idea!

[link39]

I created a topic for Z-Wave: Zwave - Aide pour la v4 - #3 par link39

[pierre-gilles]

Hello everyone!

Some news about recent developments since my last recap

• New Philips Hue bulbs are managed, the LLC001 and LTW013. Thanks @VonOx! The commit.
• CO2 sensors are now managed in Gladys
• A new MQTT API has been introduced, with the possibility to control devices via MQTT! The recap post.
• Humidity sensors are better managed in Gladys 4.
• The Caldav service is now available in Gladys 4, thanks @bertrandda! The integration works with Apple Caldav on my side, but I had feedback from @link39 that it was not working yet with Synology’s Caldav… Feel free to test the integration with your Caldav servers to give feedback to @bertrandda
• I fixed a bug today regarding the upload of backups to Gladys Plus when files were large (for those who have huge huge DBs!). It’s in the process of being built and will be available in the next few hours for you.
• I am currently working on the UI to configure a Gladys instance from a Gladys Plus backup!
• I had @link39 on the phone today, we talked a lot about Z-Wave, including multi-instance management and other bugs reported in the topic in question. New features are to be expected

Thanks to all the Gladys contributors who proposed these improvements!

[Hamtaro]

@pierre-gilles

The Caldav service is now available in Gladys 4, thanks @bertrandda! The integration works with Apple Caldav on my end, but I had feedback from @link39 that it still doesn’t work with Synology’s Caldav… Feel free to test the integration with your Caldav servers to provide feedback to @bertrandda

Do you need to disable two-factor authentication on iCloud?

[pierre-gilles]

@Hamtaro

Should two-factor authentication on iCloud be disabled?

No! At least on my end, I didn’t have to do anything, it uses iCloud app keys

[VonOx]

@bertrandda do you plan to manage the ical?