Domoticz

vco1

Indeed: Dzvents cannot handle 2 devices with exactly the same name. The device name should be unique.

And that turned out to be the cause of the issue. I had 2 devices with the same name. Two completely different types of devices - a temperature sensor and a switch - but the same name anyway ...

vco1

waltervl wrote: Thursday 23 October 2025 17:04 Is device lampBalcony the same type of device as the other switches?

Yes. They're all on/off switches.

vco1

So

local lampReading = 123
local lampBookcase = 456
local lampBalcony = 789

return {
on = {
devices = {
'$NodOn Soft Remote Grey_scene_state_scene_001_0',
'$NodOn Soft Remote Grey_scene_state_scene_001_3',
'$NodOn Soft Remote Grey_scene_state_scene_002_0',
'$NodOn Soft Remote Grey_scene ...

vco1

That's done later in the script.

Problem is that it ain't working for switch with id 123 but it is working for id 456 (a different switch/light).

Id123 does work when testing it through the API, e.g. through Postman.

vco1

I have a couple of scripts for NodOn Soft Remotes. They basically just switch on/off several lights based on the button pressed on the remote.

For one of these scripts one ZWave switch is not working anymore. That is, the light does not turn on or off based on the button clicked on the remote ...

vco1

I had several log statements in my script. Nothing got logged though. And yes, I did check all the settings. Even set the log level on the commandline tot debug and restarted domoticz. To no avail.

vco1

I got it working by creating a (hidden) text device with the full payload, a virtual device for the status and a dzVents script to tie it all together. In the end the biggest hurdle was the fact that I didn't get any logging from the dzVents script and thus had to do it by trial and error.

vco1

the TheengsGateway supports the Homeassistant autodiscover protocol that Domoticz also supports. It just could create some sensor automatically. Did you already try that? Although funky value templates with if then else are not supported.
https://wiki.domoticz.com/MQTT#Add_hardware_%22MQTT_Auto ...

vco1

First of all, thanks for this great plugin. It's a Swiss army knife.

I'm trying to implement a bluetooth (BLE) tracker as a presence tracker in Domoticz with the TheengsGateway as the intermediary. These trackers don't provide an on/off value, but instead just the rssi value. If the rssi element in ...

vco1

DrMacabre wrote: Tuesday 13 May 2025 12:02 where do you find domoticzhandler.py ?

In your AWS Lambda function.

vco1

vco1 wrote: Monday 12 May 2025 15:01 For me discovery of new switches stopped completely.

Fixed.
In DomoticzHandler.py make the following change:

Code: Select all

# response = self.api('type=scenes')
response = self.api('type=command&param=getscenes')

vco1

i've fixed the last error. Setting scenes to false. I have not scenes so the script throw an error, instead of send an empty response or so.
No I get all th devices in test script inside skill, but....
The linkng account.... it's impodsible. I cant link my account with the skill and so I cant use ...

vco1

For me discovery of new switches stopped completely.

vco1

I found, and fixed, the issue with the disappearing settings as a.o. reported by @Hencor in this post.

Believe it or not, but this is caused by the name tag in the plugin definition:
<plugin key="MqttMapper" name="MQTT Mapper with LAN Interface" author="Flying Domotic" version="1.0.19 ...

vco1

Xenomes wrote: Friday 23 February 2024 20:29 The issue has been resolved in later versions of Domoticz.

I’m running 2024.4. Problem still exists. And so far only with this plugin.

vco1

I added a second value, and again no value ....

{
"T_Living": {
"topic": "ebusd/ctlv2",
"key": "ebusd/ctlv2/z1RoomTemp",
"type": "80", "subtype": "5", "switchtype": "0" ,
"mapping": {"item": "", "multiplier": 0.1}
},

"T_Outside": {
"topic": "ëbusd/ctlv2",
"key": "ëbusd/ctlv2 ...

vco1

I think you found a bug!
If you put a other plugin in the plugin folder that uses DomoticzEX framework the value of Type: of the Mapper plugin is visible.
So a dirty fix is:
cd ~/domoticz/plugin
git clone https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin.git
sudo systemctl restart ...

vco1

I think it's not fair to (fully) blame the Domoticz developers for all the troubles people seem to have with the migration to zwave-js. But in all honesty, this wasn't a fun job at all and I spent way more time and energy on this migration than I wanted to (or should have).
I have a relatively small ...

vco1

For the ones that are also getting the "Is not responding" response when activating/deactivating groups/scene's I found a solution.

In AlexaSmartHome.py on line 454 and 466 change 'timestamp': '%sZ' % (datetime.utcnow().isoformat(),) into 'timestamp': '%sZ' % (datetime.utcnow().isoformat(sep='T ...

vco1

I've set up Alexicz successfully lasty week, the only strange thing than I'm heaving is when using scene's/groups, when I tell Alexa to activate a scene it responds with "I'm having trouble reacing null" but the scene is activated, so it's only the response that is faulty.
Is this a known issue ...

Search found 29 matches

Re: Switch does not switch

Re: Switch does not switch

Re: Switch does not switch

Re: Switch does not switch

Switch does not switch

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Alexicz - FREE Domoticz to Alexa Integration

Re: Alexicz - FREE Domoticz to Alexa Integration

Re: Alexicz - FREE Domoticz to Alexa Integration

Re: Alexicz - FREE Domoticz to Alexa Integration

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Alexicz - FREE Domoticz to Alexa Integration

Re: Alexicz - FREE Domoticz to Alexa Integration