I am currently using Jeedom, and I recently heard about Gladys. I am generally satisfied with Jeedom, but since I am curious, I would like to try this alternative system… and more if I like it!
My question is simple, but I doubt the answer will be as straightforward. Is it possible to test Gladys on my current setup without losing everything I have done and configured in Jeedom? I have Zwave roller shutters and light switches, as well as Philips Hue lights and sensors (Zigbee).
I know I can back up my Jeedom configuration and restore it. But will the different Zigbee and Zwave nodes not be modified (paths, IDs, etc.)?
Sorry if the question is silly, but I have never changed systems before.
I think so, but I’m not an expert on Z-Wave/Zigbee, I wouldn’t be able to answer you about the paths/IDs…
I’ll let the experts answer!
If you ever test, don’t hesitate to give us all your feedback, and to tell us well what would be missing for you to fully switch to Gladys. We are responsive and we continuously improve the product
Why don’t you try Gladys on a different SD card from Jeedom?
However, if you want to keep Jeedom at the same time, you will probably need 2 Pi.
At least no data loss issues.
I have no doubt about the responsiveness of the developers here. From the videos I’ve seen, a lot of work has been done, and I understand that the goal is to become the leader (a fratricidal war with Jeedom in sight)
I’ll let you know what I think of Gladys if I give it a try. In fact, it’s right up my alley.
By the way, @pierre-gilles, yes, I know I can use another SD card. As I said in my message, it’s not the loss of my Jeedom configuration itself that I’m afraid of losing (it backs up automatically), but the configuration of the nodes. But it’s mostly due to my ignorance of the exact workings of these networks.
What I want to avoid is, for example, launching a scan of my modules on Gladys, changing paths within the Mesh (zigbee and zwave), or the identifiers of the modules, and thus, when I put Jeedom back, nothing works anymore.
But maybe in reality, nothing will change in my network regardless of the home automation system I use, and I can switch from one to the other without any problem. In fact, I have the feeling that this is the case…
But my feeling is not enough for me
If you confirm that to me, then I’ll start my tests!
@VonOx@cicoub13 any idea if using the same Zigbee / Zwave key on 2 different instances can change something on the network? Can he test Gladys without any impact on his configuration?
The mesh is managed by the network itself and not by the home automation application.
However, changing the solution will require everything to be re-paired. Backup or not, what has been done on the Jeedom side will need to be redone (inclusion, etc.) because the dongle IDs will be different.
I don’t know Jeedom, so I’m not 100% sure.
So don’t dream, there will be work to do
I confirm for Zigbee. The only way not to re-pair everything would be to use the same dongle and keep the same network parameters
File configuration.yaml
network key (network_key)
Zigbee channel (channel)
panID (pan_id)
I have never tried such a manipulation so I can’t guarantee it will work
@VonOx@cicoub13
Ok, if I understand correctly, it’s the Zigbee dongle that contains the network configuration (node identification and paths).
And on Gladys, I will have to pair the modules that are registered on the Zigbee key.. since I’m starting from scratch, that’s normal a priori.
But when I put the key back on Jeedom after testing, I should find everything as it was without re-pairing, right?
It’s just that configuring scenarios for shutters and detectors is a bit of work. Starting from scratch to do a « curiosity » test on another system is different if you can switch easily, or not
In any case, you will need to go to the command line in the Docker instance created by Gladys to update this file. I understand that it’s not easy, but we haven’t planned for this case in the Zigbee Service in Gladys (which explains the manipulation).
For ZWave, it’s the controller that stores the network (with a temporary file that contains, for example, sleeping devices).
I sometimes do this but it takes time and makes the production system inoperable during this time (you need to count about an hour for +/- 40 devices, times 2 to restart Jeedom)
