Hi akbooer,
I've an installation with a centralized openluup/DY on Debian 11 where're archived and consolidated several remote openluup/DY on RPI. I'm also using a user-defined (defined with your support) "DataUser.lua" to process metrics and creating different metric names. I've a schema of this configuration but I can't upload on forum.
I'd like to manage outage network connections between remote and centralized system while the remote DY is running and archives data locally.
I see the whisper-fill.py python routine (https://github.com/graphite-project/whisper/blob/master/bin/whisper-fill.py) from Graphite tool. I know that DY/whisper format is different from Graphite/whisper (CSV vs. binary packing), but based on your deep knowledge and experience is it hard to adapt the fill routine to DY/whisper format ?
tnks
donato
Been using zigbee2mqtt and openLuup for sometime now and it is working well.
I attempted to add another Hue switch to-day. It's a newer version of the other ones I have been using so far. They are pretty much identical.
The older ones installed no problem (which is weird), but the new one won't. Looking at the code, it looks this function in L_Zigbee2MQTTBridge.lua:
configure_scene_controller(dno)is not being passed the parameter "dno" when the function is called. The device is created but is incomplete.
Just out of interest how do you pretty print to the log from within say L_Zigbee2MQTTBridge.lua? I tried a few incarnations such a:
local pretty = openLuup.loader.shared_environment.prettybut they all failed.
Originally I was using Futzle's UPnP event proxy plugin on Vera with the Sonos plugin. Worked very well.
On making the move to openLuup, one finds that the proxy can't be used because the proxy daemon start and stop, etc uses a script installed by the plugin that only works on openWRT, as used by Vera.
The Sonos plugin still works without the proxy but it reverts to polling. It becomes a bit on the sluggish side and sometimes doesn't function quite as intended.
I've modified the proxy plugin to install a script that runs as a systemd service. systemd can be found on a lot of contemporary Linux installs, including Raspberry Pis. To make use of; just install the plugin from the AltUI app store and restart the Luup engine a couple of times. The dashboard should indicate "Status: Proxy running".
Note that the service file expects "L_UPnPProxyDaemon.lua" to be located at the typical plugin files location:
/etc/cmh-ludl/After the plugin is installed, the service file should be found in:
/etc/systemd/system/as UPnPProxy.service.
If you use the Sonos plugin, you need to change the variable "UseProxy" to "1" and restart the LuupEngine. In the Sonos parent device, you should see: "Running x zones; proxy detected".
Updated doco here.
Hope it works - YMMV.
Well pretty sure I didn't change or touch anything! I've turned everything on and off again as one might hope. Excepting a total reboot of the Pi3 that's running all my stuff very reliably in openLuup.
It's all been working well for years and now all of sudden 6 second alerts are truncated to about 4 seconds. Occasionally it works as it should. I see this in the log - does it help?
2023-02-20 09:39:06.662 luup_log:0: My Lua ver 0.50 debug: executing scene 63: "Check windows doors" in room: "Watchers" 2023-02-20 09:39:06.663 luup.call_action:: 217.urn:micasaverde-com:serviceId:Sonos1.Alert 2023-02-20 09:39:06.663 luup.call_action:: action will be handled by parent: 214 2023-02-20 09:39:06.663 luup_log:0: My Lua ver 0.50 debug: rest of scene 63 was executed 2023-02-20 09:39:06.663 luup.scenes:: scene 63, Check windows doors, initiated by AltUI 2023-02-20 09:39:06.665 luup_log:214: Sonos: Alert action on device 217 URI "http://redacted:3480/www/sounds/AllClosed.mp3" duration "6" 2023-02-20 09:39:06.758 luup_log:214: Sonos: UPnP_request (Pause, urn:schemas-upnp-org:service:AVTransport:1): status=1 statusMsg=500 result=[<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns="urn:schemas-upnp-org:control-1-0"><errorCode>701</errorCode></UPnPError></detail></s:Fault></s:Body></s:Envelope>] 2023-02-20 09:39:06.759 luup_log:214: stack traceback: ./L_SonosSystem1.lua:265: in function 'error' ./L_SonosUPnP.lua:289: in function <./L_SonosUPnP.lua:169> (tail call): ? ./L_SonosSystem1.lua:3390: in function 'sayOrAlert' ./L_SonosSystem1.lua:3452: in function 'queueAlert' ./L_SonosSystem1.lua:3843: in function <./L_SonosSystem1.lua:3839> (tail call): ? [C]: in function 'pcall' ./openLuup/scheduler.lua:204: in function 'context_switch' ./openLuup/scheduler.lua:366: in function 'dispatch' ./openLuup/scheduler.lua:588: in function 'task_callbacks' ./openLuup/scheduler.lua:699: in function 'start' openLuup/init.lua:354: in main chunk [C]: ? 2023-02-20 09:39:06.888 luup.variable_set:: 214.urn:toggledbits-com:serviceId:SonosSystem1.zoneInfo was: {"zones":{"RINCON_000E58DC7BBE01400":{"Location":"http://redacted3:1400/xml/device_description.xml","Group":"RIN... now: {"zones":{"RINCON_000E58DC7BBE01400":{"Location":"http://redacted3:1400/xml/device_description.xml","Group":"RIN... #hooks:0 2023-02-20 09:39:06.895 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.TransportState was: STOPPED now: TRANSITIONING #hooks:0 2023-02-20 09:39:06.901 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentPlayMode was: SHUFFLE_NOREPEAT now: NORMAL #hooks:0 2023-02-20 09:39:06.913 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentTransportActions was: Set, Stop, Pause, Play, X_DLNA_SeekTime, Next, X_DLNA_SeekTrackNr now: Set, Stop, Pause, Play, X_DLNA_SeekTime, X_DLNA_SeekTrackNr #hooks:0 2023-02-20 09:39:06.921 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.NumberOfTracks was: 10 now: 1 #hooks:0 2023-02-20 09:39:06.922 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.AVTransportURI was: x-rincon-queue:RINCON_000E58DC7BBE01400#0 now: http://redacted:3480/www/sounds/AllClosed.mp3 #hooks:0 2023-02-20 09:39:11.929 luup_log:214: Sonos: UPnP_request() "urn:schemas-upnp-org:service:AVTransport:1"#"GetPositionInfo" action took 5.0073010921478s (long) 2023-02-20 09:39:11.932 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentTrackDuration was: 0:02:22 now: 0:00:00 #hooks:0 2023-02-20 09:39:11.933 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentTrackURI was: x-file-cifs://ELEPHANT1/Multimedia/My%20Music/Music%20JP/The%20Smiths/The%20Queen%20Is%20Dead/08%20Vicar%20in%20a%2... now: http://redacted:3480/www/sounds/AllClosed.mp3 #hooks:0 2023-02-20 09:39:11.934 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentTrackMetaData was: <DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:r... now: <DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:r... #hooks:0 2023-02-20 09:39:11.936 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentStatus was: Vicar in a Tutu: (The Smiths, The Queen Is Dead) now: AllClosed.mp3 #hooks:0 2023-02-20 09:39:11.937 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentTitle was: Vicar in a Tutu now: AllClosed.mp3 #hooks:0 2023-02-20 09:39:11.937 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentArtist was: The Smiths now: #hooks:0 2023-02-20 09:39:11.938 luup.variable_set:: 217.urn:upnp-org:serviceId:AVTransport.CurrentAlbum was: The Queen Is Dead now: #hooks:0Also see these:
2023-02-24 16:12:13.576 openLuup.server:: GET /www/sounds/YouRang.mp3 HTTP/1.1 tcp{client}: 0x17e96f0 2023-02-24 16:12:13.579 openLuup.server:: error 'closed' sending 43102 bytes to tcp{client}: 0x17e96f0So any clues?
I've got myself a nice Ecovacs Deebot 950, because one of the Roombas is getting really old (12 years and still going strong). It's my first one connected to WiFi, since the others are legacy. I've found a nice mqtt library and it's already pushing to my broker in real time, but I'm wondering if there's a generic device template and/or service, otherwise I'll start building one and I'll try to keep it as much generic as possible.
Hi,
I've installed switchboard plugin from openluup app store but I'm not sure which action to use to create a binary switch. I try "addswitch" action but I see the device only after using the "addchild" action too. is it correct ?
Attached the openluup device screen, the control switchboard and the actions i see.
tnks donato
switchboard_openluup_console.png
Hi @akbooer,
I have an updated version of one of my plugins but I cannot publish it in the ALTApp Store. When I click publish it gets in a sort of loop of Refreshing Token.../Token refreshed. However, I never get to page to refresh the token.
Looking at the browser debug window I see this as the response to http://192.168.178.101:3480/data_request?id=lr_ALTUI_Handler&command=refresh_auth_token
{"error":{"code":400,"message":"Bad Request - invalid_grant","step":"Get access token from refresh token"}}
Running openLuup v21.7.25. Any suggestion?
Cheers Rene
Hi Patrick/AK Booer
I am able to see Reactor expressions in the AltUI UI per the below and the expressions work as they should in my reactor sensors. When an expression changes, the reactor sensor responds accordingly.
javascript.png
However, I cannot see the expressions in luup state variables or the luup logs:
Luup.png
Log.png
I tried reinstalling openLuup (latest development) and when that failed to change the noted behavior, I reinstalled lua5.1. There was also no change. Rebooting the machine also produced no change.
I suspect this is an openLuup issue as I also see nil values for some plugins:
plugin.png
And other plugins are fine:
2022-01-12 20:47:12.027 luup.variable_set:: 63.urn:upnp-micasaverde-com:serviceId:Weather1.CurrentDewPoint was: 32 now: 29.7 #hooks:0 2022-01-12 20:47:12.028 luup.variable_set:: 63.urn:upnp-micasaverde-com:serviceId:Weather1.WindSpeed was: 1.76 now: 2.8 #hooks:0 2022-01-12 20:47:12.028 luup.variable_set:: 63.urn:micasaverde-com:serviceId:HumiditySensor1.CurrentLevel was: 30 now: 27 #hooks:0 2022-01-12 20:47:12.028 luup.variable_set:: 65.urn:micasaverde-com:serviceId:HumiditySensor1.CurrentLevel was: 30 now: 27 #hooks:0 2022-01-12 20:47:12.028 luup.variable_set:: 63.urn:upnp-micasaverde-com:serviceId:Weather1.LastUpdate was: 1642047430 now: 1642049231 #hooks:0Any ideas on how to troubleshoot this.....
I just published an update to my Virtual Devices Plug-in.
What's new in version 1.5:
support for async HTTP (out of the box on openluup, just download https://github.com/akbooer/openLuup/blob/master/openLuup/http_async.lua and copy with the plug-in files on Vera) experimental support for setpoints management in Virtual Heaters (you know, the device will turn itself off if temperature is reached, and automatically on when temperature is not beyond the setpoint) external device for temperature in Virtual Heaters (just set urn:bochicchio-com:serviceId:VirtualHeater1/TemperatureDevice variable) small fixes, stabilizationGrab your copy from https://github.com/dbochicchio/vera/tree/master/VirtualDevices
As always, 100% local, 100% apps friendly, 100% supported by Alexa (and Google Home, I guess).
This topic has come up before but I haven't seen an answer. Symptom: AltuUI says there is a new update available, so you tell it to do the update but the update does not happen. AltUI remains stuck on it's old version. On other occasions it works OK. So my version is:
AltUI v2.49.2546, © 2019AltUI says this:
a newer version #2551 of ALTUI is available, do you want to upgrade ? add scrollable dialog for long boxes bugfix: clock display on safari remote url update ( @olov ) update jquery and bootstrap versions credential to camera device url ( @rafale77 ) ignore Ezlo hub ( @reneboer)Track through the JavaScript and find that this issues the update command:
function _triggerAltUIUpgrade(newversion,newtracnum) { var url = '?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&Version={1}&TracRev={0}'.format(newversion,newtracnum); return _httpGet(url,{}).always( function() { PageMessage.message(_T("Upgrade Request succeeded, a Luup reload will happen"),"success"); }); };And the url variable equals:
url: "?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&Version=40628&TracRev=2551"All looks good so far. I manually issue the same url complete with my openLuup ip_address in a local browser. Update fails - looks like AltUI is doing as it should:
http://ip_address:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&Version=40628&TracRev=2551In openLuup I see:
2021-12-06 13:56:14.821 luup_log:3: ALTUI: startupDeferred, called on behalf of device:3 2021-12-06 13:56:14.838 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.Version was: v2.49 now: v2.49 #hooks:0And then later:
2021-12-06 13:55:58.256 openLuup.server:: GET /data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&Version=40628&TracRev=2551 HTTP/1.1 tcp{client}: 0x25712a8 2021-12-06 13:55:58.257 luup.call_action:: 0.urn:micasaverde-com:serviceId:HomeAutomationGateway1.CreatePlugin 2021-12-06 13:55:58.259 luup.call_action:: 4.urn:upnp-org:serviceId:AltAppStore1.update_plugin 2021-12-06 13:55:58.260 luup_log:4: AltAppStore : starting <run> phase... 2021-12-06 13:55:58.262 luup_log:4: AltAppStore : downloading amg0/ALTUI [2551] to trash/AltAppStore/ 2021-12-06 13:55:58.262 luup_log:4: AltAppStore : GitHub request: https://api.github.com/repos/amg0/ALTUI/contents?ref=2551 2021-12-06 13:55:58.760 luup_log:4: AltAppStore : GitHub request: https://api.github.com/repos/amg0/ALTUI/contents/blockly?ref=2551 2021-12-06 13:55:59.543 luup_log:4: AltAppStore : getting contents of version: 2551 2021-12-06 13:55:59.544 luup.variable_set:: 4.urn:upnp-org:serviceId:altui1.DisplayLine1 was: AltAppStore now: Downloading... #hooks:0 2021-12-06 13:55:59.544 luup.variable_set:: 4.urn:upnp-org:serviceId:altui1.DisplayLine2 was: now: Alternate UI #hooks:0 2021-12-06 13:55:59.544 luup_log:4: AltAppStore : scheduling <job> phase... 2021-12-06 13:55:59.544 openLuup.requests:: 2021-12-06 13:55:59.545 openLuup.server:: request completed (148 bytes, 1 chunks, 1288 ms) tcp{client}: 0x25712a8 2021-12-06 13:55:59.554 openLuup.server:: request completed (6233 bytes, 1 chunks, 16442 ms) tcp{client}: 0x255e680 2021-12-06 13:55:59.555 luup_log:4: AltAppStore : ...final <job> phase 2021-12-06 13:55:59.555 luup_log:4: AltAppStore : Total size 0.000 (kB) 2021-12-06 13:55:59.555 luup.variable_set:: 4.urn:upnp-org:serviceId:altui1.DisplayLine2 was: Alternate UI now: Alternate UI 100% #hooks:0 2021-12-06 13:55:59.555 luup_log:4: AltAppStore : updating icons in icons/ ... 2021-12-06 13:55:59.555 luup_log:4: AltAppStore : updating device files in ./ ... 2021-12-06 13:55:59.556 luup_log:4: AltAppStore : ... 0 icon files 2021-12-06 13:55:59.556 luup_log:4: AltAppStore : ... 0 device files 2021-12-06 13:55:59.556 luup_log:4: AltAppStore : Alternate UI update completed 2021-12-06 13:55:59.556 openLuup.luup:: device 4 'Alternate App Store' requesting reload 2021-12-06 13:55:59.556 luup.reload:: saving user_data 2021-12-06 13:56:00.262 openLuup.luup:: exiting with code 42 - after 0.3 hoursAll looks OK. Then I check GitHub. It shows the latest changes to the version 2551. However this page says the latest version is 2550.
So I wondering what's going on. Seems the latest version number is not being picked by the installer? (not sure how it works.) Is it possible for openLuup to log a bit more about the version it's trying to install. As this call returns.
https://api.github.com/repos/amg0/ALTUI/contents?ref=2551 message "No commit found for the ref 2551" documentation_url "https://docs.github.com/v3/repos/contents/"But this works fine:
https://api.github.com/repos/amg0/ALTUI/contents?ref=2550So it looks like AMG0 doesn't always update the repository with whatever is needed to get this to work (I imagine that's easy to forget). But could openLuup send back a fail result to AltUI and AltUI pick that up? Currently it looks like AltUI always assumes everything went OK. Or somehow; could openLuup log and/or notify the user what went wrong?
Hi @toggledbits and others,
Could you help me out with the following use case? I have a z-wave module that doesn't have scene functionality, but I want to trigger a double click action on the switch.
What is the easiest way to do this in reactor? I'm struggling with this and I think I'm thinking too complex at this point.
Well, I disappeared down a rabbit hole on a different mission and resurfaced with this monstrosity.
What does it do?
It translates button functions for various (certainly not all) IRP protocols to Pronto codes. These can then be sent by a plugin that sends Pronto Codes to IR transmitters - such as the BroadLink Plugin or the GC100 Plugin (or similar).
The IRP protocol "Device", "Subdevice" and "Function" numbers are stored in a json file as buttons for "virtual remotes".
So you could have say three physical IR transmitters and want to command different AV devices (ie TVs, AVR, Xmas tree, etc) in the vicinity of those various IR emitters.
The button codes are far less cumbersome than heaps of pronto codes. You can set up a virtual remote for each AV device in the json file. Each physical emitter can be assigned to any virtual remote. And away you go!
Well - you already have a pile of pronto codes already running just fine? However, as the plugin "manufacturers" pronto codes, you could also use it to scan/search for functions for any AV device you may have. GitHub has an example for Pioneer: SearchForButtonCodes.lua
Read about the IRP protocol
Find "Device", "Subdevice" and "Function" codes:
IR database
Plugin details in:
GitHub
Install via AltUI:
Plugins available via AltUI
Version 0.51
Initial release.
Version 0.52
Add RC6 format: includes Windows Media Center based items eg Intel NUCs, Xboxes, Kodi, etc
Panasonic plasma TV json.jpg
Panasonic plasma TV web page.jpg
@toggledbits Hi Patrick. I had my internet go down for about 12 hours the other day, and that experience encouraged me to work on getting my HA off the cloud to the extent that I can. I have not converted my Veras to local devices yet, though after the next VeraPlus stable firmware release, I will probably run your scripts to localize the device as I don't see Ezlo surviving to maintain Vera firmware.
My question concerns the icons in your plugins. While attempting to mod a reactor sensor during the outage, I could not really do anything (without a sense of risk anyway) as the icons used are pulled from your website. Many Vera plugins operate this way--no doubt to save space on the vera, and my inclination was to manually start downloading what I needed when the outage was over. I run everything on openLuup and space is not an issue. It occurred to me that localizing a plugin could be a button push somewhere in the plugin UI where one could auto download any needed icons and the plugin would recognize the local copy first, before trying the cloud.
Could this be a possible enhancement to your plugins? I don't really have a technical grasp of whether this would be workable or not.
Homebridge to Openluup
-
thanks @akbooer . I'll be adding the installation instructions to the readme file... By the way, this plugin also works for ecobee thermostat, the native ecobee lua plugin by @rafale77 works ok when there is only one thermostat in the ecobee account but when more than one, ecobee server keeps deauthorizing the plugin...
@rafale77 I also use homebridge the other way (openluup to homebridge) and is great.
I'm currently using it for:
- Nest thermostats with google accounts.
- Ecobee accounts with multiple thermostats
- AUX Mini split with built-in wifi modules
Planning on adding control for AppleTV , Ring devices, Doorbird motion detection and many more...
It will allow us to finally include many of the popular cloud based devices that own into the openluup environment...
Something really cool about homebridge is that the manual and basic automation can be done from within homekit by the end-user, but deeper logic can be done from within openluup. Thinking about bringing node-red into the mix also... anyhow... I hope it can be useful for everyone here...
-
Hi ronluna
Great to see more stuff supporting openLuup and the like. If you feel like adding the plugin to the Alt App Store; I can add it to the list of available plugins:
-
@ronluna I reinstalled the plugin from altappstore but still can't change setpoint. It's sending the wrong characteristicType
2021-03-19 08:47:29.288 luup_log:17: homebridge2openluup debug: Homebridge Put device VALUE = 23 2021-03-19 08:47:29.288 luup_log:17: homebridge2openluup debug: request_body for everything else = {"characteristicType":"HeatingThresholdTemperature","value":"23"} 2021-03-19 08:47:29.288 luup_log:17: homebridge2openluup debug: PUT Auth = Bearer XXXXXXXXXX 2021-03-19 08:47:29.288 luup_log:17: homebridge2openluup debug: PUT Request Body = {"characteristicType":"HeatingThresholdTemperature","value":"23"} 2021-03-19 08:47:29.288 luup_log:17: homebridge2openluup debug: PUT Request Length = 65 2021-03-19 08:47:29.303 luup_log:17: homebridge2openluup debug: URL request result: r = 1 2021-03-19 08:47:29.303 luup_log:17: homebridge2openluup debug: URL request result: c = 400 2021-03-19 08:47:29.303 luup_log:17: homebridge2openluup debug: URL request result: h = table: 0x55b66e8b2910 2021-03-19 08:47:29.303 luup_log:17: homebridge2openluup debug: PUT Access Token = XXXXXXXXXX 2021-03-19 08:47:29.303 luup_log:17: homebridge2openluup debug: response_body PUT 1 = {"statusCode":400,"message":"Invalid characteristicType. Valid types are: 'TargetHeatingCoolingState', 'TargetTemperature', 'TemperatureDisplayUnits', 'RotationSpeed', 'TargetHorizontalTiltAngle', 'TargetVerticalTiltAngle'.","error":"Bad Request"} 2021-03-19 08:47:29.303 luup_log:17: homebridge2openluup debug: HTTP 400 Bad Request: JSON parse error
-
@crille I thought there were only two type of temperature controller (Thermostat and HeaterCooler) in homebridge/homekit but apparently I'm wrong. I also thought homebridge/homekit (depending on the device type) would force device to share the same characteristicType ... Seems like I was wrong again... so depending on the plugin being used on homebridge the author may very well define the characteristicType somewhat differently to other plugin-ins...
What kind of thermostat is configured on your homebridge setup? Brand / model . Can you please share the json response when the plug-in is updating the device’s values.. similar to this:
2021-03-21 07:24:20.861 luup_log:83: homebridge2openluup debug: concat_response_body 1 = {"aid":339,"iid":8,"uuid":"0000004A-0000-1000-8000-0026BB765291","type":"Thermostat","humanType":"Thermostat","serviceName":"My ecobee","serviceCharacteristics":[{"aid":339,"iid":10,"uuid":"0000000F-0000-1000-8000-0026BB765291","type":"CurrentHeatingCoolingState","serviceType":"Thermostat","serviceName":"My ecobee","description":"Current Heating Cooling State","value":0,"format":"uint8","perms":["ev","pr"],"maxValue":2,"minValue":0,"minStep":1,"canRead":true,"canWrite":false,"ev":true},{"aid":339,"iid":11,"uuid":"00000033-0000-1000-8000-0026BB765291","type":"TargetHeatingCoolingState","serviceType":"Thermostat","serviceName":"My ecobee","description":"Target Heating Cooling State","value":0,"format":"uint8","perms":["ev","pr","pw"],"maxValue":3,"minValue":0,"minStep":1,"canRead":true,"canWrite":true,"ev":true},{"aid":339,"iid":12,"uuid":"00000011-0000-1000-8000-0026BB765291","type":"CurrentTemperature","serviceType":"Thermostat","serviceName":"My ecobee","description":"Current Temperature","value":24.3667,"format":"float","perms":["ev","pr"],"unit":"celsius","maxValue":37.77777777777778,"minValue":-73.33333333333333,"minStep":0.1,"canRead":true,"canWrite":false,"ev":true},{"aid":339,"iid":13,"uuid":"00000035-0000-1000-8000-0026BB765291","type":"TargetTemperature","serviceType":"Thermostat","serviceName":"My ecobee","description":"Target Temperature","value":23.8556,"format":"float","perms":["ev","pr","pw"],"unit":"celsius","maxValue":26.666666666666664,"minValue":15.555555555555555,"minStep":0.1,"canRead":true,"canWrite":true,"ev":true},{"aid":339,"iid":14,"uuid":"00000036-0000-1000-8000-0026BB765291","type":"TemperatureDisplayUnits","serviceType":"Thermostat","serviceName":"My ecobee","description":"Temperature Display Units","value":1,"format":"uint8","perms":["ev","pr","pw"],"maxValue":1,"minValue":0,"minStep":1,"canRead":true,"canWrite":true,"ev":true}],"accessoryInformation":{"Manufacturer":"ecobee","Model":"nikeSmart","Name":"My ecobee","Serial Number":"Vera ID: 173","Firmware Revision":"0.8.3-beta.12"},"values":{"CurrentHeatingCoolingState":0,"TargetHeatingCoolingState":0,"CurrentTemperature":24.3667,"TargetTemperature":23.8556,"TemperatureDisplayUnits":1},"instance":{"name":"homebridge","username":"0E:10:83:81:C6:A5","ipAddress":"10.1.11.21","port":51706,"services":[],"connectionFailedCount":0},"uniqueId":"240d0198fc8289b3b5a77315b7e4ec132096ddbd6e6beb5e4c174a6a84908e8d"}
-
@ronluna I thought so as well. That’s why I thought any device configured as a thermostat in homebridge would have the same characteristics and your plugin would support it.
My “thermostat” is another homebridge plugin for MELCloud (Mitsubishi cloud for my WiFi connected inverters).Here is the json response:
luup_log:17: homebridge2openluup debug: concat_response_body 1 = {"aid":60,"iid":8,"uuid":"0000004A-0000-1000-8000-0026BB765291","type":"Thermostat","humanType":"Thermostat","serviceName":"Övervåningen","serviceCharacteristics":[{"aid":60,"iid":10,"uuid":"0000000F-0000-1000-8000-0026BB765291","type":"CurrentHeatingCoolingState","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Current Heating Cooling State","value":1,"format":"uint8","perms":["pr","ev"],"maxValue":2,"minValue":0,"canRead":true,"canWrite":false,"ev":true},{"aid":60,"iid":11,"uuid":"00000033-0000-1000-8000-0026BB765291","type":"TargetHeatingCoolingState","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Target Heating Cooling State","value":1,"format":"uint8","perms":["pr","pw","ev"],"maxValue":3,"minValue":0,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":12,"uuid":"00000011-0000-1000-8000-0026BB765291","type":"CurrentTemperature","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Current Temperature","value":23,"format":"float","perms":["pr","ev"],"unit":"celsius","maxValue":100,"minValue":0,"minStep":0.1,"canRead":true,"canWrite":false,"ev":true},{"aid":60,"iid":13,"uuid":"00000035-0000-1000-8000-0026BB765291","type":"TargetTemperature","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Target Temperature","value":22,"format":"float","perms":["pr","pw","ev"],"unit":"celsius","maxValue":38,"minValue":10,"minStep":0.1,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":14,"uuid":"00000036-0000-1000-8000-0026BB765291","type":"TemperatureDisplayUnits","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Temperature Display Units","value":0,"format":"uint8","perms":["pr","pw","ev"],"maxValue":1,"minValue":0,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":15,"uuid":"00000029-0000-1000-8000-0026BB765291","type":"RotationSpeed","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Rotation Speed","value":60,"format":"float","perms":["pr","pw","ev"],"unit":"percentage","maxValue":100,"minValue":0,"minStep":1,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":16,"uuid":"0000006C-0000-1000-8000-0026BB765291","type":"CurrentHorizontalTiltAngle","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Current Horizontal Tilt Angle","value":0,"format":"int","perms":["pr","ev"],"unit":"arcdegrees","maxValue":90,"minValue":-90,"minStep":1,"canRead":true,"canWrite":false,"ev":true},{"aid":60,"iid":17,"uuid":"0000007B-0000-1000-8000-0026BB765291","type":"TargetHorizontalTiltAngle","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Target Horizontal Tilt Angle","value":0,"format":"int","perms":["pr","pw","ev"],"unit":"arcdegrees","maxValue":90,"minValue":-90,"minStep":1,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":18,"uuid":"0000006E-0000-1000-8000-0026BB765291","type":"CurrentVerticalTiltAngle","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Current Vertical Tilt Angle","value":-45,"format":"int","perms":["pr","ev"],"unit":"arcdegrees","maxValue":90,"minValue":-90,"minStep":1,"canRead":true,"canWrite":false,"ev":true},{"aid":60,"iid":19,"uuid":"0000007D-0000-1000-8000-0026BB765291","type":"TargetVerticalTiltAngle","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Target Vertical Tilt Angle","value":-45,"format":"int","perms":["pr","pw","ev"],"unit":"arcdegrees","maxValue":90,"minValue":-90,"minStep":1,"canRead":true,"canWrite":true,"ev":true}],"accessoryInformation":{"Manufacturer":"Mitsubishi","Model":"Default-Model","Name":"Övervåningen","Serial Number":"1805118279","Firmware Revision":"0.3.4"},"values":{"CurrentHeatingCoolingState":0,"TargetHeatingCoolingState":0,"CurrentTemperature":0,"TargetTemperature":10,"TemperatureDisplayUnits":0,"RotationSpeed":0,"CurrentHorizontalTiltAngle":-90,"TargetHorizontalTiltAngle":-90,"CurrentVerticalTiltAngle":-90,"TargetVerticalTiltAngle":-90},"instance":{"name":"homebridge","username":"CC:22:3D:E3:CE:43","ipAddress":"127.0.0.1","port":51826,"services":[],"connectionFailedCount":0},"uniqueId":"8f37721c51dc9fd6b15aad7024d6a8460038b1ee7e6fb23c732f1abc5bcfb8fd"}
-
@ronluna Sorry, but it does not work.
I believe the MELCloud plugin only accepts "TargetTemperature" for changing Setpoint
luup_log:17: homebridge2openluup debug: response_body PUT 1 = {"statusCode":400,"message":"Invalid characteristicType. Valid types are: 'TargetHeatingCoolingState', 'TargetTemperature', 'TemperatureDisplayUnits', 'RotationSpeed', 'TargetHorizontalTiltAngle', 'TargetVerticalTiltAngle'.","error":"Bad Request"}
and not
luup.variable_set:: 18.urn:upnp-org:serviceId:TemperatureSetpoint1_Heat.CurrentSetpoint was: 22 now: 18 #hooks:0
This is only if you want to support the MELCloud provisioned thermostat, otherwise do not put to much energy in to it.
For me it would be at great way to control my temperature triggered by house modes since there is no MELCloud plugin for openLuup.