OK, I just found the download section on the website https://www.domoticz.com/downloads/ (stangely the wiki does not refer to that page, I only found it becasue it was mentioned in another forum topic. . .) Took the file from there and installed. One happy camper running 2024.7 now But I guess ...

I finaly found the time to update my RaspberryPi armv7l Domoticz 2024.4 version (to 2024.7 I expected) The updaterelease script fails however. Turns out that an empty domoticz_release.tgz is downloaded. When I check https://github.com/domoticz/domoticz/releases/ there only seems to be an x86 64bit ...

Popping in on this question of the compare graph. I have a managed counter that records the hourly energy prices (date + timestamp) Once a day I store the average price per day into the history of the managed counter (date without timestamp) The compare graph seems to be following that last daily ...

Since every (post) function we try returns an error 500, it looks liket that someting is clearly wrong on the Volvo side, so I can report that to them. To quote myself, It looks like Volvo has changed something at their side, because locking/unlocking the car seems to work now. Tx, glad it works ...

I am looking for a solution to show in one graph: 1. The historic values from the managed counter (today + tomorrow) of the hourly electricity prices (device 1676) 2. The setpoint (device 1677) that indicates when I qualify a given electruicity price as 'high (above setpoint) or ĺow' (below setpoint) ...

OK, apparently dzVents does not work as described here. Generally it appears that when using .updateQuiet, you have to provide the nValue , i.e 1 instead of 'On' and 0 instead of 'Off' This applies to other type of devices as well. E.g. for a Doorlock you have to use 1 instead of 'Locked' and 0 ...

Oh well forget about the above error. Talking about blindness of your own code. I happened to mis-type the variable of the device idx: idxPreconditionng should be idxPreconditioning BUT: still my device state is not updated with this corrected code, so any help is still appreciated! if ...

I have a device of type 'switch' defined that I want to use to control the preconditioning of my EV. Triggering the device submits an API call to the car to switch the preconditioning on or off. At the same time I have a script that collects the actual status of the car (including precontitioning ...

For whatever reason in the past I have created a Temperature sensor that should have been a Setpoint device (it shows the SetPoint temperature of my heatpump heating buffer). I have now corrected this (so the value is shown on the Utility tab and not on the Temperature tab). I would like to migrate ...

Hi @akamming There is an option that hasn't been added in de python plugin yet. It is reading and setting charging amperage . I'd be very happy if it could be added. Would serve well to balance PV output and home power consumption where the car can be charged from excess solar energy. Please look ...

Yeah, found that as well.
Hence my question if 'someone' could change the hardcoded constant into a hardware setup item. . . .
My programming skills are rather limited once it goes beyond backend (and 'simple') Python coding....

I am using the AirconWithMe plugin for some time to control my Mitsubishi Heavy Industries airco/heatpump. Works like a charm, but I notice that the data from the AirconWithMe is updated every 30 seconds. because I want to minimize the traffic on my network, I´d like to change this. Of course I can ...

Thx for clarifying and advice !
I think I just have to drop my general approach here and do more in dzVents because it simply is capable of doing more things and doing thins better....

I prefer to use Blocky events as long as what I want to acgieve is do-able in blocky.... This weekend I noticed some unexpected behaviour: I have a virtual switch that (when Ón, used to register if there is anyone 'in the room') should enable switching on/off a heater based on a Thermostat Setpoint. ...

Solved: Created a dzVents event with code: return { on = { devices = { 445 } }, -- Idx of correct momentary switch execute = function(dz) dz.devices(210).toggleSwitch() -- Idx of switch to todggle end } Instead of one value for the Idx of the momentary switch, you can also provided a comma separated ...

Found a working solution I created a dzVents event return { on = { devices = { 445 } }, -- Idx of correct momentary switch execute = function(dz) dz.devices(210).toggleSwitch() -- Idx of switch to todggle end } I think I can just add similar code-blocks for every momentary switch I want to get ...

Mmmm, apparently a bad search. Found something VERY similar: viewtopic.php?t=37950

I have a TuYa TS0041 momentary switch. This switch generates 3 devices in Domoticz that get triggered based on the ' type' of buttonpress: single, double or hold. The Zigbee2MQTT part and the integration with Domotiocz seem to be OK.... The trouble I seem to have is that the 'on' on the Domoticz ...

FireWizard wrote: ↑Sunday 09 October 2022 19:59 Hi,

More info:

https://discourse.nodered.org/t/eebus-know-how/17582

Regards

Update in that thread (and similar to what I learnt from Vaillant): "Yes we do support Eebus via VR921, but unless you are a business partner you will not get access".
Very customer-minded I would say....

Finally I found the time to upgrade my old Domoticz to the newest version and also include MQTT Autodiscover. At another location I already have that running, so was not expecting much issues. All seems OK, Zigbee2MQTT picked up my Zigbee devices (all data exposed and in Zigbee2MQTT. But for unclear ...