Search found 246 matches
- Sunday 25 January 2026 17:50
- Forum: Device information
- Topic: Best Z-Wave smoke detector for Europe (2026)
- Replies: 4
- Views: 70
Re: Best Z-Wave smoke detector for Europe (2026)
Never had the need to update ....
- Sunday 25 January 2026 12:33
- Forum: Device information
- Topic: Best Z-Wave smoke detector for Europe (2026)
- Replies: 4
- Views: 70
Re: Best Z-Wave smoke detector for Europe (2026)
I'm using the FGSD002 it is small and does what is needed and is battery powered.
- Saturday 24 January 2026 12:37
- Forum: Bugs and Problems
- Topic: MQTT AD Dimmer switches issue in beta 17003
- Replies: 11
- Views: 261
Re: MQTT AD Dimmer switches issue in beta 17003
I checked the Zigbee2MQTT parameter and it is set right. Ive downloaded my setup file in Dockge:
services:
domoticz:
image: domoticz/domoticz:2025-beta.16997
#image: domoticz/domoticz:beta
container_name: domoticz
restart: unless-stopped
ports:
- 8080:8080
- 8443:443
- 6144:6144
volumes ...
services:
domoticz:
image: domoticz/domoticz:2025-beta.16997
#image: domoticz/domoticz:beta
container_name: domoticz
restart: unless-stopped
ports:
- 8080:8080
- 8443:443
- 6144:6144
volumes ...
- Friday 23 January 2026 10:16
- Forum: Bugs and Problems
- Topic: MQTT AD Dimmer switches issue in beta 17003
- Replies: 11
- Views: 261
Re: MQTT AD Dimmer switches issue in beta 17003
I use Dockge, so I update in the Dockge application. Within Dockge I have Domoticz, zwave-js-ui, zigbee2mqtt, nefiteasy-http-server, modbusproxy, eclipse-mosquitto and ebusd
It went fine upto around 16997, I updated the beta and I refreased the program. I had problems with the versions after that ...
It went fine upto around 16997, I updated the beta and I refreased the program. I had problems with the versions after that ...
- Thursday 22 January 2026 20:53
- Forum: Bugs and Problems
- Topic: MQTT AD Dimmer switches issue in beta 17003
- Replies: 11
- Views: 261
Re: MQTT AD Dimmer switches issue in beta 17003
After loading a fresh release
- Thursday 22 January 2026 16:50
- Forum: Bugs and Problems
- Topic: MQTT AD Dimmer switches issue in beta 17003
- Replies: 11
- Views: 261
Re: MQTT AD Dimmer switches issue in beta 17003
Does anyone know why i need to restart Domoticz server to get it to see Zigbee2MQTT and Z-wave JS UI?
Otherwise Domoticz runs but is does not update any swiches.
Otherwise Domoticz runs but is does not update any swiches.
- Thursday 08 January 2026 17:21
- Forum: Bugs and Problems
- Topic: MQTT AD Dimmer switches issue in beta 17003
- Replies: 11
- Views: 261
Re: MQTT AD Dimmer switches issue in beta 17003
Had an incident again.
Reverted back to Domoticz version 16997 and reset the whole PC which has it running ..... And now it all works. Did something change?
Reverted back to Domoticz version 16997 and reset the whole PC which has it running ..... And now it all works. Did something change?
- Thursday 08 January 2026 10:53
- Forum: Bugs and Problems
- Topic: MQTT AD Dimmer switches issue in beta 17003
- Replies: 11
- Views: 261
Re: MQTT AD Dimmer switches issue in beta 17003
Ok, i got it solved.
It was a very strange way of doing things. Because I had errors in both Zwave-JS-UI and Ziggbee2mqtt I reset both, set Domoticz to use the previous version 16997. I reset the switches in Zwave-JS, and refreshed them, and restarted the application several times. All of a sudden ...
It was a very strange way of doing things. Because I had errors in both Zwave-JS-UI and Ziggbee2mqtt I reset both, set Domoticz to use the previous version 16997. I reset the switches in Zwave-JS, and refreshed them, and restarted the application several times. All of a sudden ...
- Tuesday 06 January 2026 13:35
- Forum: Bugs and Problems
- Topic: MQTT AD Dimmer switches issue in beta 17003
- Replies: 11
- Views: 261
MQTT AD Dimmer switches issue in beta 17003
I am using MQTT Auto Discovery
I have some problems in 17003 with Dimmer switches, they don't turn off anymore ..... Also tried to switch from the Domoticz UI and it fails. Its local to Domoticz, i tried in Z-wave JS and it works fine.
error: Error sending switch command, check device/hardware ...
I have some problems in 17003 with Dimmer switches, they don't turn off anymore ..... Also tried to switch from the Domoticz UI and it fails. Its local to Domoticz, i tried in Z-wave JS and it works fine.
error: Error sending switch command, check device/hardware ...
- Sunday 23 November 2025 13:47
- Forum: Bugs and Problems
- Topic: New script does not run
- Replies: 2
- Views: 63
Re: New script does not run
Got it! Changed it to minutes.
Is there a reason why I don't see all my devices at start-up?
Is there a reason why I don't see all my devices at start-up?
- Sunday 23 November 2025 12:50
- Forum: Bugs and Problems
- Topic: New script does not run
- Replies: 2
- Views: 63
New script does not run
I think there is something wrong, my script does not run, I'm running the latest beta release. I also noticed not all my devices are being refreshed at every start-up, new feature?
return {
on = {
timer = { "every 30 seconds" } -- Test timer trigger
},
logging = {
level = domoticz.LOG_INFO ...
return {
on = {
timer = { "every 30 seconds" } -- Test timer trigger
},
logging = {
level = domoticz.LOG_INFO ...
- Tuesday 18 November 2025 16:11
- Forum: dzVents
- Topic: Enever: managed Counter kWh -> 1..24 scale for price index?
- Replies: 17
- Views: 900
Re: Enever: managed Counter kWh -> 1..24 scale for price index?
I think I got it to work.
How do you readout a managed counter? I'm working on it, i see the values in the variable logging
How do you readout a managed counter? I'm working on it, i see the values in the variable logging
- Monday 17 November 2025 23:47
- Forum: dzVents
- Topic: Enever: managed Counter kWh -> 1..24 scale for price index?
- Replies: 17
- Views: 900
Re: Enever: managed Counter kWh -> 1..24 scale for price index?
I turned StroomprijzenMorgen into StroomprijsMorgen, but still the error.
I checked the https site and I receive the site with the data.
but i still get 2025-11-17 23:15:00.272 Error: dzVents: Enever stroomprijs: Kon JSON niet parsen uit StroomprijzenMorgen.
What else can it be?
I checked the https site and I receive the site with the data.
but i still get 2025-11-17 23:15:00.272 Error: dzVents: Enever stroomprijs: Kon JSON niet parsen uit StroomprijzenMorgen.
What else can it be?
- Monday 17 November 2025 16:37
- Forum: dzVents
- Topic: Enever: managed Counter kWh -> 1..24 scale for price index?
- Replies: 17
- Views: 900
Re: Enever: managed Counter kWh -> 1..24 scale for price index?
I added StroomprijsMorgen as a uservariable and my token was added, but i still get the following error:
2025-11-17 16:36:00.193 Error: dzVents: Enever stroomprijs: Kon JSON niet parsen uit StroomprijzenMorgen
Ik heb StroomprijzenMorgen ook als user variable toegevoegd, maar dat was hem niet ....
2025-11-17 16:36:00.193 Error: dzVents: Enever stroomprijs: Kon JSON niet parsen uit StroomprijzenMorgen
Ik heb StroomprijzenMorgen ook als user variable toegevoegd, maar dat was hem niet ....
- Friday 14 November 2025 14:39
- Forum: dzVents
- Topic: Enever: managed Counter kWh -> 1..24 scale for price index?
- Replies: 17
- Views: 900
Re: Enever: managed Counter kWh -> 1..24 scale for price index?
I just integrated the script of the hourly prices, and that script also locates the lowest prices ...... maybe later, need to get some experience with it first
- Thursday 13 November 2025 15:07
- Forum: dzVents
- Topic: Enever: managed Counter kWh -> 1..24 scale for price index?
- Replies: 17
- Views: 900
Re: Enever: managed Counter kWh -> 1..24 scale for price index?
Thanks for the quick answer! That was it. When will getting the data on a 15 minute basis be made available in Domoticz?
I had to use the managed counter of Enever.
I had to use the managed counter of Enever.
- Thursday 13 November 2025 14:36
- Forum: dzVents
- Topic: Enever: managed Counter kWh -> 1..24 scale for price index?
- Replies: 17
- Views: 900
Re: Enever: managed Counter kWh -> 1..24 scale for price index?
I have Enever running with the API key.
I installed a managed counter and a switchIdx accoriding to your instructions:
local switchIdx = 3103 -- IDX van je schakelaar
local managedCounterIdx = 3102 -- IDX van de managed counter
I also tried Enever's managed counter 2977, same error
I tried ...
I installed a managed counter and a switchIdx accoriding to your instructions:
local switchIdx = 3103 -- IDX van je schakelaar
local managedCounterIdx = 3102 -- IDX van de managed counter
I also tried Enever's managed counter 2977, same error
I tried ...
- Tuesday 11 November 2025 13:10
- Forum: Python
- Topic: Python Plugin: MqttMapper
- Replies: 505
- Views: 69504
Re: Python Plugin: MqttMapper
I think i fixed it with " EBUSD_MQTTJSON: "" " in the settings.
Thanks
Thanks
- Tuesday 11 November 2025 13:08
- Forum: Installation, Compiling, Permissions, Security and Starting
- Topic: Enever NULL values cause time shift in Enever_Electricity_tomorrow variable
- Replies: 8
- Views: 3742
Re: Enever NULL values cause time shift in Enever_Electricity_tomorrow variable
I ran your script, but i get back "Could not open Energy_Prices_Today.csv for writing" ok that is clear.
het is al gelukt!
Greetings
het is al gelukt!
Greetings
- Saturday 01 November 2025 0:03
- Forum: Python
- Topic: Python Plugin: MqttMapper
- Replies: 505
- Views: 69504
Re: Python Plugin: MqttMapper
No, but I actually only readback from ebusd.
I don't see the exact message now, but if it happens i will write it here
I've also added EBUSD_MQTTJSON: "" to the settings, don't know if that will make it more consistent
I don't see the exact message now, but if it happens i will write it here
I've also added EBUSD_MQTTJSON: "" to the settings, don't know if that will make it more consistent