Domoticz

https://domoticz.com/forum/viewtopic.ph ... d for all!

heggink wrote: Friday 22 October 2021 23:27 Correct! Interested to see your feedback. Keep us posted.

I think it's better to create a new topic...
First feedback:
I didn't found immediatly what to put in "Auto Discovery Prefix:" in mqtt hardware ; it's the same as "Discovery prefix" in ZWaveJS2MQTT => I set homeassistant

All devices seems to have been created ; I didn't check one by one... There were created Used what I found a bit strange...

I've tried some and they passed my simple tests (On / Off / Watt)

I still have the issue with FIBARO FGRGBWM441 RGBW Controller: no specific panel to change the colors, only a lot of dimmers
see https://domoticz.com/forum/viewtopic.ph ... ro#p278978
And I need to read https://www.home-assistant.io/docs/mqtt/discovery/

There is a mqtt_autodiscovery topic on slack. Any missing devices you can post the autodiscovery message there. Let me know if you need an invitation for the domoticz slack channel.

Sent from my SM-G980F using Tapatalk

Post the mqtt topic & payload of the config for the device so we can have a look to see what happens.
Jos

What about the config of several devices I posted on slack?
Do you want me to post them again?
Because 25% of my devices are not working or not working properly.

A tremendous amount of things have changed over the last week or so. Maybe these got lost so probably good to summarise what is not working, again, by posting on slack.

Sent from my SM-G980F using Tapatalk

EddyG wrote: Sunday 24 October 2021 8:38 What about the config of several devices I posted on slack?
Do you want me to post them again?
Because 25% of my devices are not working or not working properly.

Which one ? The LastSeen is discussed and looked at.

I summarize them again and put them on slack.

heggink wrote: Saturday 23 October 2021 16:09 There is a mqtt_autodiscovery topic on slack. Any missing devices you can post the autodiscovery message there. Let me know if you need an invitation for the domoticz slack channel.

Sent from my SM-G980F using Tapatalk

Ok for the slack, never used, I'll look at it... I'll be busy next week and on holiday after, so perhaps few contributions at the beginning
To give a positive feedback, I have a motion sensor that "disconnects" every week from openzawe that is still ok in zwavejs2mqtt on my testing environment, important because it's for the outside light
For the RGB controller perhaps there is a part in the discovery and another one with json directly on zwavejs2mqtt
See viewtopic.php?t=8605
What is used now is something like this http://localhost:8080/json.htm?type=com ... 2_Ng%3D%3D
Do you have an example of json directly on ZWaveJS2MQTT? and I'll did the script after (I'll try)
Also https://community.home-assistant.io/t/f ... ms/37235/2

I've done some testing and could report some results on the slack when invited

I think I need to upgrade
My
zwavejs2mqtt: 5.4.6
zwave-js: 8.1.1

on the git: Release 5.10.0
But I don't find out how to do it

Did you read https://zwave-js.github.io/zwavejs2mqtt/#/

I strongly suggest you run this in a docker container. Easiest to upgrade and roll back if need be.

Sent from my SM-G980F using Tapatalk

Also: please note that, even though autodiscovery is in its final stages of development, breaking changes may still occur. The current state is still beta.

Just a word of caution!

Sent from my SM-G980F using Tapatalk

EddyG wrote: Tuesday 26 October 2021 10:02 Did you read https://zwave-js.github.io/zwavejs2mqtt/#/

yes
but perhaps, I'm on the latest!
What version do you have?

zwavejs2mqtt: 5.4.5
zwave-js: 8.0.8
I am a bit behind (don't fix what ain't broken)...

Sent from my SM-G980F using Tapatalk

On Docker Hub 5.10.0 see https://hub.docker.com/r/zwavejs/zwavejs2mqtt/tags

I've managed to upgrade to 5.10.0 latest did not work
I had to remove the container before As I'm not so good with dockers and containers, I've lost all the naming...
So, some time to redo this...

@hestia I would recommend that you have your entire configuration is a local folder that you can easily access. I have all my data in /opt/zwavejs2mqtt/store. That way, you can stop the docker container, backup that folder and start a new container using a different release. If that then fails for whatever reason, you can just put back everything you backed up and start the original container again to be back where you were.

Using the above, I start it as follows:
If you want to test a new release, you could name the docker container zwavejs-test ie stop zwavejs2mqtt, start zwavejs-test, test the new container, if not OK, stop zwavejs-test and start zwavejs2mqtt again. The fun part is that you can have multiple versions with different names. As long as they use the same config dir (/opt/..), you will never lose any config.

@heggink,
thanks again for your help
I was stuck on the upgrade because when I've tried this "latest" there was no upgrade
So I tried several things... and could upgrade!
I was more focus on the upgrade to check if I could get a device ZP3102 than to keep my data as it was a testing env.
I saw your advice "don't fix what ain't broken"
I my case the ZP3102 was fixed with the last version installed (I read it was fixed in a version after mine, but could not retrieve the info now).
Now all my devices were seen in dz at least once