Gladys beginner — tests before possibly migrating from Domoticz?

Hello,
Gladys is very interesting, that’s why I want to test it before migrating… a basic IT approach.

Today I use Domoticz with:

  • link to Netatmo (the station + rain gauge)
  • link to two indoor Netatmo cameras
  • temperature collection provided via a curl -s -i etc etc json.html?type=command etc etc
  • use of a plugin: DomoticzLinky

What exists and can therefore be reused/migrated or not?

I installed the Gladys Raspberry Pi image found via rpi-imager.

  • Installation / boot: OK
  • note:
    • on first login the user is pi; one suggestion is to use the userconf.txt file to create « your » user and forget the default « pi » user
    • why not a richer motd with, for example: « welcome to Gladys » [ok ok the hostname is gladys]
    • display a first welcome message, inviting to connect to http://192.168.x.x to start the configuration

I created the house with the rooms, a dashboard with the weather and two Netatmo cameras
For each camera: the test is OK
however for one of the two, saving fails:
« An error occurred while saving the camera. »

Any idea how to fix this?
Thank you very much
Phil

Good evening,

Unfortunately I can’t help you… I don’t have the necessary skills!

Maybe you should create a thread in the configuration section to make your message more visible (with a dedicated subject) :+1:

Hello @Phil and welcome to the forum!

Did you test your stream with VLC?

As I do in this tutorial:

To get more information, you can check the Gladys logs by running:

docker logs gladys

For the Netatmo cameras @Terdious found a workaround

Hello everyone,
Many thanks for your feedback.

@guim31 :
That’s exactly what I thought I had done « a thread in the configuration section »
Thanks for the message I felt less alone all of a sudden :+1:

@pierre-gilles :
Thanks for the welcome! :smiley:
yes the stream works with VLC .. and on domoticz :wink:
I tried the calendar with Framagenda .. ‹ other › option :smiling_face_with_tear:
The calendar that appears is consistent with what I have on the web and on the phone
→ but there are « calendar » errors in the log.
however, nothing found with camera or webcam [ egrep -i « camera|webcam » ]

    see file to download with the link :  [docker logs gladys]

(drop.infini.fr)

@VonOx :
Thanks, indeed that’s what I had found several years ago to put it successfully in domoticz
I retried the links :grinning: without success on the « backup » side (see the screenshot) because the test works fine.

Thanks in advance for your help in considering a migration.

Best regards
Phil

Ok, autre piste, est-ce que tu pourrais ouvrir les logs de ton navigateur quand tu créé la caméra.

Dans ton navigateur, tu fais « Clic droit » sur la page =\u003e « Inspecter l’élément » =\u003e « Console »/« Network », puis tu créé la caméra.

Les deux choses qui nous intéressent c’est les requêtes et potentiels erreurs qu’il pourrait y avoir, comme ça:


(Désolé, c’est un peu tech, mais bon là on a pas le choix pour t’aider :D)

Je ne pense pas que ça ait de rapport ici, mais je tag le développeur de cette intégration pour qu’on regarde quand même si c’est un problème :slight_smile:

@bertrandda je te tag je ne sais pas si il y a quelque chose à faire ou si l’erreur est « normale », dans les logs de @Phil on voit des erreurs de synchro CalDAV :

2022-05-18T15:42:05+0200 \u003cerror\u003e calendar.syncUserCalendars.js:72 (Promise.map.concurrency) Error: Bad status: 415
    at exports.XMLHttpRequest.request.onreadystatechange (/src/server/services/caldav/node_modules/dav-request/dav.js:3424:27)
    at exports.XMLHttpRequest.dispatchEvent (/src/server/services/caldav/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:25)
    at setState (/src/server/services/caldav/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:14)
    at IncomingMessage.\u003canonymous\u003e (/src/server/services/caldav/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:447:13)
    at IncomingMessage.emit (events.js:412:35)
    at endReadableNT (internal/streams/readable.js:1334:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
2022-05-18T15:42:05+0200 \u003cerror\u003e index.js:52 (Timeout.syncAllUsers [as _onTimeout]) NotFoundError: CALDAV_FAILED_REQUEST_CHANGES
    at Promise.map.concurrency (/src/server/services/caldav/lib/calendar/calendar.syncUserCalendars.js:73:15)
    at runMicrotasks (\u003canonymous\u003e)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

Hello,

The error occurs when clicking the « save » button.
No error when clicking « Test » which works perfectly and correctly displays the camera image.
Information collected via Firefox and Chromium



Regards
Phil

@Phil,
Don’t you already have another device named « salon »?
Have you tried changing the name?

It seems to me that the conflict error corresponds to a uniqueness constraint in the database. Two devices cannot have the same name. Well, in theory. You can bypass this by registering a device for the first time with a unique name, then renaming it. That will work.

If that’s the case, maybe a clearer message should be displayed for the different errors. I’ll open an issue and a PR this weekend to that effect (if you also confirm @pierre-gilles)

Edit : for info I can reproduce it with identical names, also tested with identical names in 2 different integrations!! ^^

Hello @Terd

I just re-ran a test ..
Removal of the cameras then
adding salon into salon : Ok
adding salon2 into salon : Ok
So it’s all good
There must have been a problem during the additions; however I agree with @Terdious the

1 Like

100% agree, the message is not at all explicit!

I created a GitHub issue so we can fix that:

Good to hear it works in the end :slight_smile:

1 Like

Thank you for your help and patience :clap:

Well, I saw about Netatmo — @Terdious did an amazing job :clap: :clap: :clap: Can’t wait to test
Best regards
Phil

And @damalgos :wink:

1 Like

I confirm what @VonOx said, most of the work was done by @damalgos!!

@Phil, you can test via the image docker pull terdious/gladys:netatmo-prod-190522. But according to a test by @_Will_71 it doesn’t work from a new DB. So I think I still need to fix something when starting from a blank DB.

1 Like
2 Likes

Hello @Phil,
I’ve looked at your CalDAV error, it must be the calendar associated with the Deck app that’s not being handled correctly. I’ll try to fix your problem. Do you use the Deck app in Framagenda?

It is indeed the Deck app that created a partial calendar. I just proposed a fix

2 Likes

Hi @pierre-gilles,

I’m taking this opportunity to report a bug on the same topic but much more worrying… I wanted to create the PR and so I did a test on the MQTT integration to see the message that appeared… and then it’s a disaster!!!
MQTT doesn’t return any error but simply overwrites the device directly!! :scream: :scream: deleting the other device’s features in the process…
Bug save mqtt same external_id

I also tested with 2 features in the same MQTT device, it’s the same, no error and the first feature gets overwritten!! However, if you create an identical feature in another device then we get the correct message:

I created an issue for that!!

Ah yeah, that one can be very frustrating because there’s no feedback.

We need to fix it quickly.