Nobody is wrong, experience and each personâs job mean that our opinions diverge. For the RC, you think core and API, I think mainly features (in the broad sense).
For zigbee2mqtt, I completely understand, thatâs why I said « we all do our best ».
So I think youâll have understood that for me, an RC is software (Iâm not talking about Gladys in particular) close to the feature release. But my point of view may not be suitable for Open Source, I agree, and itâs also true that youâre a bit alone on the dev at the moment!
Some news about the Zigbee2mqtt module following recent questions.
First, about the history, to give credit where itâs dueâŠ
Actually, itâs @AlexTrovato who started the development of this module and I offered to take over when he was short on time to continue. He still helped me a lot to get started.
In my turn, Iâve been short on availability recently with very important project milestones at work, until last week. Iâm currently on vacation with family and should get back to Gladys next week.
As I already mentioned, the latest developments of the module have notably focused on the use of an MQTT container and I had interrupted this part when seeing the developments of @AlexTrovato and @VonOx on the subject.
Their PR being integrated, I will reuse their work for the MQTT part to ensure some homogeneity. These developments do not seem too complicated to integrate.
However, as I also mentioned, the testing part will be missing for @pierre-gilles to integrate the PR in Gladys for the RC.
Iâm not an expert in this field and if there are any volunteers (@VonOx?), it would be a great help.
Thatâs it, see you soon to give you news about the next developments of the module.
Iâm currently taking a look at the demo and thereâs something that bothers me on the integration page.
When I see the list of all integrations, I realize that itâs not very clear for an average person.
What I mean is that a person who wants to make their shutter compatible, well, they are lost.
Wouldnât it be more interesting to have categories, that is, light bulb and on click the modules that can control them, window and same on click etcâŠ
Thanks, itâs cool to hear news .
Iâm just an end user, but this module is the basis of my modest installation .
I dare to make a small request: can you rebuild a Docker image containing Z2MQTT from the latest Gladys image (beta 11) while waiting for the final integration?
This would allow me (us?) to benefit from the improvements that have been integrated since v4.0.0 beta 4.
French language, openweather, caldavâŠ
I have no idea how much time this represents, so if itâs too much, no problem :).
Thanks for your message @Reno and thanks for the work done so far!
Wow great! Looking forward to seeing you back in the community.
For the testing part, itâs really not complicated, Iâm available to call if you want help setting them up. Itâs true that it can be scary when youâve never done it, but youâll see that once you know how to write them, youâll save time in development and especially in code quality.
Testing is a real product development philosophy, I try as much as possible to be in « TDD » (Test Driven Development) mode, that is, you write your tests before writing your code and then see your tests validate progressively. It saves a lot of dev time with tests!
My vision in Gladys 4 was to do the opposite reasoning:
If a user buys a Philips Hue bulb, and wants to control it in Gladys, they expect to search for « Philips Hue » then « Bulb » then « Add ». Especially if they buy a Philips Hue kit, they want to add all their Philips Hue devices at once, so they go to the « Philips Hue » integration, and click « Add » on each device.
I find that the opposite reasoning, starting from the object to go back to the brand (« Bulb » => « Philips Hue ») makes less sense.
After, thatâs on the product side.
On the documentation side, I agree with you, to find the devices compatible with Gladys, itâs the opposite option that makes sense:
You wonder which bulb you can buy to use with Gladys? You go to the site, you filter by « bulb » and then you see all the available brands.
Thatâs what we did on the v3 site, and what weâll do on the v4 site. For now, there are few products listed on the site (on the Integrations page) so I havenât coded the filters yet (by tech/by product type/etcâŠ), but thatâs the goal.
Well, we seem to have trouble understanding each otherâŠ
I asked for corrections in May, and the PR hasnât changed since and my comments havenât been answered, so on GitHub, on my side, itâs marked as « awaiting correction ». I thought @link39 didnât have time to make the fixes but given his message, we seem to have trouble understanding each other ^^ @link39 I can help if needed but I need to know the status of the PR
You did well to ask, itâs really a shame these communication problemsâŠ
Small message for those who develop on Gladys, there are a lot of issues/PRs on GitHub. The only way I know that a PR is « ready » to be reviewed is that you say it ^^ I canât guess where the work is, and there are too many PRs/issues in progress for me to remember each case individually.
For example @atrovato does this very well, when he finishes a PR, he « requests a review » on GitHub, which gives me a notification:
I know the PR is ready for review, I put it in my todos and as soon as it comes to the top of my stack, I do my review, which is concluded by 2 possibilities:
The PR is good, I accept it and it is merged to master
I have feedback, the PR then goes from status « Ready for review » => « Changes requested ».
In case 2., as long as the PR is in « Changes requested », it is completely out of my radar, I only see it again on my GitHub if the changes are made and the remarks I had written have been « marked as fixed » by the author of the PR.
I understand your reasoning about documenting integrations actually, I was getting there because I didnât know what the tasmota module controlled anyway..
Two small questions,
Regarding the notification part of the scenes, can we not retrieve the events from a calendar?
That is, for a wake-up scene, it would have been great to be able to check if appointments are scheduled and if so, notify the user.
Indeed, that would be nice! Itâs an interesting feature, although itâs not yet estimated or scheduled for the short term. For now, all my resources are focused on the stability of the core for the RC release
If my memory serves me well, if Gladys is on Docker:
No broker is detected by its name, we suggest downloading it
A broker is present, we suggest using it
We do not use an embedded broker by Gladys (manual configuration)
Now if the page is not clear enough, it is possible to modify the helps, but we need to know what to modify, because @Serge your explanations are not clear to us either.
A new week starts for me, I reviewed this morning all the pending PRs on GitHub and merged 3 great PRs from @AlexTrovato + a PR on the Gladys 4 documentation
I made good progress on timezone management in Gladys, but itâs a bigger project than expected and I will take more time than estimated.
I updated the milestone with the new estimate, for information we are at:
2 low tasks * 2 = 4 hours = 0.5 days
5 medium tasks * 1 day = 5 days
1 high task * 4 days = 4 days
= 9.5 man-days of development remaining
@VonOx, while going up the channel, I realized you had a display issue with hue devices 12 days ago, is this still the case?
If yes, can you create a GitHub issue with an exact description of the problem as well as the necessary information to resolve the bug (the JSON of the devices)?
GitHub is my only source of truth, if a bug is not on GitHub, it slips through my net and I forget it the second I leave the forum ^^
I think Iâm going to invest in a larger ”SD card.
I donât know if itâs possible to boot Gladys on a ”SD, then work on a USB key. This to avoid overworking the ”SD.
I had found a tutorial to do this when I was using Domoticz
How can I stop Gladys?
The interface does not offer this option.
via SSH pm2 stop gladys (with or without sudo) returns [PM2][ERROR] Process or Namespace gladys not found
for info since version 4 of gladys, pm2 is no longer used.
Version 4 has been containerized via docker.
You should be able to find the command by searching on Google: stop a docker container.
.
