I stopped both Mosquitto and Zwave JS UI.
Then I started Mosqutto before I started Zwave JS UI.
Now it is working again.
Previously I tried to reboot the system but that did not help. So, I guess there is a dependency on the start order of the servives.
Is there a better expalnation?

Hi FireWizard,
Thank you for the prompt comment.
Yes. I can connect to the broker with MQTT Explorer.
Which timeout parameter are you referring to? Where is it set?
In Zwave JS UI I only find "MQTT/Reconnect period (ms)" I use the defaut 3000ms.

I'm in the process of migrating from OPENZWAVE to Zwave JS UI/MQTT
I managed to follow the guideline so that all devices show in Domoticz but they did not function.
I got suck so I decided to readd all the devices.

The procedure is simple.
1. Exclude the device
2. Include the device
3. Enable ...

Recently I installed a Fibaro Double switch (FGS-223) with the purpose to monitor the status of the Automower.
In order to do that I’m dependent on the FGS-223 to report the power usage but unfortunately it is not working as expected.
FGS-223 should report power usage upon change. In my case I ...

Ok. I see. Maybe someone find the time to fix the issue so no workaround is needed. In my use case where the input comes from a triggered alarm a 2 second delay does not have any impact on the user experience so I can use the delay. Thanks for the clarifcation.

Thanks for the suggestion.
I improved it by skipping the "afterSec(2)". Then there is an instant refresh of the UI.

Version: 2020.2 (build 12230)
Platform: Raspberry Pi
Plugin/Hardware: N/A

Description:
I'm trying to use the setIcon function in a simple dzVents script in order to change the icon of a dummy selection switch.


return {
on = {
devices = {
'Larmstatus'
}
},
execute = function(domoticz ...

Thanks for the prompt responses.
I'm not very keen on changing the battery optimization settings but I found this article:
https://firebase.google.com/docs/cloud-messaging/concept-options#setting-the-priority-of-a-message

In my understanding the FCM messages can be sent with Normal priority ...

Thanks for the prompt responses.
I'm not very keen on changing the battery optimization settings but I found this article:
https://firebase.google.com/docs/cloud-messaging/concept-options#setting-the-priority-of-a-message

In my understanding the FCM messages can be sent with Normal priority or ...

I have this problem for a long time already (since Android 9). In my case may be related to Oxygen OS. Eventually I found out that disabling Android Doze does the job. Running
su
dumpsys deviceidle disable

in an Android terminal (I made a tasker task to do this) does the job for me. From ...

I'm running version 0.2.187 (6509) of the app.
Since Android 10 notifications do not appear promptly while the phone is in standby. It can take 10-15 minutes before the app show a notification.
This was not the case on Android 9 where the notifications showed promptly (within 1-2s) in the phone.
I ...

Today I got the update (0.2.187 (6509)
Notifications seems to work again.

I'm running Domoticz 4.10962 on Raspberry Pi
Notifications were woriking fine until I reinstalled the app (version 0.2.180, 6474) on the phone (Xperia 1 /Android 10)
Any idea why it is not working anymore?


I got hold of a Pixel device which reproduces the issue.
It would be great if this issue ...

I'm running Domoticz 4.10962 on Raspberry Pi
Notifications were woriking fine until I reinstalled the app (version 0.2.180, 6474) on the phone (Xperia 1 /Android 10)
Any idea why it is not working anymore?

+1 On this one.
I don't use Sonos with Domoticz yet but might do it in the future.
In general I think the Domoticz UI could improve a lot if all virtual sensors/switches had customized icons just like the physical switches.

Skickat från min H8216 via Tapatalk