Ok I answer myself. I was ssuming that domoticz may have some kind of mapping table to translate the sensortype and scale vales coming from the Zwave driver. However apparently instead of using those values, domoticz tries to guess which device type fits better using the units of measurement. This ...

Hi, I recently added the referenced air quality sensor to my domoticz install. Most of the sensors came up correctly, but I have some issues of different criticality levels that I've tried to solve myself with no success. The setup is Domoticz 2024.7 (build 16360), with Zigbee MQTT Autodiscovery ...

Hi, in case others get into the same problem as me... I just upgraded to 10939 in a 1513+ cedarview version and go the OZW crash. Deleted the ozw cache file and restarted, seems to be working now. Thanks!

I reported the same issue back in November. Apparently the plug-in uses certain assumptions on the format of the rss responses to extract the information. In certain circumstances, the rss feed seems to use a slightly different format which causes the plug-in to fail. After some time the feed users ...

Should be doable using the information here:

https://github.com/xoseperez/espurna/wi ... ZLD-44EU-W

Yes I know what that option does, there is no need to repeat. The point is that that option disables creation of ALL devices, while the request is an option to disable creation of ONLY rfxcom devices. Ideally, I guess an option to disable creation of devices BY type would be also welcome.

I think that what the gjvdp is proposing is an option to disable automatic creation of new rfxcom devices. I would agree with the suggestion since I have the same problem.

Since I updated to last beta 4.10343, I started to see Domoticz crashing after some minutes after start. I traced down the problem to the Tuya plugin. As soon as I disabled it, domoticz didn't crash any more. See below the last lines in the domoticz.log file right before crashing, in case it helps ...

I was actually looking into that... and you nailed it. The issue is caused by the Tuya plugin by Tixi. Once I disabled it, domoticz does not crash anymore.

No need to recompile the older version. Many thanks for your help!

I think it was around 4.10320 but I'm not sure of the exact version number. I've been running the python version since the last non-beta version with no problems. Meanwhile, I'm checking the syno config in case I see something changed that could be causing this. Which plugin script are your ...

Adding below the last lines of the domoticz.log file in case someone can imagine what's going on... no changes done since last beta update, just the domoticz upgrade. 2019-01-11 16:22:30.438 Error: Domoticz(pid:9358, tid:9440('PluginMgr_IO')) received fatal signal 11 (Segmentation fault) 2019-01-11 ...

Many thanks. I tried the new version but still have the same problem.

It's actually possible to downgrade. Is there some way to download the previous beta version (with Python)?

Thanks,

Hi,

I just installed version domoticz_cedarview-6.2_4.0.10327-8.spk on my Syno. After some minutes, it crashes. The previous beta version worked perfect. Would it be possible to download it again so I can downgrade?

Many thanks in advance.

By the way - personally I would leave the present setup that on and off fence notifications are always sent whichever the current status of the switch is. This allows Domoticz to record the time of each change in case it's needed. At most, I would recommend leaving this as an option.

In case it may help... I had a similar issue, my phone worked correctly, my wife's worked when at home but not when out of home. After a lot of investigation, it turned out to be a "%" character in the domoticz password, in conjunction with authentication set to be only required when connected from ...

I'm using a regional feed and getting an error in line 189, and the device shows no data. The web site is showing an alert right now. The feed is: <?xml version="1.0" encoding="utf-8" ?> <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> <channel> <atom:link href="http://meteoalarm.eu ...

No, just select it in the hardware tab, click on Enable, click on Update, select or again, click on Enable, then on Update. That should trigger it. If not, you can always restart the full domoticz.

Did you restart the plug-in after allowing devices creation? That should trigger detection of new devices

Have you tried the Tuya plug-in? It looks like it may work with this device.

That can easily done from Domoticz using the alexa_remote_control.sh script. Search in Google for it for complete info.