Same here, RMN chenged their app, now de API isn't accessible anymore. The data is somewhere out there, does somebody have a solution?

Since last night I cannot access the RMN API anymore: HTTP/1.1 response: 404 ==>> Not Found

It appears that they've launched a new app at 16 January, which might relate to this: https://www.rmn.nl/rmn-app/

Any ideas how it is possible to gather the data now?

This is where I found it, it is really a description about how the log is kept: https://www.domoticz.com/wiki/Applicati ... og_History

But you might be right, i'll give it a try later!

If I understand the manual correctly this is aimed at showing and keeping the data in the log of a sensor. Not about the update of the sensor itself?

I was exactly looking for this functionally. Is this already possible, or is there a workaround?

Wow surprise here! I was doing online checks for other devices with Crojobs. But this is much more convenient!

Hehe thanks for the out of the box thinking (don't know why i could not come with such a bright solution myself )

I am using a script to monitor the production of a Omnik/Hosola solar inverter (see below if you would like to reuse this, it also include a warning when the production is too low and a daily report of production). When the sun is not shining, the inverter is powered down. Which means that the http ...

Great, I misunderstood the documentation. Thank you!

I'm testing a trigger of a dzVents script by a MQTT command send by NodeRED. Domoticz is set-up to receive MQTT commands through with the domoticz/in prefix (this works to trigger devices already). I've created a test flow in NodeRED, which results in the following output on MQTT: Schermafbeelding ...

Thanks both! Both solutions work actually.
This saved me a lot of trial and error and googling

I feel a bit stupid, the command is working in the console, but I cannot get it working by sending it through a dzvents script. I've tried: os.execute("mosquitto_pub -h localhost -p 1883 -t 'zwave/nodeID_17/112/0/9/set' -m '{"value": 100}'") dz.executeShellCommand("mosquitto_pub -h localhost -p 1883 ...

great thanks a lot, your example is already working. But I should start setting a username and password for security

Thanks voor your guidance waltervl I've done some tests and I'm now able to update the parameters according to the MQTT API manual, through MQTT Explorer. See the example where I've successfully updated the thermostat value tot 95 (9.5 degrees): Schermafbeelding 2023-01-10 091706.png I'm ...

After migration to ZwavejsUI I have troubles with one of my devices, as not all parameters are appearing as devices in Domoticz (Auto discovery issue: https://www.domoticz.com/forum/viewtopic.php?t=39694) I was also used to update some of the parameters with dzVents scripts, using commands like this ...

After some work I've successfully migrated from OpenZwave to zwavejs. Most devices are working properly, though there is one problem with my Heatit floor heating thermostat (Z-TRM2fx / https://devices.zwave-js.io/?jumpTo=0x019b:0x0003:0x0202:3.0# ). Using OpenZwave in my old configuration there were ...

Thanks for the tip, using MQTT explorer I indeed found that zwavejs was not sending data. And I found that the 'localhost' was also used in the MQTT configuration in zwavejs. Based on this topic I was under the impression that it was about the localhost in the Domoticz hardware configuration. Now I ...

I'm trying to update to Zwave JS UI, from OpenZWave, but don't get the autodiscovery working. No new devices are appearing: Mosquitto is working fine Z-Wave JS UI is installed an works fine, I can access it throught the web interface. I've updated all settings in JS UI according to the migration ...

Hummm.. do not see what could be wrong... Still problems ? Unfortunately it is still not working. Strange enough I recently received 1 update of the calendar items in the device. Only full-day events are included in the timer and when I ran a test soon after (by adding extra calendar items) they ...

I still cannot wrap my mind around the problem that my devices are not updated by the plugin. I've tried multiple things: Reinstall the plugin/hardware (by removing the devices) Checking whether the device numbers match with the devices used by the plugin Switch the Default to AtWork: to TRUE and ...